Integration Summary
For more information, see Singular's iOS 14 and SKAdNetwork articles.
SKAdNetwork Postback Handling | Forwarding |
Conversion Value Decoding | Supported |
Campaign Data Enrichment | Supported |
Campaign Data Granularity | Campaign Name (Ad Campaign Name) Campaign ID (Ad Campaign ID) Sub Campaign Name (Ad Squad Name) Sub Campaign ID (Ad Squad ID) |
Introduction
Apple's SKAdNetwork framework allows ad networks (and advertisers) to receive some data about app installs attributed to their campaign without compromising the end-user's privacy. All the data about the app install and post-install events has to be contained in a single number from 0 to 63, called the conversion value.
Singular's SKAdNetwork solution offers several different ways to encode data into the conversion value, depending on whether the advertiser is interested in optimizing for revenue, retention, or other KPIs. Each encoding method is called a conversion model.
Snapchat's SKAdNetwork campaigns are supported through Singular managed these conversion models. By following the steps in this article, you'll be able to configure your Singular conversion model so that it is compatible with Snap SKAdnetwork campaigns and enable SKAdNetwork campaigns in your Snapchat Ads Manager.
Snapchat SKAdNetwork performance data is available in your aggregate SKAdNetwork reports, SKAdnetwork postback exports, and ETL data destinations.
Setup Instructions
1. Implement Singular's SKAdNetwork Solution
If you haven't done so yet, add SKAdNetwork support to your Singular SDK Implementation (see iOS SDK: Adding SKAdNetwork support) or S2S integration (see SKAdNetwork S2S Implementation Guide).
2. Configure a Conversion Model
In the Singular platform, go to Attribution > SKAdNetwork and select Add Conversion Model. Snapchat supports conversion event, revenue, and engagement models that you can configure through Singular. Learn more in the SKAdNetwork Conversion Models Dashboard FAQ.
3. Add a Snap App ID and Map Conversion Model Events to Snapchat Events
Snap requires apps have a Snap App ID for SKAdNetwork enabled campaigns. You can find more information on how to generate and retrieve your Snap app ID in Snapchat's help center article. Ensure that the Snap app ID is added to your partner configuration.
Next, ensure that all events used in the conversion model have been added and mapped to a Snapchat event (see Snapchat Partner Configuration). This is a prerequisite for the Singular conversion model to be recognized by Snapchat's optimization engine.
For example, if you have the following events configured in your SKAdNetwork conversion model, make sure they're mapped to a Snap event name in your Snapchat partner configuration.
SKAN Conversion Model Configuration: |
→ | Snapchat Partner Configuration: |
4. Configure SKAdNetwork in Snapchat Ads Manager
Continue to review Snap's instructions in their setup guide to finish your SKAdNetwork configuration and manage SKAdNetwork campaigns in Snapchat Ads Manager. To make sure that Singular receives Snapchat's SKAdNetwork postbacks, follow these steps:
- In the Apps section, make sure Snapchat is sharing postbacks with Singular:
- Select the SKAdNetwork campaign opt-in option when starting your campaign:
FAQ
Singular's SKAdNetwork report only shows results based on SKAdNetwork postbacks, while Snapchat's report may include both SKAdNetwork installs and IDFA-based installs.
To filter only SKAdNetwork results in the Snap Ads Manager dashboard, use the column SKAdNetwork App Installs instead of App Installs.
Starting September 13th, 2021, Snap forwarded SKAdNetwork postbacks will not contain the following SKAdNetwork postback fields:
- transaction-id
- campaign-id
- attribution-signature
- re-download
Additionally, a new field snap-transaction-id will be added to facilitate de-duplication, and the timestamp field will be updated to correspond to midnight PST of the day that Apple sent the postback to Snap.
Due to these changes, Snap SKAdNetwork conversions appear in Singular "Raw Data Report" and "SKAdNetwork Postback Export" with the following modifications:
- Removed SKAdNetwork fields will be shown as "N/A" in reporting
- Estimated Install Date will be calculated using the rounded Snap timestamp value
- All Snap SKAdNetwork Conversions are reported as re-download=false
- Snap SKAdNetwork forwarded postbacks will be de-duplicated according to snap-transaction-id
- Snap SKAdNetwork forwarded postbacks will not be validated against the attribution-signature