Skip to content

Twitter Ads



Branch links can be used together with Twitter App Install Campaign ads, allowing you to track ad-driven installs on the Branch dashboard.

By connecting your Twitter Ads and Branch accounts, the following is enabled:

  • App conversion data collected by the Branch SDK sent to Twitter Ads for attribution.
  • Read-only access to install data (not cost/click/impression data) from Twitter Ads in your Branch account.



  • To track installs from Twitter Ads you should integrate the Branch SDK into your app OR send events via server to server integration including device IDs (Google AID or Apple IFA).
  • To use Twitter App Install Ads ensure you have:
    • URI schemes configured on iOS
    • URI schemes configured on Android
    • iOS App Store ID set
    • Android Package Name set
  • Ads is a premium product priced on Monthly Active Users. Sign up for the Ads product to enable this functionality.

Enable Twitter Ads for Measurement

Completing this section -- "Enable Twitter Ads for Measurement" -- will result in Branch sending app events to Twitter in order to attribute them back to Twitter ad campaigns. At this time, the integration does not support deep linking new users directly to content the first time they open your app.

  1. Navigate to the Partner Management tab and search for Twitter.

  2. Click Log in with Twitter


  3. Provide your Twitter credentials to begin the authorization process.

  4. Agree to the Advertising Terms & Conditions by checking the I agree to the Twitter Ads Terms & Conditions.


  5. Authorize Branch Twitter Ads Manager to use your account by clicking Authorize app.


  6. Select the ad accounts for which you want to run app install ads and click Save.


  7. Finally, to create a Twitter Ads link click the Create Twitter Link button in the top right hand corner.

Creating a Twitter Ads Campaign

Please follow Twitter's documentation on how to set up an App Install Ad Campaign.

Adding the Agency Tag to Campaign Name

Only agencies managing advertising campaigns on behalf of a client must prepend their Agency ID to the campaign name when creating advertising campaigns for Self-Attributing Networks (SANs).

Agency ID Required

Failure to append the campaign name with the Agency ID will result in any subsequent conversion not being properly attributed to the responsible agency.

Finding Your Agency ID

You can find your Agency ID under Account Settings in the Agency view.

Creating Your Agency Tag

Your agency tag must adhere to the following format:


Example Campaign with Agency tag


You can append the Agency Tag to either the beginning or the end of the campaign name.

Agency ID Removed When Exporting

The "~campaign" value displayed in exports/analytics will not include the agency_id. If you set up a campaign called test_campaign_agency_1234 in Facebook, and for any installs that came from that campaign, the "~campaign" value will be "test campaign".

Data Mapping between Twitter Ads & Branch

Branch maps the following data fields from Twitter Ads to Branch.

Twitter Data Branch Data Possible Values
n/a ~advertising_partner_name “Twitter”
tpn_attribution ~channel “Twitter” if null or last touch, or “Twitter Audience Platform” if TAP is last touch
engagement_time last_attributed_touch_timestamp 1455675372963
campaign_name ~campaign Light Bright Launch
campaign_id ~campaign_id 15292426
engagement_type last_touch_type CLICK or IMPRESSION
country_code ~user_data_geo_country_code US

Forwarding Events to Twitter Ads

Once you begin tracking events through the Branch SDK, we will start sending them to Twitter Ads. Twitter Ads has pre-defined events that map to pre-defined Branch events, listed below.

Branch will forward in-app events to Twitter Ads for campaign optimization. In addition, Branch will receive attribution data for rich analysis in the Branch dashboard.

Branch Event Name Twitter Conversion Type

In order to track these events, please refer to the v2 Event document for further information.

Twitter Data Sharing

Twitter has a data agreement with TUNE, and there are several layers of data that are concealed and can be exposed depending on who is accessing the data, and how the data is being accessed or exported.

Data Levels

Source Level > Source level is the source information including Partner name (Twitter Ads) and Partner Site (PROMOTED, ORGANIC, TAP).

Campaign Level > Campaign level includes campaign information such as Partner Campaign (campaign name), Partner Ad (Tweet ID), Partner Ad Group (Line Item ID)

Accessible Data


Branch API/UI:

  • Can access source and campaign level data by default in aggregate reports.
  • Source and campaign level data is not accessible in exports.


  • Can receive source level data with identifiers by default to an internal BI endpoint only Data can not be sent to third party analytics (see below for third parties) – the postback must be whitelisted for source level data by contacting support.
  • Campaign level data can not be sent to internal endpoints by default, please speak with your Twitter account manager for more information.


Only official Twitter partners can be attributed to and access Twitter data, those found at

Branch API/UI:

  • Can see source and campaign level data without identifiers for conversions they are attributed to (Twitter conversions that contain their attribution string in the campaign name).
  • Identifiers are never accessible.


  • Can receive source and campaign level data to their endpoints, and identifiers will be scrubbed out, no exceptions. This occurs by default and does not need whitelisting for a partner that has Twitter enabled on their integration.

Third parties (analytics providers)

  • Third parties (not client or official Twitter partner) can not receive Twitter data, no exceptions.
  • Postbacks set up to analytics providers will scrub source and campaign level information by default, identifiers will still pass through, and the conversions will appear organic to the third party.


Agencies can access Twitter data under the following circumstances:

  • If they have been provided full agency access by the client.
  • If they are an official Twitter partner.
  • If they append their agency attribution code to the Twitter campaign they are running.


Why am I seeing an onboarding error or not seeing an ad account?

  • You must have permissions to configure ad accounts.
  • You can only track apps that are configured with store IDs & package names in Link Settings.

What does the error Missing app event tags mean?

If you see the Missing apop event tags error while trying to enable the Twitter integration, please go through the onboarding flow in your Branch dashboard again. If you continue to see this error, please Contact Support.

What does the error Non-Branch app event provider configuration detected mean?

If you see the Non-Branch app event provider configuration detected error while trting to enable the Twitter integration, this means you have another Twitter Mobile Measurement Partner configured for your app/ad account combination. You must disable/delete any other MMP integration before enabling the Twitter integration in your Branch dashboard.

Why are there so many events?

We configure all permissible events at time of enablement so there’s no delay in tracking new events when they’re set up.

Why can't I view cost/click/impression data?

Twitter does not currently allow MMPs to access this data. We’re in active discussions. Please tell your Twitter AM if you’d like this data available in Branch.