Level 1
Batch & simple campaigns
One or two campaigns running on daily-batch event pushes. Fastest path to a live engagement program.
- 4–6 weeks to first campaign
- 1–2 weeks of integrator engineering effort
- 1–2 campaigns running in parallel
Most successful Flourish rollouts follow a three-level progression: start narrow, prove the model, then expand. Each level is a complete production deployment — not a stepping stone — so you launch real campaigns at any depth that matches your timeline.
All three levels run live campaigns and pay real rewards. The difference is breadth: how many campaigns, how fresh the data, how dynamic the segmentation.
Level 1
One or two campaigns running on daily-batch event pushes. Fastest path to a live engagement program.
Level 2
Real-time events, multiple parallel campaigns, automated segment updates. The most common production deployment.
Level 3
All event types, daily tier recalculation, full segmentation, A/B testing of mechanics. Mature programs only.
Level 1
Best for first-pilot rollouts, validating the model on a single cohort, or running a one-off promotional campaign before deciding on a larger commitment.
PUT /api/v3/card-transactions or PUT /api/v3/bills/payments.PUT /api/v3/customers/{code}/segments/{segment}.Any single campaign from the patterns library — e.g. Onboarding Activation, Spending Threshold Cashback, or Login Engagement. Combining two campaigns is fine; combining three with batch data starts to lose freshness.
Typical timeline: 4 to 6 weeks from contract signature. Engineering effort on your side: 1 to 2 weeks of focused work to wire the daily batch and the webhook handlers.
Graduate to Level 2 when: you want users to see their progress update during the day, you want to launch a wheel-based campaign, or you want to run more than two campaigns simultaneously.
Level 2
The most common production deployment. Real-time event flow unlocks gamification (wheel, scratch card), responsive UX (users see balances update immediately), and parallel campaigns covering multiple goals.
PUT /api/v3/card-transactions.PATCH /api/v3/card-transactions/{id}/status as they happen.PUT /api/v3/bills/payments.PUT /api/v3/generic-events.3 to 5 patterns simultaneously is the typical sweet spot. A common bundle:
Typical timeline: 8 to 10 weeks from contract signature. Engineering effort on your side: 3 to 4 weeks — mostly the real-time event-push pipeline and the cashback eligibility endpoint.
Graduate to Level 3 when: you want to run dozens of parallel campaigns, A/B test mechanics, support multiple corridors, or operate a daily-recalculated tier ladder.
Level 3
For mature programs running an engagement engine as a core product capability. All event types, full segmentation, A/B testing, daily tier moves, multi-currency, and multi-corridor support.
Unlimited, organized by segment. A typical L3 program runs:
Typical timeline: 12+ weeks from contract signature. Engineering effort on your side: 5 to 8 weeks. Most of the additional time is on the integrator side, building real-time tier recalculation jobs and wiring custom event sources.
Most common starting point.
Tell us about your data, your stack, and your timeline. We'll recommend a starting level and a path forward.
Talk to our team