Branch can help track your Snap Ad campaigns through our integration with Snap.
Snap is a self-attributing network (SAN).
Snap campaign tracking can show you how many installs and conversion events were attributed to Snap, allowing you to make informed decisions with your advertising dollars.
Before you begin, be sure the following is confirmed.
- First, the Branch SDK must be integrated into your app, for both iOS and Android.
- You must also collect the IDFA on iOS, or the AAID on Android. For specifics, refer to the set up guide for iOS and Android respectively.
- Make sure to track all necessary events through the SDKs, with instructions here
Authenticate with Snap¶
- Navigate to the partner management tab and search for Snap.
Select the tile with the ghost logo.
Log in with Snapchat.
Read and accept the Snap Advertiser Agreement terms if you haven't already.
You must be an Admin on the Branch account in order to accept the Snap Advertiser Agreement terms. You must accept the terms to track your Snap advertising.
Log in to Snap. Once logged in, accept permissions and click
Due to an issue with Snap Login, if you see the Snap "My Account" screen after logging in, you'll need to manually return to the Branch dashboard at https://dashboard.branch.io/ads/partner-management/a_snap?tab=settings. Click
Log in with Snapchatagain in the same browser, and you should see the
Continuebutton instead of the login screen.
Continueto return to the Branch dashboard.
Confirm the ad accounts that you would like to track.
Click Save to finish.
Note: The Snap measurement integration requires you to have configured your Android and iOS apps on the Link Settings page. If those have not been set up, you will not be able to track ads and you may see a validation warning.
View Attribution on Dashboard¶
All the attribution can be visible on the Branch dashboard summary page. All installs and opens registered from this channel will automatically be tagged with
Snap. Other analytics tags will reflect the campaign, ad squad and ad names you set up in the Snap Ads dashboard.
Note that these stats are limited to the date range at the top of the page. You can expand the range if you'd like.
Changing attribution windows¶
You can edit your attribution windows for Snap only. With this, you can preserve your Account Level Attribution Windows, but the attribution windows set for Snap will take precedence for Snap campaigns.
Please make sure your Branch attribution windows for Snap match those in your Snap account. See the Troubleshooting section for more detail.
Mapping of Branch event names to Snap events¶
Branch supports sending Standard and Custom Events to Snap. Here are the mappings for Branch events to Snap events.
By default, all events in the below table will be sent to Snap.
|Branch event name||Snap event name|
The below events can be sent to Snap by registering custom events that exactly match the Branch custom event name below. Snap does not accept other custom events, so they will not be sent to Snap.
|Branch custom event name||Snap event name|
Branch provides the following cost metrics for this ad partner:
|Analytics Tag||Description||Used for|
|Cost||Total cost (spend) for those dimensions (analytics tags, user data, time range), regardless of cost model||Understanding the total amount spent|
|eCPI||cost / installs||Normalizing spend per install, to understand the average price of an install across networks or over time|
|eCPC||cost / clicks||Normalizing spend per click, to understand the average price of an click across networks or over time|
|eCPM||cost / (impressions / 1000)||Normalizing spend per thousand impressions, to understand the average price of 1000 impressions across networks or over time|
|eCPA||cost / purchases [includes web and app purchases]||Normalizing spend per purchase, to understand the average price of a purchase across networks or over time|
|Return On Investment (ROI)||(revenue-cost / cost) * 100||Deriving return on investment, to understand the percentage "profit" made on ad spend|
|Return On Ad Spend (ROAS)||(revenue / cost) * 100||Deriving return on investment by understanding the percentage revenue multiple for a given unit of spend|
All cost data is ingested in local currency and then translated to USD on the dashboard using the exchange rate for that currency on the day the data is stored. In effect, this means the dashboard shows the amount that campaign cost converted to USD at the time it ran.
- Snap Ads Manager time zones are set at the time your ad account is created. You can see your Snap time zone in your Snap Ad Account Settings, but you cannot change it. You can change your Branch dashboard time zone in Account Settings to match.
Verify your Snap attribution windows match your Branch attribution windows. Ask your Snap account manager for your attribution windows. Your Branch windows are visible either in Link Settings (global windows) or in the Attribution Windows section of the Snap entry in Ads Partner Manager. Snap windows can be configured under "Customize Columns" in the Snap UI.
When deep linking, create a link via the Branch dashboard. If you are running an app campaign, please ensure your link has
%24deeplink_no_attribution=trueas a query parameter to remove that link's ability to claim attribution, otherwise the link may claim attribution over the SAN claim. The link will still deep link.
- Snap's reporting API does not provide any "compare by" functionality outside of the ads analytics tags. So, you cannot compare Snap click + impression data by platform, OS or country, for example.
Branch Cost data not matching the Ad Partner dashboard¶
Please ensure that you've selected the same time zone in your Ad Partner's dashboard and your Branch dashboard.
CPI metric doesn't match between Ad Partner and Branch, although cost metric does¶
Branch's last-click attribution model can lead to differences in install counts for Branch vs self-attributing networks (SANs) that in turn cause differences in CPI metrics. Verify whether your cost and install metrics match the Ad Partner's dashboard. If there is an install discrepancy, it is likely legitimate and due to differences in install counts, where Branch's number is more accurate. If the discrepancy is very large, investigate causes of install discrepancies through the usual troubleshooting steps.
Cost, click and impression data is all missing¶
Cost, click and impression data for SANs are generally sourced from Partner APIs (unless Branch impression pixels or links are being intentionally used for attribution, for example, in web campaigns). When you enable a SAN, you authenticate with your provider. Branch uses this authentication to retrieve click, cost and impression data. If the authentication token expires (for example, if you reset your password, or the partner force resets your token), then you may not see click, impression or cost data. In this case, simply reauthenticate and that will refresh your token.
Cost data is missing or incorrect for certain "compare by" breakdowns¶
Downstream events, such as installs, should always have the full range of compare by options in the dashboard. However, clicks, impressions and cost data for SAN are often imported via Partner APIs. These APIs do not necessarily provide the same breakdowns for cost data that Branch supports with raw install events, so there may be cases where the Branch Dashboard cannot compare by the same dimensions for cost data vs install data.
Exporting Snap Data¶
Data integrations will never include events attribution to Snap. This is because we cannot share device-level Snap attribution data with third parties.
There are many ways to access data pertaining to Facebook.
You can see analytics on impressions, clicks, installs, opens and conversion events on various pages of the Branch Dashboard, as well as the Query API.
We cannot send device-level Snap attribution data to third parties. Thus we cannot send events attributed to Snap via Data Integrations. Please instead consider analyzing this data in-house (using Webhooks, the Data Export API, or CSV Exports), or using the Branch Dashboard for all of your analytics and attribution needs.