TikTok Ads Legacy Integration to SAN Migration


With TikTok For Business's new SAN Integration, there are specific steps necessary to migrate from the ads legacy integration to help reduce the number of discrepancies and issues with your campaign performance.

Migration Benefits

The new SAN integration unlocks several benefits:

  • Automated and streamlined way to measure attribution and support deep linking for your mobile apps
  • Ability to map Branch Custom Events to any TikTok Standard Event to share the SKAdNetwork Conversion Value with TikTok For Business.
  • Higher ROAS
  • Increased accuracy in attribution for complex campaigns


In order to enable TikTok For Business, you need to have completed the following:

  1. Admin access to both the Branch and TikTok For Bussiness accounts.
  2. Already have the Legacy Ads TikTok Integration enabled.
  3. Running TikTok For Business campaigns.

Migrate to the SAN Integration

1. Connect TikTok For Business SAN in Branch

In the Branch Dashboard under AdsPartner Management, find/search for TikTok For Business SAN. If you're already logged into the Branch Dashboard, you can also click here to go there directly.

Click the Log In With TikTok button and follow the prompts to authenticate your TikTok For Business account


Be sure to read and agree to the permissions requested by Branch in order to properly authenticate.


Once enabled, Branch will automatically pull your iOS/Android App IDs from the ads legacy integration as well the set attribution windows.


2. Configure Events

After authenticating your TikTok For Business account to Branch, navigate to the Events Config tab to configure your events.

It is important to add your event mappings here for Branch to properly send event metadata to TikTok For Business for attribution. You should see the events you are tracking with the Branch SDK here when you Add Event Mappings. For more details on the TikTok For Business and Branch event and metadata mapping, see the specifications here.



Additional Event Details

  • If you plan to run TikTok SKAN Campaigns and are tracking Custom Events, make sure you map your Custom Event to TikTok's Standard Event.

Click the blue Save button to set your event mappings.

3. Continue Running Campaigns

New campaigns do not need to be created in TikTok Ads Manager. The existing campaigns should automatically transition to this new SAN integration after the TikTok Events Manager starts showing "App SAN Ready" for the app.

As campaigns run, TikTok For Business will begin sending Branch attribution claims (click-through or view-through) after receiving events (INSTALL, PURCHASE, etc.).

4. Verify Metrics in the TikTok Ads Manager

In the TikTok Ads Manager, you can verify the status of your campaigns to make sure metrics are populating correctly.


5. Verify Metrics in the Branch Dashboard

In the Branch Dashboard under AdsAnalytics. Apply the following to the Events table:

Events Setting

Compare By

  • 广告合作伙伴(3p)
  • 广告合作伙伴
  • Campaign


  • last attributed touch type equals CLICK and IMPRESSION
  • ad partner (3p) equals a_tiktok

Table Columns

  • cost
  • 点击次数
  • 展示数
  • 安装次数
  • 重新安装
  • (any other standard/custom events you are tracking)

Once you see metrics come in for a_tiktok then Branch is receiving attribution claims from TikTok for Business through the SAN integration. You may still see metrics for a_tiktok_ads from previous attribution claims. Any new claims should report to a_tiktok.


Will there be duplicate campaign data in the Branch Dashboard while having both integrations enabled?

For the time being, there will be duplicate metrics in the Branch Dashboard for cost, click, impression, and SKAN data. Make sure you are filtering your data in the reports through the ad partner (3p) equals a_tiktok NOT a_tiktok_ads.

Do I need to disable the legacy integration after the SAN integration has been enabled?

No, you do not need to disable the legacy integration. Branch will take care of it on the back end at a particular date.

Will agency access change with the new SAN integration?

No, both agency and user access permissions will remain the same.