Skip to main content
FloKit should fit around the systems a subscription app already uses. The integration story should make it obvious where each signal comes from and what job it does.

Source categories

CategoryExamplesWhy it matters
Ad platformsMeta, Google, TikTok, Apple Search AdsSpend, budgets, campaigns, creatives, bids, and delivery
Attribution and MMPAppsFlyer, Adjust, BranchUser-source joins, campaign attribution, install quality
Subscription stackRevenueCat, Adapty, app stores, StripeTrials, subscriptions, renewals, cancellations, refunds
Product analyticsAmplitude, Mixpanel, PostHog, FirebaseActivation, onboarding, paywall, and retention events
WarehouseBigQuery, Snowflake, RedshiftSource-of-truth joins and finance-approved reporting
Creative systemsAsset folders, campaign naming, creative metadataCreative fatigue and retained-value analysis

Integration promise

For marketing docs, this page should show that FloKit does not replace the monetization stack. It adds the acquisition intelligence and controlled action layer on top of it.

First-pass setup

1

Choose source of truth

Decide which system owns revenue, cohort joins, campaign names, and user identity.
2

Connect read-only data

Start with warehouse exports, platform reports, or webhooks before enabling any write action.
3

Map identifiers

Confirm how campaign IDs, creative IDs, user IDs, and transaction IDs join across systems.
4

Validate payback

Compare FloKit metrics to finance-approved reports before trusting action recommendations.