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.

While the App Installs campaign type does not require the use of Branch links, you can insert Branch links into the Drive Traffic to App campaign type for ensuring proper routing including deferred deep linking.

Please ensure you choose Web Site as the FALLBACK TYPE and inserting the same Branch link into the provided field. If you choose App Install as the FALLBACK TYPE, users not properly routed will be sent to the App Store without the Branch link and deferred deep linking will not occur.

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 Ad Partner: 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.

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.

Info

Please make sure your Branch attribution windows for Snap match those in your Snap account. See the Troubleshooting section for more detail.

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

Info

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.

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=true as 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.

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.

When you reauthenticate, double check that you have selected the correct accounts. We will only pull cost data for accounts that you select as part of the authentication process.

Background:
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.

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.