Journey 3 · Non-transacted bidder: funnel abandon: Review Pack

Journey 3 · Non-transacted bidder: funnel abandon (ACTIVATE · O2 · 8 moments) · Review packPack version: 4 Aug 2026, 16:51 (London) · source of truth: J3/content.json

Funnel abandon: I hesitated, remove my doubt, don’t punish it

The buildable spec: the TO-BE map tab (entry, splits, waits, exits, suppressions) and the decisioning matrix on the Campaign brief tab (who gets what, with copy).
The contact rules: the global set on the Reference tab, plus this journey&rsquo;s own applications and exceptions in the TO-BE map&rsquo;s rules panel. Both bind the canvas.
The data: the asks table below; each row&rsquo;s status and owner is the build dependency list. The dwell rows sequence AFTER Analytics defines the thresholds (Analytics brief, ask 1).
Not a dependency: the next-best-action decisioning engine. It compiles the same rules this pack states; this canvas launches on Braze-native logic plus the ruled exclusion segments, and adopts the engine&rsquo;s attributes when they land.

For: Sheran (gate) plus Analytics, Product, Eng, Design and CRM via the Gate-1 feedback form.
The one change: The ~72k drops a month (confirmed) are three jobs, not one, and each gets an answer at the step where doubt bites.
How to read: Live (watch it as the customer) · AS-IS (today) · TO-BE map (the build logic) · Campaign brief (the plan) · Design brief · Analytics brief · Engineering brief · How we work · Reference.
Status: draft until this journey’s design brief is approved. ACT-13 is signed; the other seven moments are not.

📮 How to feed back (this pack IS the review): read it, then put everything in the feedback form: as many points as you like, and submit again any time more occurs to you. Every point gets an answer. Sign-off comes after the changes round, recorded per team.

ValidatedAnalytics validation requiredData / build outstanding