> ## 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.

# Integrations

> Connect the tools your subscription app already uses.

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.

```mermaid theme={null}
flowchart LR
    subgraph Sources["Data sources"]
        SUB["Stripe / App Store / Google Play / RevenueCat / Adapty / Superwall<br/>subscription evidence"]
        MMP["AppsFlyer / Adjust<br/>install attribution"]
        ADS["Ad platforms<br/>spend data"]
        EVENTS["Server-side events API"]
        WH["Data warehouse<br/>historical cohorts"]
    end
    INGEST["FloKit ingestion<br/>(API pull + webhooks)"]
    JOIN["Identity join +<br/>cohort model"]
    REPORTS["Payback reports and LTV"]
    QUEUE["Action queue<br/>(approval-gated)"]
    SUB --> INGEST
    MMP --> INGEST
    ADS --> INGEST
    EVENTS --> INGEST
    WH --> INGEST
    INGEST --> JOIN
    JOIN --> REPORTS
    REPORTS --> QUEUE
```

<CardGroup cols={2}>
  <Card title="AppsFlyer" icon="bullseye" href="/integrations/appsflyer">
    Install attribution and campaign source
  </Card>

  <Card title="Adjust" icon="sliders" href="/integrations/adjust">
    Attribution, cohort exports, and campaign analytics
  </Card>

  <Card title="Stripe" icon="credit-card" href="/integrations/stripe">
    Web subscription payments and revenue events
  </Card>

  <Card title="App Store Connect" icon="apple" href="/integrations/app-store-connect">
    iOS sales, subscription reports, and proceeds
  </Card>

  <Card title="Google Play" icon="android" href="/integrations/google-play">
    Android subscription reports and financial data
  </Card>

  <Card title="Data Warehouse" icon="database" href="/integrations/warehouse">
    Historical cohort exports from BigQuery, Snowflake, or Redshift
  </Card>
</CardGroup>

***

## 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

| Signal                    | Source                                                                                 | Required    | What it enables                        |
| ------------------------- | -------------------------------------------------------------------------------------- | ----------- | -------------------------------------- |
| Subscription events       | Stripe, App Store Connect, Google Play, RevenueCat, Adapty, Superwall, manual evidence | Yes         | LTV, renewal rate, payback             |
| Install attribution       | AppsFlyer, Adjust                                                                      | Yes         | CAC by campaign and creative           |
| Spend data                | Ad platforms (Meta, Google, etc.)                                                      | Yes         | ROAS, payback curves                   |
| Product and funnel events | Server-side events API                                                                 | Recommended | Onboarding, paywall, and offer signals |
| Historical cohorts        | Data warehouse                                                                         | Optional    | Backfill and validation                |

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:

| Mode | What it means                                | First-client use                    |
| ---- | -------------------------------------------- | ----------------------------------- |
| A    | Public/manual evidence only                  | Allowed for onboarding and strategy |
| B    | Provider import or live read                 | Preferred first-client path         |
| C    | FloKit executes checkout/webhook/entitlement | Gated until provider checks pass    |

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](/send-data/event-taxonomy).