Overview
Amazon SAN (Self-Attributing Network) is Branch’s integration with Amazon Ads, and it enables you to measure and attribute app installs and in-app events from your Amazon DSP campaigns.
This integration uses Amazon’s Events Manager to pass conversion data in real-time, allowing you to:
Track mobile app installs and in-app conversions.
Attribute user actions back to Amazon advertising campaigns.
Optimize campaigns based on cost per install (CPI), cost per action (CPA), and return on ad spend (ROAS).
Create custom audiences based on app conversion signals.
For more information about Amazon's Events Manager and MMP integration, visit Amazon’s help documentation.
Platform support
Amazon SAN integration supports:
Android mobile devices
Amazon Fire TV devices
Amazon Fire Tablet devices
iOS devices (via SKAdNetwork)
iOS attribution with SKAN
iOS campaigns are supported through Amazon’s integration with Apple’s SKAdNetwork (SKAN). While Android and Amazon Fire devices use Amazon’s direct SAN integration, iOS attribution works through SKAN to comply with Apple’s privacy requirements.
SKAN is more limited than the direct SAN integration, so expect to see more comprehensive attribution on Android and Amazon Fire devices than iOS devices.
Learn more in our SKAdNetwork documentation.
Prerequisites
Branch setup requires:
A Branch account.
The Performance product enabled for your account. Learn more on our Products page, or contact our Sales team.
The Branch SDK integrated into your mobile app(s):
Amazon setup requires:
An Amazon Ads or Amazon DSP account.
Admin access to your Amazon Advertising console.
Access to your Amazon Advertiser ID (more information below).
Enable Amazon SAN
Step 1: Enable Amazon SAN in Branch
Visit the Ad Partners page in Branch.
In the search bar, type Amazon SAN and select this option from the results.
Select Save & Enable.
Step 2: Enter Amazon Advertiser ID
Enter your Amazon Advertiser ID in Branch when prompted during setup.
Find your Amazon Advertiser ID
For self-service advertisers:
Navigate to the Amazon Ads reporting console.
Look for your advertiser name in the Advertisers tab of the Amazon DSP Campaign Manager.
Copy your Advertiser ID from this location.
For managed service advertisers:
Managed service advertisers must contact their Amazon account manager to obtain their Amazon Advertiser ID.
Step 3: Configure event mapping
Navigate to the Event Config tab in Branch’s Amazon SAN partner settings.
Enable the events you want to share with Amazon Ads by toggling them on.
Map your in-app events:
In the left field, select the name of a Branch Event. You can use Standard Events, which are predefined by Branch, or Custom Events, which are defined by you.
Branch strongly recommends that you use Standard Events whenever possible.
In the right field, map it to one of Amazon’s predefined conversion events.
Repeat this for all events you want to track with Amazon.
Standard Amazon conversion event types
Amazon supports the following standard conversion event types for mapping:
Amazon event name | Description | Branch options |
|---|---|---|
| When a user adds a product to their shopping cart. |
|
| When a user submits an application. |
|
| When a user goes to the checkout page. |
|
| When a user supplies contact information, such as email, phone number, etc. | Custom Event |
| When a user performs an action that initiates a sales lead. |
|
| When a user makes a purchase for a service or product. |
|
| When a user visits a page on your website. |
|
| When a user performs a search for a product. |
|
| When a user signs up for a product or service. |
|
| When a user signs up for your service. |
|
| User events that don’t fit the definition of the standard conversion types. | Custom Event |
| When a user launches the mobile app for the first time. | Tracked by default by Branch SDK as |
For a full list of Branch Standard Events and how to track them, see Track Branch Events.
Important notes:
Only events that are properly mapped will be sent to Amazon. Unmapped events will not be shared with Amazon Ads.
For Amazon events that don't have a direct Branch Standard Event equivalent (like
CONTACTorLEAD), you can create a Custom Event with an appropriate name.The
MOBILE_APP_FIRST_STARTevent is automatically tracked by the Branch SDK as anINSTALLevent.
Step 4: Set attribution windows
Navigate to the Attribution Windows tab in Branch’s Amazon SAN partner settings.
Configure your attribution windows to match your campaign needs:
Click-through attribution window: Time window after click during which conversions are attributed to Amazon.
View-through attribution window: Time window after an impression during which conversions are attributed to Amazon.
Data sharing and privacy
Amazon has specific data handling requirements that Branch adheres to:
User-level data retention: Amazon user-level data is retained for attribution purposes according to Amazon’s policies.
Privacy protection: Amazon does not provide access to certain raw campaign data to protect end-user privacy.
Campaign details: When installs or events are attributed to Amazon, campaign details are available in Branch.
FAQ
What is Amazon SAN?
Amazon SAN (Self-Attributing Network) is Branch’s integration with Amazon Ads that allows you to measure and attribute app installs and in-app events from your Amazon DSP campaigns.
What platforms does Amazon SAN support?
Amazon SAN integration supports Android mobile devices, Amazon Fire TV devices, and Amazon Fire Tablet devices. iOS campaigns are not supported.
Do I need to create Branch Ad Links for Amazon campaigns?
No, Amazon SAN does not require you to create Branch Ad Links for tracking Amazon campaigns as Amazon’s platform automatically handles tracking.
What should I do if events are not showing up?
If you don’t see the events you’re expecting:
Verify event mapping is configured correctly.
Ensure the Branch SDK is properly implemented and events are being logged.
Check that postbacks are enabled for the events you want to share.
Confirm your Amazon Advertiser ID is entered correctly.
What should I do if I’m seeing attribution discrepancies?
If you’re seeing attribution discrepancies between Amazon and Branch:
Remember that Amazon is self-attributing and may have different attribution logic than Branch.
Check that the same events are being tracked consistently across both platforms.
Why is my campaign data not appearing?
If your campaign data is not appearing as expected:
Confirm Amazon SAN integration is enabled in Branch.
Verify you have active Amazon DSP campaigns running.
Allow up to 24 hours for initial data to populate.