Data Connectors
Fload pulls data from your app stores, revenue tools, and ad platforms through connectors. Each connector authenticates once and then syncs automatically on a regular schedule.
Available connectors
| Connector | Type | Setup method | What it unlocks |
|---|---|---|---|
| App Store Connect | App store | Invitation (no API key needed) | iOS metrics, reviews, subscriptions |
| Google Play | App store | Invitation (service account) | Android metrics, reviews, revenue |
| Apple Search Ads | Ad platform | Public key upload | iOS campaign performance |
| Meta Ads | Ad platform | OAuth | Facebook/Instagram campaign performance |
| Google Ads | Ad platform | OAuth | Google UAC performance |
| TikTok Ads | Ad platform | OAuth | TikTok campaign performance |
| Stripe | Revenue | API key | Web subscription data |
| RevenueCat | Revenue | API key | In-app subscription data |
| Amplitude | Analytics | API key | User behavior, funnels, retention |
| Mixpanel | Analytics | API key | Events, funnels, user profiles |
| PostHog | Analytics | API key | Product analytics, session data |
Messaging integrations
Fload also integrates with messaging platforms for alerts and notifications:
| Integration | Setup method | What it unlocks |
|---|---|---|
| Slack | OAuth | Alerts, reports, and AI chat in Slack |
| Discord | Bot token | Alerts and reports in Discord channels |
Connector health
Every connector has a health status and an operational status.
Health status:
- Healthy: syncing normally
- Degraded: some recent failures but still working
- Unhealthy: multiple consecutive failures; data may be stale
- Disabled: connector has been manually disabled
Operational status:
- Active: connector is running normally
- Error: credentials are invalid or a persistent issue occurred
- Paused: connector has been temporarily paused
- Validating: connector is being set up or credentials are being verified
If a connector goes unhealthy or enters an error state, Fload will alert you. Reconnecting or refreshing credentials usually resolves it.
Recovering a broken connector
Every connector in Fload now shares the same recovery UI. When something goes wrong, the connector card surfaces a specific, readable error (not a generic "failed") and gives you the right action inline:
- Reconnect: for ad platforms (Apple Search Ads, Meta Ads, Google Ads, TikTok Ads), expired or revoked tokens are detected automatically. Click Reconnect to re-run the OAuth/credential flow without rebuilding anything else.
- Sync now: if the connector is healthy but data looks stale, force an on-demand sync from the connector card. No waiting for the next scheduled window.
- Inline error messages: permission failures, rate limits, and platform outages each show a specific message explaining what happened and what to do.
Reconnect preserves everything you've configured on top of the connector. Ad account selection, campaign mappings, and any assigned apps survive the re-auth.
Syncing
- App Store Connect and Google Play: synced automatically on a regular schedule. Apple reports are typically available 1–2 days after the reporting date; Play reports 2–3 days.
- Ad platforms: synced via their official APIs. Data is usually available within hours.
- Stripe: synced via Stripe's API on a regular schedule.
- RevenueCat: synced in real-time via webhooks. Data appears instantly as subscription events occur, with no polling delay.
Initial sync after connecting a new account may take 15–60 minutes depending on how much historical data needs to be imported.
Adding multiple connectors
You can connect as many accounts as you need. Common setups:
- Multi-app founders: one App Store Connect connector per Apple developer account, one Google Play connector per publisher.
- Agencies: separate connectors per client's accounts.
- Cross-platform apps: one App Store Connect + one Google Play + one or more ad platform connectors.
Each connector is linked to one or more assets (apps) inside Fload.
Cross-platform app linking
During onboarding, Fload auto-detects iOS/Android pairs of the same app. You can link or unlink these pairs so they share a single asset, giving you a unified view of your cross-platform app's performance.