Building the behavioral trigger layer
The activation sequence fired on a schedule instead of on what people actually did, and nobody had named that as the problem.
The read
Funded users were stopping there, and nothing in the lifecycle spoke to them once they had. There was no path at all from a funded account to a first trade.
Users were funding their accounts and stopping. The lifecycle was sending scheduled emails about why to trade. They had already decided to fund — they were stuck on the next step, not the first one. The messaging was solving the wrong problem.
The read: the lifecycle was timed, not triggered. A user who funded yesterday and a user who funded six weeks ago were getting the same email at the same time.
The decision
Rebuild the trigger layer around real product events. Funded-idle is a specific signal. It needed its own journey, its own timing, and its own messaging logic, separate from the general activation sequence.
Treat funded-idle as a distinct lifecycle stage, not a variation of onboarding.
The number I picked
Funded-idle to first-trade conversion. Not activation broadly, not engagement. The specific transition from funded and dormant to first real product action. That was the number that proved whether the trigger layer was working.
The build
Instrumented the funded-idle event in Braze as a behavioral trigger and built a dedicated journey that fired on account funding, not on a schedule. Designed messaging around the specific barrier a funded user faces — not why to trade, but how to make your first trade right now.
Built separate branches for users who funded and did nothing, users who viewed the trading interface but didn’t execute, and users who started a trade and dropped off. Each branch had different logic and timing. Pulled in Product to confirm the event instrumentation was clean before scaling.
~19%
Funded-idle to first trade at two months, where there had been no path before
~24%
The same rate on the longer-term read
The behavioral layer proved that responding to what users did, rather than how long they’d been in the funnel, was what moved revenue behavior. It also validated the next step: branching the whole Canvas by product intent.
Tech
Braze
Multi-channel Canvas architecture
Product event instrumentation
Behavioral triggers
Push deep-linking
Suppression and frequency logic