> ## Documentation Index > Fetch the complete documentation index at: https://docs.flokitai.com/llms.txt > Use this file to discover all available pages before exploring further. # Customer onboarding > Run a structured onboarding process from kickoff through the first trusted payback report. Use this guide to onboard a new subscription app into FloKit. The goal is to move from kickoff to a trusted payback report without mixing test data, skipping identity validation, or enabling automation too early. Onboarding should be treated as an operating rollout, not only a technical integration. Growth, data, finance, and product should agree on the source of truth, target payback window, and safety guardrails before recommendations are used for live spend decisions. ## Outcomes At the end of onboarding, the team should have: * A production workspace scoped to one app. * Revenue and attribution sources connected. * Core product and funnel events mapped or planned. * Identity joins validated across subscription, attribution, and product systems. * A first payback report reviewed against source-of-truth numbers. * Guardrails configured before write access or automation. * A clear owner for ongoing recommendation review. ## Roles | Role | Responsibilities | | ------------- | ---------------------------------------------------------------------------------------- | | Growth owner | Defines acquisition goals, target payback, markets, campaign scope, and approval process | | Data owner | Validates source mappings, identity joins, metric definitions, and warehouse alignment | | Product owner | Confirms onboarding, paywall, offer, and lifecycle events | | Finance owner | Confirms revenue source, refund treatment, and reporting tolerance | | Admin owner | Manages workspace access, API keys, and integration permissions | ## Pre-kickoff checklist * Production app name, platform, bundle ID or package name, and store URLs. * App Store Connect, Google Play, Stripe, or warehouse revenue access. * AppsFlyer or Adjust access, if attributed CAC is required. * Ad platform access, if recommendations will include campaign or budget actions. * Identifier strategy across anonymous users, app users, subscription customers, and MMP customer IDs. * Target payback window, such as 30, 60, or 90 days. * Initial markets, channels, campaigns, and excluded campaigns. ## Onboarding process Create one workspace for the production app. Keep staging, sandbox, QA, and demo data in separate workspaces so payback reports are not polluted by test users or fake transactions. Add the app name, platform, store URL, bundle ID or package name, primary markets, and default currency. These values help scope integrations, reports, and recommendations to the right product. Connect App Store Connect, Google Play, Stripe, or a warehouse source first. Revenue is the anchor for payback, ROAS, cohort LTV, renewals, refunds, and churn. Connect AppsFlyer or Adjust so FloKit can read install source, campaign, ad set, creative, country, and cost context. Confirm the minimum event set for onboarding and paywall analysis. Start with paywall views, trial starts, subscription starts, cancellations, and important onboarding milestones. Review anonymous IDs, app user IDs, subscription customer IDs, and MMP customer user IDs. Resolve join gaps before relying on campaign-level CAC or payback. Compare CAC, revenue, trial-to-paid conversion, renewal rate, and cohort sizes against your MMP, subscription source, warehouse, or finance reporting. Configure budget caps, excluded campaigns, approval thresholds, action types, rollback triggers, and owners before enabling write access. Begin in read-only mode. Review recommendations manually until the team agrees that FloKit's signal is accurate enough for controlled execution. ## Data quality acceptance criteria | Area | Acceptance criteria | | ----------- | ------------------------------------------------------------------------------------------- | | Revenue | Historical sync completed and totals match source of truth within the agreed tolerance | | Attribution | Campaign, ad set, creative, country, and cost fields are populated for paid cohorts | | Identity | Join rate is high enough for campaign-level decisions and unattributed users are understood | | Events | Required lifecycle events are arriving with stable names and timestamps | | Reports | Payback report can be explained by growth and data owners without unresolved metric gaps | | Guardrails | Spend caps, exclusions, approvals, and rollback triggers are configured | ## Common onboarding blockers | Blocker | How to resolve it | | ---------------------------------- | ----------------------------------------------------------------------------- | | No payback report appears | Confirm revenue sync completion and enough subscription history | | CAC does not match source of truth | Check attribution cost windows, currency, campaign naming, and imported spend | | Too many unattributed users | Review ID mapping between subscription customer IDs and MMP customer user IDs | | Product funnel is incomplete | Add missing paywall, trial, subscription, and onboarding events | | Recommendations are too broad | Tighten markets, campaigns, excluded campaigns, and action types | | Stakeholders disagree on numbers | Document source-of-truth rules before using recommendations | ## Launch readiness Do not move beyond read-only recommendations until: * The first payback report has been reviewed by growth and data owners. * Known data gaps are documented. * Guardrails have an accountable owner. * Finance or leadership understands the reporting tolerance. * Write access is intentionally configured, if needed. ## Related pages * [Set up FloKit without an app release](/guides/no-app-release-setup) * [Get your first payback report](/guides/first-payback-report) * [Set safe guardrails before automation](/guides/safe-guardrails) * [Action queue](/product/action-queue)