Snapchat App Conversions Through MMPs: AppsFlyer, Adjust, and the CAPI Fields
Snapchat app conversions reach Snap through two possible routes: the App Ads Kit SDK inside the app, or a mobile measurement partner - AppsFlyer, Adjust - forwarding measured events. The Conversions API sits inside this picture as the server-side channel whose fields and scoping rules the MMP integrations depend on.
The MMP Route
AppsFlyer and Adjust both maintain Snap integrations: the SDK measures the install and the in-app events, the MMP attributes them, and the measured conversions are forwarded to Snap through the partner connection. For an advertiser this is the configuration-light path - no direct CAPI pipeline for app events, with the MMP owning delivery. The trade is the usual MMP trade: attribution logic and raw event access live with the partner, and the events arrive shaped by the partner's measurement rules.
The App Identifiers the Conversions API Documents
| Field | What it is | Rule from Snap's reference |
|---|---|---|
madid | Mobile advertising ID (GAID/IDFA) | Normalize to lowercase; do not hash |
idfv | iOS vendor identifier | Highly recommended for app events; do not hash |
anon_id | Application install identifier | App events only; do not hash |
download_id | App download identifier | Do not hash |
These are the fields that make an app event matchable: the mobile ad ID and vendor identifiers are what Snap's attribution consumes for app campaigns. For web-plus-app funnels they complement the web match parameters - hashed email and phone, the IP with user agent - documented in Snapchat conversion events.
Deduplication and Scope for App Setups
Two Conversions API rules matter for MMP setups. Deduplication: client_dedup_id is honored across the pixel, the App Ads Kit, and the API within a 48-hour window, so an MMP forwarding events that the SDK also reports must share the dedup identity - otherwise the same install or purchase counts twice. Scope: the Conversions API token only sends events for pixels and app IDs in its own organization, which includes the app identifiers - the failure behind cross-org app setups. The token rules are in the Snapchat CAPI token guide, and the cluster map in the complete guide. For web funnels that also want server-side delivery without an MMP, MOST delivers tracker postbacks to Snap directly, and Pixel Activator covers single manual tests.
Frequently asked questions
Sources
Sources
- Manual testing and validation: Pixel Activator fires free test events while you tune parameters.
- Automated delivery: Most routes conversions from your tracker or CRM continuously, with deduplication and retries handled.