> For the complete documentation index, see [llms.txt](https://help.branch.io/llms.txt). # Enable Amazon SAN (New) > Integrate Amazon SAN with Branch to track app installs and events, ensuring real-time data flow and accurate attribution for your Amazon DSP campaigns. ## Overview Amazon SAN is Branch's integration with Amazon Ads. It enables you to measure and attribute app installs and in-app events from your Amazon DSP campaigns, and to share conversion signals with Amazon's Events Manager in real time. Amazon is a self-attributing network (SAN), which means Amazon handles attribution directly and reports results to Branch via API rather than receiving traditional Postbacks from Branch. Branch Ad Links are not required to track Amazon campaigns. For more information about integrating ad partners in general, visit our [Ad Partner Integration Guide](https://help.branch.io/marketer-hub/ad-partner-integration-guide-new.md). > **Note: this guide is for new Branch** > > Please note that this guide is about integrating Amazon SAN in the [new Branch experience](https://help.branch.io/marketer-hub/new-branch-overview.md). For information on Amazon SAN in legacy Branch, visit our [legacy guide](https://help.branch.io/marketer-hub/amazon-san.md). ### Partner capabilities | Capability | Details | | --- | --- | | Company type | Self-attributing network (SAN) | | Deep linking | Supported ([Universal Links](https://support.apple.com/en-us/102062), [App Links](https://developer.android.com/training/app-links)) | | Attribution | Click-through attribution, View-through attribution, Engaged View-through attribution | | Ad campaign types | Amazon DSP campaigns | | Supported platforms | Android, iOS (via SKAdNetwork), Amazon Fire TV, Amazon Fire Tablet | | Cost ingestion support | Supported (via API) | | Pricing models | CPM | | Engagement Builder Ad Partner Integration | Not available | ## Before you begin To set up the Amazon SAN integration, you need: - Ad partner integrations enabled for your Branch account. Availability varies by Branch plan. See [Branch pricing](https://www.branch.io/pricing/) or contact your Branch representative. - A Branch account with access to **Configuration > Ad Partners** and admin permissions to enable and configure integrations. - An Amazon Ads account with admin access. ## Enable Amazon SAN To begin, navigate to **Configuration > Ad Partners > Amazon SAN**. ### Find your Amazon Advertiser ID Your Amazon Advertiser ID is required to complete setup in Branch. **Self-service advertisers:** Find your Advertiser ID in the **Advertisers** tab of the Amazon DSP Campaign Manager. **Managed service advertisers:** Contact your Amazon account manager to obtain your Advertiser ID. > **Caution: use a numerical ID** > > The Amazon DSP advertiser account ID is a numerical ID. Other account ID types, such as alphanumeric IDs (e.g., `acamzn1.ads-account.g.1aygvwt6dzo4yl6vqbdmkg71z`), should not be entered. If you are unable to locate your numerical account ID, please contact your Amazon representative. ### Connect with Amazon SAN 1. Select **Connect with Amazon SAN**. 2. In the **Manage account** modal, select **Sign in with Amazon SAN**. 3. In the **Before you sign in** dialog, select your **Amazon Ads API region** from the dropdown, then select **Sign in with Amazon SAN** to complete authentication. 4. Back in the **Manage account** modal under **Account Settings**, enter your **Advertiser ID**. 5. Select **Save**. ## Configure attribution To configure attribution windows, select the **Attribution windows** tab on the Amazon SAN page. By default, Amazon SAN uses your global app attribution settings. To set attribution windows specific to Amazon SAN, enable the **Override global app settings** toggle on the **Attribution windows** tab. ## Configure events To configure event mappings, select the **Event config** tab on the Amazon SAN page. Map your Branch in-app events to Amazon's standard conversion event types. Only mapped events are sent to Amazon Ads, unmapped events are not shared. For more information about event mapping, see [Configure events](https://help.branch.io/marketer-hub/ad-partner-integration-guide-new.md#configure-events) in the general [Ad Partner Integration Guide](https://help.branch.io/marketer-hub/ad-partner-integration-guide-new.md). The full Branch-to-Amazon event name reference is in [Data mappings](#data-mappings) below. > **Note: use Branch Standard Events when possible** > > Branch strongly recommends mapping to Branch Standard Events whenever a direct equivalent exists. For Amazon event types that don't have a Branch Standard Event equivalent, create a Branch Custom Event with an appropriate name. ## Verify your data After enabling Amazon SAN, confirm that data is flowing correctly: - **In Branch** [**Liveview**](https://app.branch.io/testing-and-monitoring/events): confirm that events from your app appear in real time and are attributed to Amazon SAN. This is the fastest way to confirm SDK events are firing. - **In Branch** [**Analysis dashboards**](https://help.branch.io/marketer-hub/analysis-data-sources-new.md): review attributed installs, events, and cost data where `Ad Partner Name = Amazon SAN`. - **In Amazon Ads console**: confirm that conversion events are appearing in your Amazon Ads account. > **Note: allow time for initial data** > > Allow up to 24 hours for initial campaign data to populate after enabling the integration. ### Cost data To verify that cost data is flowing into Branch, you need to: - Complete all implementation steps above. - Have live campaigns running for the ad network. #### Important cost data limitation Please note that **geo-based reports** may not match the total campaign spend. Campaign spend is pulled from Amazon’s campaign-level reporting and includes all campaign traffic. Geo spend is pulled from Amazon’s geo-level reporting and only includes traffic where Amazon was able to determine the user’s geographic location. Some impressions may not be eligible for geo reporting due to privacy settings, VPN usage, or limited location signals. As a result, Geo spend should be used for geographic breakdowns only, while **Campaign spend should be used as the source of truth for total spend reconciliation.** ## iOS and SKAdNetwork iOS campaigns are measured through both Apple's SKAdNetwork (SKAN) framework and Amazon's MMP API. SKAN operates regardless of a user's App Tracking Transparency (ATT) choice, and returns aggregated postback data, subject to Apple's privacy thresholds and reporting limitations. Through Amazon's MMP API service, attribution depends on identifier availability. When the IDFA is present, Amazon can attribute deterministically. When it isn't, Branch still forwards the conversion, and Amazon attributes it probabilistically based on IP. ## Data mappings ### Event names | Branch event name | Amazon event name | | --- | --- | | `INSTALL` | `MOBILE_APP_FIRST_START` | | `COMPLETE_REGISTRATION` | `SIGN_UP` | | `SUBSCRIBE` | `SUBSCRIBE` | | `ADD_TO_CART` | `ADD_TO_SHOPPING_CART` | | `SEARCH` | `SEARCH` | | `PAGEVIEW` | `PAGE_VIEW` | | `PURCHASE` | `CHECKOUT` | | Branch Custom Event | `CONTACT`, `LEAD`, `APPLICATION`, `OFF_AMAZON_PURCHASES`, `OTHER` | ## Data limitations - **iOS SKAN**: Raw user-level data is not available through SKAdNetwork, only aggregated SKAN data is returned, subject to Apple's privacy thresholds. - **User-level data**: Amazon does not provide access to certain raw campaign data to protect end-user privacy. - **Time zone**: Ensure your Branch reporting time zone matches your Amazon Ads account time zone to minimize reporting discrepancies. To update your Branch time zone, go to [**Configuration > App Settings > General**](https://help.branch.io/account-hub/general-new.md#timezone). ## Troubleshooting > **Events are not appearing in Amazon Ads** > > Verify that event mapping is configured correctly in the **Event config** tab. Only events that are mapped are sent to Amazon, unmapped events are not shared. Also confirm that the Branch SDK is properly implemented and that events are being logged. > **Attribution discrepancies between Branch and Amazon** > > Amazon is a Self-Attributing Network and uses its own attribution logic, which may differ from Branch's. Verify that attribution windows in Branch match the settings in your Amazon Ads account. See [Common Sources of SAN Reporting Discrepancies](https://help.branch.io/marketer-hub/common-sources-of-san-reporting-discrepancies.md) for the full list of expected differences. > **Campaign data is not appearing in Branch** > > Confirm that Amazon SAN is enabled and that your Amazon Ads account is connected. Verify that you have active Amazon DSP campaigns running. If the integration was recently enabled, allow up to 24 hours for data to populate. ## Additional resources For more information, visit the following articles: - [Ad Partner Integration Guide](https://help.branch.io/marketer-hub/ad-partner-integration-guide-new.md) - [Enable SKAdNetwork](https://help.branch.io/marketer-hub/enable-skadnetwork.md) - [Amazon Events Manager and MMP integration](https://advertising.amazon.com/help/GF97FJUFXBDM32P4)