Attribution
Conversion APIs
Send installs, trials and purchases back to Meta, Google, Snap, TikTok and Pinterest, so their ads optimise on real results.
Ad networks optimise on the results they hear about. Fictura can send each network your installs, trials and purchases from its server, so you don't need each network's SDK in your app.
Providers
| Provider id | Network | Notes |
|---|---|---|
meta_capi_app | Meta Conversions API for App Events | Needs a dataset linked to your app. |
google_app_conversions | Google Ads app conversions | Needs a Link ID from Google Ads (as an "other provider" link). |
snap_capi | Snap Conversions API | Needs your Snap App ID. |
tiktok_events_app | TikTok Events API for apps | Your TikTok rep has to allowlist your account first. |
pinterest_capi | Pinterest Conversions API | Needs a conversion token. |
Each one is off until you save its credentials in Dashboard → Attribution → Settings (/dashboard/attribution/settings).
What is sent
| Event | Extra data |
|---|---|
install | — |
trial_started | — |
purchase | Value and currency. |
- The IDFA, GAID and ATT status go only when the person allowed tracking.
- EEA consent flags are passed through unchanged. Without them, Google models conversions instead of counting them (Google).
Deliveries
Every send is logged as a delivery: provider, event, the install it was for, status and the network's response.