DemoSpace
A

Assumptions & Notes

  • Approving will create this journey as a DRAFT only. After creation, ask to 'send this journey for approval' to submit it conversationally.
  • Using default points program: DemoSpaceDefaultProgram
  • Note: In the campaign creation flow, 'module_type' is always set to 'ENGAGE' for both allocation and expiry strategies.
  • Push Notification Account changed from ['DemoSpace'] to ['PN_BUKL'].
  • Using existing allocation strategy: AIRA_902370515, other matches []

Journey's ready for your review — it's in the UI now with a Create CTA. Here's what it does:

  • Enters: loyal customers with total bill amount ≥ $1 (last 365 days, dynamic — refreshes as customers transact)
  • Step 1: push notification — "Thanks for shopping with us!" / "We've added 50 points to your account as a thank-you..."
  • Step 2: 50 fixed loyalty points (points program DemoSpaceDefaultProgram)
  • Exit after points

Two things worth knowing:

Push account — "DemoSpace" resolved to the org's actual MOBILEPUSH account PN_BUKL, so the push fires through that.
Trigger reality — a journey enters customers from an audience, so this reacts to audience membership, not each live transaction. If you actually want "the instant any customer bills ≥ $1, fire push + award points" on the transaction event itself, that's a promotion, not a journey — say the word and I'll build that version instead.

Approving creates it as a draft. Once you're happy, tell me to "send this journey for approval" and I'll submit it. Want any changes to the copy, points, or audience window first?