CONNECTIONS / Mobile SDK / Mobile SDK to Snap App CAPI
Your Mobile SDK and Firebase events, wired to Snapchat's App Conversions API.
Connect Mobile SDK and point Signals at your Mobile SDK and Firebase events; it posts in-app purchases and installs to Snapchat for app-campaign optimization as in-app events fire, hashed and consent-checked for Snapchat.
- ● mobile sdk → snap.capi :: live
- > read app_events rows=19,852
- hash sha256(email,phone) consent=filtered
- route snap deliver
- ✓ delivered · 14,690 matched
WHAT THIS ENABLES
Mobile SDK to Snap App Conversions
Mobile SDK to Snap App Conversions: your Mobile SDK and Firebase events, hashed and consent-checked, feed Snapchat as Signals posts in-app purchases and installs to Snapchat for app-campaign optimization as in-app events fire.
- In-app purchase and install events from your Mobile SDK and Firebase events activated for Snapchat, as Signals posts in-app purchases and installs to Snapchat for app-campaign optimization.
- App conversions Snapchat can optimize on server-side, drawn from your Mobile SDK and Firebase events by app teams on the Mobile SDK or Firebase.
WHAT FLOWS WHERE
Mobile SDK to App CAPI, mapped.
Each sync hands the in-app purchase and install events from your Mobile SDK and Firebase events to Signals, which hashes and filters every record, then Snapchat's App Conversions API logs the app conversions for mobile-ad-id matching.
Each sync hands the in-app purchase and install events from your Mobile SDK and Firebase events to Signals, which hashes and filters every record, then Snapchat's App Conversions API logs the app conversions for mobile-ad-id matching.
Built for the teams that own the number.
App teams on the Mobile SDK or Firebase activating Snapchat's App Conversions API straight from Mobile SDK and Firebase events.
From kickoff to verified events.
-
Connect
The Signals Mobile SDK or a Firebase export to feed Snapchat's App Conversions API, sized for mobile-ad-id matching.
-
Map
Signals receives your Mobile SDK and Firebase events, and its columns map to Snapchat's App Conversions API in the visual mapper, hashed and checked for mobile-ad-id matching.
-
Deliver
On each run, Signals pulls your Mobile SDK and Firebase events, posts in-app purchases and installs to Snapchat for app-campaign optimization, and forwards each app event as it arrives, with mobile-ad-id matching in the debugger.
What ships with this use case.
App conversions Snapchat can optimize on server-side on every run, as Signals reads your Mobile SDK and Firebase events and forwards each app event as it arrives.
In-app conversions counted on Snap from your Mobile SDK and Firebase events, with event volume steady because Signals forwards each app event as it arrives.
A per-run match report from Snapchat's App Conversions API on mobile-ad-id matching, straight out of your Mobile SDK and Firebase events.
What App CAPI actually receives.
- ● signals :: event payload
- > POST /v2/conversion source=mobile-sdk.app_events
- event_type "PURCHASE" · event_conversion_type "MOBILE_APP"
- hashed_email "2ac910…" · mobile_ad_id "8f2b…"
- timestamp 1784343575 · price 2844 · currency SAR
- ✓ accepted · match=true
Adjacent moves on the same stack.
from Mobile SDK
Mobile SDK to Meta App CAPI
Mobile SDK to Meta App Conversions: your Mobile SDK and Firebase events, hashed and…
Learn more
from Mobile SDK
Mobile SDK to TikTok App eAPI
Mobile SDK to TikTok App Events API: your Mobile SDK and Firebase events, hashed and…
Learn more
same use case
Adjust to Snap App CAPI
Adjust to Snap App Conversions: Signals reads your Adjust postbacks and posts in-app…
Learn moregeneric
Snap App CAPI
Server-side app conversion tracking into Snap, integrated with your MMP.
Learn moreAsked on almost every call.
How often does the Mobile SDK Snap App CAPI sync run?
Delivery tracks Mobile SDK, run by app teams on the Mobile SDK or Firebase: a near-real-time or scheduled sync of your Mobile SDK and Firebase events feeds Snapchat on that cadence. Each run forwards each app event as it arrives, so in-app conversions counted on Snap holds up on mobile-ad-id matching. The live debugger confirms every delivery inline.
What match rate should a Mobile SDK-sourced Snap App CAPI batch expect?
Match rate follows identifier coverage in your Mobile SDK and Firebase events, which app teams on the Mobile SDK or Firebase control, not Mobile SDK itself. A record with a current hashed email or phone matches for Snapchat; one missing both cannot. First-run feedback from App Conversions API pinpoints mobile-ad-id matching, the number app teams on the Mobile SDK or Firebase tune against.
NEXT STEP