Workload Optimization in User Account Creation with Multiple Actions (Social Login, Affiliates, Plans, etc.)

Hi everyone!

I’m currently experiencing a considerable amount of workload consumption in my user account creation flow and would like to understand if this level of usage is expected—or if anyone has suggestions on how to optimize it.

Current Flow:

When a new user registers (mostly via Google social login), I perform the following actions in the backend:

  1. User creation (via Bubble’s default action or Google login).

  2. Check if the user already has other accounts, to prevent them from receiving free credits more than once.

  3. Check for pending subscriptions, since a user may purchase a plan before registering. If that’s the case, we link the subscription to the newly created user.

  4. Check for affiliate referrals, in case the user was invited by someone.

  5. Modify the user’s data, transferring information returned by Google login (which Bubble stores in a specific field) to my main user fields (name, email, etc.). This helps with future CRM integrations and data consistency.

Current Stats:

  • An average of 150 new registrations per day

  • Around 5,300 workload usage per week

My Question:

Does this workload usage seem too high for this kind of flow?
Has anyone experienced something similar or has ideas on how to optimize the process?

Notes:

  • Some actions are already centralized in backend workflows to avoid duplication.

  • Modifying the Google data is important for me, as it standardizes user info and simplifies CRM integration.

I’d really appreciate any help or insights you can share!

This topic was automatically closed after 70 days. New replies are no longer allowed.