No SDK Setup
Should You Use the No SDK Setup?
Use this setup if:
- You run ads only with TikTok, Google, or Meta (no Apple Ads, Snapchat, etc.)
- You already use the official SDK from your ad network (e.g., Meta SDK, Firebase SDK) or an MMP SDK
- You have set up Appstack to receive postbacks from your app
- You know which SDK in your app is responsible for updating the SKAN conversion value
- You have duplicate SKAN conversion value mapping for all Ad Networks you use (and inside Appstack)
How It Works
- Your app uses an official Ad Network or MMP SDK to update SKAN conversion values
- Appstack receives postbacks from your app (no Appstack SDK needed)
- Appstack matches postbacks to your ad campaigns and shows attribution data in your dashboard
Step-by-Step Setup
- Connect your ad network(s) to Appstack
- Add the Appstack endpoint to your app so postbacks are sent (see Send postbacks to Appstack)
- Ensure only one SDK in your app is responsible for updating the SKAN conversion value
- Set up your SKAN conversion value mapping in your ad network's dashboard (e.g., Meta Event Manager, TikTok Overview)
- Verify data: Check after 2 or 3 days to see if the postbacks are correctly matched to your ad campaigns. For new campaigns, this can take up to 3 days.
Where to find the SKAN conversion value mapping for Meta Ads?
Event Manager > Select your app > Settings tab > Edit Events
Where to find the SKAN conversion value mapping for Tiktok Ads?
Event Manager > Select your app > Overview tab > Configure SKAN
Where to find the SKAN conversion value mapping for Google Ads?
Coming soon
In the future, Appstack will provide ways to auto-import and check that the conversion value mapping is synchronized between Ad Networks and Appstack. For now, this need to be done manually.
Real-World Examples
✅ Correct Setups
1. Meta Ads (Meta SDK only)
- John runs ads only Meta Ads for his app "John AI"
- He uses the Meta SDK
- Meta integration is connected to Appstack and he sees campaign data such as spend for Meta in the dashboard
- Appstack endpoint is added to his app and postbacks are received
- SKAN conversion value mapping is set up in Meta's Event Manager and duplicated inside Appstack
2. Google Ads + Meta Ads (Firebase SDK and Meta SDK)
- John runs ads on Google and Meta for "John AI"
- He uses both Firebase SDK and Meta SDK
- He has disabled SKAN updates in the Firebase SDK so only Meta SDK updates the SKAN value
- Meta and Google integrations are connected to Appstack and data appears in the dashboard
- SKAN conversion value mapping is consistent across both ad networks and duplicated inside Appstack
Always make sure only one SDK is responsible for updating the SKAN conversion value in your app!
❌ Incorrect Setups
1. Using unsupported ad networks
- John runs ads on Snapchat for "John AI" (Snapchat is not supported)
2. Meta Ads with no SDK
- John runs Meta campaigns but has no SDK or MMP SDK in his app (web campaigns won't send data to Appstack)
3. Multiple SDKs updating SKAN
- John uses both Firebase and Meta SDKs, but hasn't disabled SKAN updates in either. Both try to update SKAN, causing conflicts and unreliable data.
If more than one SDK tries to update SKAN, your attribution data will be inconsistent. Always ensure only one SDK is responsible for updating the SKAN conversion value.