Twitter Ads setup guide—integration and setup

At a glance: Integrate your Twitter Ads account with AppsFlyer to display attribution data of Twitter campaigns.

 Related reading

For a complete picture of working with Twitter Ads in AppsFlyer, check out these articles:

Connecting your Twitter Ads account to AppsFlyer

  1. Log in to your Twitter Ad Account on
    Clicking on the Ads button, at the top left corner of the page, redirects you to the Ads page.

  2. Click the App Installs or App re-engagements option under Select the objective for your campaign.


    Choose your app and fill in the details in the form. Click Conversion tracking under App.


  3. Click Go to AppsFlyer on the Conversion tracking page.


  4. A notification displays informing you that you're about to leave Twitter Ads to go to the AppsFlyer website. Click Go to AppsFlyer, and then log in to your Dashboard.


  5. Go to the dashboard of your app and click Integrated Partners on the left bar.


  6. Enter "Twitter" in the search field and click its logo to open the Twitter configuration window. The following screen displays:


  7. Accept the Twitter Terms and Conditions for Mobile App Conversion Recording (MACT). After accepting the terms, click Save Integration


  8. Turn on Activate Partner and click Login with Twitter.
  9. Click Authorize app to authorize AppsFlyer to use your account. 

  10. Activate the partner to enable attribution and display the Integration tab settings.
  11. Activate the required Twitter Ad account or accounts by selecting them and then Save & Close.


  12. You have now connected your Twitter account with AppsFlyer!

Twitter attribution setup

These are the tabs you'll use to set up the attribution. 

For a detailed description of the Partner Configuration Window Header, click here.

Integration tab

The Integration Tab is divided into different sections as described below. Partner must be activated on the first visit to enable its setup.

Ad account connected

Select the accounts to enable attribution.


Click-through attribution

Use the slider to set the maximum time from click to install. Only installs (first launches) that take place within the lookback window may be attributed to Twitter.

You can customize this value to 1-23 hours or 1-30 days. We recommend setting the click-through lookback window to 14 days, to align with Twitter.


View-through attribution lookback window

This slider allows you to set the maximum time from impression to the install. Only installs (first launches) that take place within this lookback window, following an ad impression, are attributed to Twitter, providing there was no other relevant ad click.

You can customize this value to 1-23 hours or 1-7 days. We recommend setting the View-through lookback window to 1 day, to align with Twitter.


Re-engagement settings

Twitter retargeting attribution includes only re-engagement conversions.

Turn on the Re-engagement attribution toggle to start attributing re-engagements for Twitter.

Re-engagement click-through lookback window

Set the duration of the Re-engagement click-through lookback window (the maximum period of time after an ad is clicked, within which a retargeted user can be attributed to the ad). You can set the value in hours (up to 23) or days (1-30).


Re-engagement view-through lookback window

To start attributing impressions of retargeting ads, activate Re-engagement view-through attribution.

Then, set the duration of the Re-engagement view-through lookback window (the maximum period of time after an ad is viewed, within which a retargeted user can be attributed to the ad). You can set the value in hours (up to 23) or days (1-7):


Re-engagement window

Set the duration of the Re-engagement window (the period when the user's in-app events are attributed to the retargeting media source). You can set the value in days (1-90), hours (up to 23), or even lifetime:


In-app event postback settings

In this section, you can map your AppsFlyer events with your partners via postbacks.


To configure in-app event postbacks: 

  1. Set the Partner ID (if required).
  2. Enable In-app event postback.
  3. Set the In-app event postback window, if required (read more about in-app event postback window configuration).
  4. If available, select whether to send events automatically or manually. Learn more about sending all events as they are.
  5. Click Add event to add an SDK or server-to-server event to the list.
  6. Complete the parameters required.
  7. [Optional] Click conditional-iae-postbacks-icon.png to set conditions for sending certain in-app events to the partner.
    Learn more about conditional in-app event postbacks
Parameter name Description
AppsFlyer event

The name of the event, as received by AppsFlyer either from the SDK integrated into your app or from server-to-server events.
Tip: Don't see the event you are looking for?

  • Make sure to activate the event on a device with a non-organic installation and recheck.
  • Type it in AppsFlyer event, then click Create custom. Read more about custom event mapping.
mapped to partner event

The unique name or ID of each event, as defined on the partner's side. Possible mapping configurations are:

  • Text field: Get the corresponding event ID from the partner.
  • Drop-down box: Select the most suitable pre-defined AppsFlyer event.
  • As is: Send the events as they are, without name mapping.
for users from

Select the sending option for the event:

  • This partner only: send postbacks only when this event is attributed to this partner.
  • All media sources including organic: send postbacks for events attributed to any partner and organic events.
  • No data (default): send only the event itself without the event value.
  • Values and revenue: send all the event parameters, including the revenue value (if exists in the event).
  • Values without revenue: send all the parameters excluding the revenue value.

Attribution link tab

Twitter does not use attribution links for attribution.


For all SRNs, such as Facebook, Apple Search Ads, Adwords, Twitter etc. this tab is not functional, as they do not use external attribution links.

Cost tab

AppsFlyer gets cost details by API. See the ad network cost integration table for full details on the supported dimensions, metrics, and features. Note: Cost data requires an Xpend subscription.

To enable the cost API:

View your cost API status and the last time AppsFlyer managed to pull matching cost data in either the cost (and ad revenue) integration status dashboard, or in the individual ad network dashboard.

Ad revenue tab

Ad revenue integration is not available for Twitter. To receive ad revenue data, integrate MoPub.

Permissions tab

In this tab, you can select the permissions to grant Twitter, whether the partner acts as an ad network, agency, or even both. Note that even if attribution is disabled for Twitter, the permissions tab is active and you can grant control to Twitter.

Use these toggles to give the ad network permissions to handle its own configuration for your app:

Ad network permissions

  • Allow to configure integration - permit the partner to set up the integration tab (except in-app event postbacks)
  • Allow to configure in-app event postbacks - permit the partner to setup in-app event postbacks mapping to itself on the integration tab
  • Allow access to your retention report - only to the partner's own retention data
  • Allow access to your aggregate loyal user data - only to the partner's own loyal user data
  • Allow access to your aggregate in-app event data - only to the partner's own in-app event data
  • Allow access to your aggregate revenue data - only to the revenue data attributed to the partner
  • Allow access to your Protect360 dashboard - only to the partner's own Protect360 data, and providing the feature is enabled for the advertiser

Learn more about granting ad network permissions.

Advanced Twitter setup video 

Was this article helpful?