Skip to main content
FloKit reads from the systems you already run. No new SDK is required for most integrations — connect your existing subscription platform, MMP, and ad stack, and FloKit assembles a unified picture of acquisition cost, conversion quality, and revenue payback.

AppsFlyer

Install attribution and campaign source

Adjust

Attribution, cohort exports, and campaign analytics

Stripe

Web subscription payments and revenue events

App Store Connect

iOS sales, subscription reports, and proceeds

Google Play

Android subscription reports and financial data

Data Warehouse

Historical cohort exports from BigQuery, Snowflake, or Redshift

​
Connection modes

FloKit supports three integration modes depending on the data source and the action being taken. Read-only FloKit pulls data via API on your behalf. No write permissions are needed. All reporting, LTV modeling, payback curve, and recommendation features operate in read-only mode. Use this for all subscription, attribution, and store integrations. Webhook receiver FloKit receives real-time events pushed from Stripe, Apple, or Google. Webhook delivery reduces event latency from hours to seconds for subscription lifecycle events. Recommended alongside the pull-based API integration for all subscription platforms. Approval-based write FloKit prepares actions — budget reallocations, bid adjustments, creative pauses — and executes them only after a human approves each change in the FloKit dashboard. This mode requires explicit write permissions scoped to the relevant ad platform. No write action runs automatically without approval.

​
What FloKit needs to run

Subscription events and install attribution are the minimum required for FloKit to produce payback analysis. Spend data is pulled directly from your connected ad platforms. Product events and warehouse data improve model accuracy and cohort precision, but are not required to get started.

​
Monetization readiness

FloKit separates evidence from execution: Paddle is a Mode C checkout candidate, not the default first-client path. Provider readiness is shown per connection in the FloKit dashboard under Integrations → Payments; the GET /api/monetization/provider-profile endpoint that previously reported it has been removed. For the full event taxonomy FloKit expects, see Event taxonomy.