FloKit can start without an app release when your subscription source and MMP
are already live. Add SDK or server-side events later when you need richer
onboarding, paywall, and lifecycle signals.
Before you start
- Production app name, platform, bundle ID or package name, and store URLs.
- Access to App Store Connect, Google Play, or Stripe revenue data.
- Access to AppsFlyer or Adjust if you want attributed CAC and payback.
- A known user identifier strategy across subscription, attribution, and product events.
- A target payback window, such as 30, 60, or 90 days.
Onboarding steps
Create the workspace
Create a FloKit workspace for the production app. Keep staging, sandbox, and
production workspaces separate so reports and guardrails do not mix test data
with live acquisition spend.
Confirm app identity
Add the app name, platform, store URL, bundle ID or package name, and primary
markets. FloKit uses this identity to scope integrations, attribution joins,
reports, and future recommendations to the correct app.
Connect revenue
Connect App Store Connect, Google Play, or Stripe first. Revenue is the anchor
for payback, ROAS, cohort LTV, trial conversion, renewals, refunds, and churn.See App Store Connect,
Google Play, or Stripe.
Send product and funnel events
Send events directly to FloKit or import them from a warehouse. Start with
paywall impressions, trial starts, subscription starts, cancellations, and
key onboarding milestones.See Event taxonomy and
Server-side events.
Validate identity mapping
Check that anonymous IDs, app user IDs, subscription customer IDs, and MMP
customer user IDs join correctly. Resolve gaps before relying on CAC or
payback by campaign.See Identity mapping.
Review the first payback report
Open the payback report after the initial sync. Compare CAC, revenue,
trial-to-paid conversion, renewal rate, and cohort sizes against your source
of truth before enabling recommendations.See Payback reports and
Validate CAC payback.
Set guardrails
Configure spend caps, excluded campaigns, approval thresholds, rollback
rules, and action types that require human review.See Guardrails.
Review recommendations
Start in read-only mode. FloKit can recommend budget shifts, creative pauses,
campaign changes, offer tests, and paywall experiments without executing
changes until your team approves them.See Action queue.
Production readiness checklist
- Revenue source is connected and historical sync is complete.
- Attribution source is connected and campaign metadata is visible.
- Core product events are arriving or imported.
- Identity join rate is high enough for campaign-level payback decisions.
- Payback report matches source-of-truth numbers within the team’s tolerance.
- Guardrails are configured before write access is enabled.
- First recommendations are reviewed manually before any automation is turned on.
Common blockers
| Blocker | What to check |
|---|---|
| No payback report | Revenue sync has not completed or there is not enough subscription history yet. |
| CAC does not match source of truth | Attribution cost import, campaign naming, or identity joins are incomplete. |
| Too many unattributed users | Subscription user IDs do not match MMP customer user IDs. |
| Recommendations look too broad | Guardrails, target markets, excluded campaigns, or payback window are not specific enough. |
| Funnel metrics are missing | Product events or paywall events are not being sent yet. |