← Back to home

Integration Blueprint

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.

Pick your starting level

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

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

Details ↓

Level 2

Real-time & dynamic

Real-time events, multiple parallel campaigns, automated segment updates. The most common production deployment.

  • 8–10 weeks to full launch
  • 3–4 weeks of integrator engineering effort
  • 3–5 campaigns running in parallel

Details ↓

Level 3

Full personalization

All event types, daily tier recalculation, full segmentation, A/B testing of mechanics. Mature programs only.

  • 12+ weeks to full launch
  • 5–8 weeks of integrator engineering effort
  • Unlimited parallel campaigns

Details ↓

Level 1

Batch & simple campaigns

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.

What you push

  • One nightly batch of card transactions or bill payments to PUT /api/v3/card-transactions or PUT /api/v3/bills/payments.
  • One initial segment assignment per qualifying customer via PUT /api/v3/customers/{code}/segments/{segment}.

What you receive

  • Mission completion webhooks (informational, for analytics).
  • Cashback wallet payout webhooks at month-end (your handler delivers the money).
  • Eligibility check webhook before each cashout (your endpoint returns yes/no).

Campaigns you can run

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.

What's not in scope at L1

  • Real-time mission progress (users see yesterday's totals).
  • Wheel and gamified mechanics (these need real-time event flow to feel responsive).
  • Tiered loyalty (segment changes lag a day).
  • Multi-corridor remittance campaigns.

How long

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

Real-time & dynamic

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.

What you push

  • Card transactions in real time (within seconds of authorization) to PUT /api/v3/card-transactions.
  • Status updates (chargebacks, reversals) via PATCH /api/v3/card-transactions/{id}/status as they happen.
  • Bill payments in real time to PUT /api/v3/bills/payments.
  • Generic events (login, profile completion, etc.) to PUT /api/v3/generic-events.
  • Segment assignments updated automatically on a recurring job (weekly typical, daily for tier-based campaigns).

What you receive

  • Mission completion webhooks for every running campaign.
  • Reward Notification webhooks for wheel wins (immediate) and cashback cycle close (monthly).
  • Eligibility checks before payouts.
  • Generic event notifications for behavioral milestones.

Campaigns you can run

3 to 5 patterns simultaneously is the typical sweet spot. A common bundle:

What's not in scope at L2

  • Tiered loyalty ladders with daily recalculation (still possible, but typically batched weekly at L2).
  • Multi-corridor remittance with real-time settlement.
  • A/B testing of campaign mechanics within the same segment.

How long

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

Full personalization

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.

What you push

  • Everything from Level 2, plus:
  • Transfer events for remittance and P2P campaigns (when transfer ingestion ships) or generic events for transfer-driven mechanics.
  • Daily tier recalculation: every customer's segment is recomputed from up-to-the-minute event data and updated via segment-assignment APIs.
  • Custom event names for product-specific actions (referral completed, KYC level upgraded, savings goal hit, etc.).

What you receive

  • Everything from Level 2.
  • Limit Booster webhooks if running credit-limit-redemption campaigns.
  • Wallet-mode-switch intent webhooks for users moving between cashback and Limit Booster modes.

Campaigns you can run

Unlimited, organized by segment. A typical L3 program runs:

What's not in scope at L3

  • The platform doesn't replace your CRM, your fraud-detection system, or your accounting ledger. L3 integrates deeply with all three but does not subsume them.

How long

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.

How to choose

Start at Level 1 if…

  • You're piloting the model with one cohort or one campaign.
  • Your engineering team has 1–2 weeks to allocate.
  • You don't need real-time progress in the user UI.
  • Daily-batch settlement matches your existing data pipeline.

Start at Level 3 if…

  • You already have a real-time event pipeline.
  • You're committing to engagement as a core product capability.
  • You need tier-based loyalty with daily moves.
  • You operate across multiple currencies or corridors.

Not sure which level fits?

Tell us about your data, your stack, and your timeline. We'll recommend a starting level and a path forward.

Talk to our team