Designing a user journey automation for different user states in Make

Questions
1

:bullseye: What is your goal?

Design an automated user journey in Make that routes users based on their state
(cold user, dropped user, ready-to-buy user) to the correct flow or destination.

:thinking: What is the problem & what have you tried?

I’m unsure about the best scenario architecture in Make to detect user state
and route them efficiently.

I’m considering using a Custom Webhook as the entry point, a Router to split
the flow, and a Data Store to track user state, but I’m not confident about
the best logic or structure.

:clipboard: Error messages or input/output bundles

Hi everyone,

I’m building a scenario in Make and I need advice on designing a clean and
scalable user journey automation.

The scenario should handle:

  1. Cold users with no prior interaction
  2. Users who drop off during the process
  3. Users who have confirmed purchase intent

Planned tools: Webhooks, Routers, Data Stores
Goal: route users to the correct flow or provide immediate product access

Any best practices or recommended patterns would be appreciated.

1 Like
3

I suggest you make a detailed description of your manual process and send it if possible.
Where does the data come from?
What is the flow that the data will follow?
What are the conditions? etc.

4

Your logic is sound.
The main question is, who or what changes the user’s states?
Do you do it manually or is it rule based after a user action (or inaction)?