Skip to main content
Question

Branching funnel based on user state (new vs existing user)

  • April 15, 2026
  • 2 replies
  • 28 views

Forum|alt.badge.img

Hi,

I’ve been exploring RevenueCat Funnels, and the feature looks really promising.

However, I’m not sure how to handle branching the flow based on the user’s state.

As part of my funnel, I include authentication. I redirect users to my app where they can sign in or sign up, and then I send them back to the funnel.

What I’d like to achieve is showing different steps depending on the user type:

  • Newly registered users
  • Existing users who already have an account but haven’t purchased a subscription yet

For each group, I want to display different content. For new users, I’d like to introduce the app in general + show subscription benefits. For existing users without a subscription, I want to focus more on subscription benefits.

When redirecting users back to the funnel, I could include a query parameter like ?new_user={true|false}, along with state and app_user_id. However, I don’t see any option in the funnel settings that allows branching based on these parameters.

Is there a way to achieve this kind of behavior?

Thank you for your help!

Jan Zabloudil

2 replies

amps33
Forum|alt.badge.img
  • New Member
  • April 15, 2026

You’re trying to turn a linear tool into a decision engine, it won’t bend that way.

RevenueCat funnels don’t really “branch” on external params like that bc they assume you already know who you’re talking to.

So the move is simpler:

Don’t branch inside the funnel, decide before the funnel.

Send users to different funnel entry points based on state:

- new users → intro + context

- existing users → straight to value

Trying to pass

?new_user=true

and expecting logic inside is where it breaks and backend thinking in a frontend tool. Keep the funnel dumb because converts better anyway. 


Dan Pannasch
RevenueCat Staff
Forum|alt.badge.img+3
  • RevenueCat Staff
  • April 16, 2026

Hi Jan! So happy to hear you’re exploring Funnels. What you’re describing is certainly possible. The way you’d do this is:

  1. Add a Branch node after the user authenticates
  2. Add a rule in the branch node that when the custom parameter new_user is true then navigate to x, else navigate to y (or whatever set of logic around that custom parameter you'd prefer)

 

Let me know if you have any trouble setting that up, or if you have any other questions or feedback as you go!