No send in this journey is fired natively by the app itself, so there is no native-to-Braze migration roster here: everything that sends today already lives in the messaging platform or an external one, and each row’s call sits on the As-is tab.
7 rows: 4 new events and feeds, 0 sends moving into Braze, and 3 computed traits (Analytics builds, no engineering hours). The D badge is the walkthrough pin number, coloured by what exists today: BUILDABLE TODAY EXISTS, NOT USABLE YET DOES NOT EXIST YET. Delivery fixes and app defects follow in their own sections.
The events and attributes the journey's triggers and ends ride. Each row is the contract: what fires, what it carries, who reads it. Nothing in this band gates the phase 1 welcome-back door.
| The data point | The work | What it must carry | Phase · status · depends on |
|---|---|---|---|
D4The lapse-threshold crossing eventlapse_threshold_crossed, on the day-60 boundaryBuild the event so entry is trigger-driven; the batch-derived hand-off is the working interim. | New event | Entry by hand-off, not day-count: the event makes the hand-off real time instead of overnight. | PHASE 2 gated Queued; the batch interim works Nothing. ▸ What exists today, and where it is usedWhat exists today BUILDABLE TODAYDerivable in batch; no event exists. Used where Episode entry |
D6Final-attempt evidence eventsfinal_sent · final_answered · suppressedBuild the three events so the end can be proven to be an end. | New events | The post-end suppression is a promise to the customer; without the events it cannot be audited. | PHASE 2 gated Queued behind the offer decision The offer-depth ruling. ▸ What exists today, and where it is usedWhat exists today DOES NOT EXIST YETDo not exist. Used where The final attempt and its suppression |
D7App open plus lifecycle statesession + lifecycle band, at read timeNothing new: session recency is Braze-native and the lifecycle band rides the sync extension. Stated so the organic-return suppression's contract exists once. | Configuration | An organic return is recognised instead of chased: any session inside 30 days suppresses the win-back. | PHASE 1 ships now Configuration at build The sync extension. ▸ What exists today, and where it is usedWhat exists today BUILDABLE TODAYSession recency live in Braze; the band rides the sync. Used where The organic suppression and the welcome-back trigger |
D2The ownership hand-offjourney_state, campaign-written, carrying the power markerNothing to build: the first-slip journey's canvas writes the hand-off at day 60; this journey's canvas reads it. | Canvas wiring | One lapse owner per customer, and the power-user marker travels so the recognition register fires without a second lookup. | PHASE 1 ships now Wiring at build, jointly with the first-slip journey The first-slip journey's go-live. ▸ What exists today, and where it is usedWhat exists today DOES NOT EXIST YETCampaign-written at build, both sides. Used where Episode entry and the register pick |
No new data in this band: logic, integration and release work.
| The change | The work | Phase · status · depends on |
|---|
Named here so the full picture is one table. The contract is the row: what each trait computes, what reaches the sender today, and what remains to build.
| The computed trait | The work | Phase · status · depends on |
|---|---|---|
D1The churn band and propensity scorechurn_band · propensity, dailyPipe the live warehouse score into the daily sync: the one launch gate. | Sync payload extension, Analytics-owned | PHASE 1 ships now With Analytics The CDI payload extension. ▸ The contractWhat it must carry Who is worth a touch and how hard: the band gates every triggered send, sets the backfill order, and draws the low band's silence.What exists today EXISTS, NOT IN BRAZELive in the warehouse; not in the payload. Used where Every triggered send |
D3The usual route and the from-priceusual_route · from_price, nightly computedCompute nightly on the standing pattern: never a live lookup, never an up-to claim. | Computed traits, Analytics-owned | PHASE 1 ships now With Analytics The CDI payload extension. ▸ The contractWhat it must carry The route anchor in every send, and the substantiated comparison figures (walk-up, paid, from-price).What exists today DOES NOT EXIST YETComputable; not built for this journey's cohort. Used where Both knocks, the door card, the goodbye and the anniversary |
D5The anniversary traitfirst_purchase_anniversary, nightlyCompute the anniversary date; the warehouse holds first and last purchase for the whole pool. | One computed trait | PHASE 1 ships now With Analytics The CDI payload extension. ▸ The contractWhat it must carry The annual beat's trigger: for the mostly one-time pool the first and last purchase share a date.What exists today BUILDABLE TODAYDerivable; not built. Used where The anniversary message |
Not listed because there is nothing to build: session recency (Braze-native, the whole phase 1 trigger), the transaction events that clear an episode, and the ownership flag the canvas writes.
Four changes the customer never sees: what is broken today, the fix we are asking Engineering for, and why it belongs in this journey rather than a general engineering backlog. None is a comm and none needs a decision from Marketing. Each one either loses a message this journey depends on, or decides whether something else can be built at all.
One plumbing extension carries the whole launch: the churn band and propensity score into the daily warehouse-to-Braze sync. The score is live in the warehouse today.
| The delivery fix | The fix we are asking for | Who does it | Phase |
|---|---|---|---|
| The churn band and propensity score into the daily sync | Add the band and score to the daily warehouse-to-Braze sync on the standing pattern; Analytics pipe from their side, Engineering only if the CDI mapping needs registering. | BACKEND ENG | PHASE 1 ships now ▸ The problem today, and why it sits hereThe problem today The score is live in the warehouse today; it does not reach the sender, and every triggered send selects on it.Why it sits in this journey This one extension is the whole phase 2 launch gate: it replaced the model build the journey once waited on. |
| The expiring magic-link door | Fix the link lifetime or the retry flow: a product fix, flagged from this journey because returners hit it hardest. | BACKEND ENG | PHASE 1 ships now ▸ The problem today, and why it sits hereThe problem today Magic links can expire before the code is typed: the sign-in door itself fails some returners.Why it sits in this journey Every send in this journey lands on a sign-in; a failing door taxes them all. |
Two live gaps. Neither blocks the door; both cost reads or returns.
| The defect | The fix we are asking for |
|---|---|
| Content-card impressions and clicks do not register | Fix the shared content-card instrumentation so impressions and clicks register.▸ The problem today, and why it matters hereThe problem today The estate-wide instrumentation gap: the welcome-back card and the live incentive card both run blind.Why it matters here The phase 1 ship is a card; until the fix lands its read is indirect (sessions and conversions only). |
| The magic-link expiry | Product fix; flagged here because the welcome-back promise dies at a failed door.▸ The problem today, and why it matters hereThe problem today The sign-in link can expire before the emailed code is entered.Why it matters here Returners are the cohort most likely to be signed out, so the defect concentrates on exactly this journey's audience. |
Source: the 20 Aug 2026 data-availability sweep in the journey spec, the pins record, and the 30 Jul 2026 warehouse count. Board rows are raised from these contracts once sized.