Twitter configuration with AppsFlyer

1. Login to your Twitter Ad Account on ads.twitter.com
   
   

   

2. Clicking on the Ads button, at the top left corner of the page, redirects you to the Ads page.
3. Click the App Installs or App re-engagements option under Select the objective for your campaign.
   
   

   

4. Choose your app and fill in the details in the form. Click on Set up conversion recording under Choose an app to promote
   

   

5. In the next screen, click on Manage mobile measurement partner.

   

6. Click Manage AppsFlyer on the Manage mobile measurement partners page
   

   

   
   
7. A notification appears to inform you that you are about to leave Twitter Ads to go to the AppsFlyer website, click Go to AppsFlyer and login to your Dashboard:
   

   

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

   

9. Enter "Twitter" in the search field and click its logo to open Twitter's configuration window. The following screen appears:

   

10. Accept the Twitter Terms and Conditions for Mobile App Conversion Recording (MACT) and click Save Integration. 
    
    

    

11. Toggle Activate Partner and click on Login with Twitter.

    

12. Authorize AppsFlyer in the following window:
    

    

13. Activate the partner to enable attribution and reveal the integration tab.
    
14. Activate the required Twitter Ad account or accounts by clicking on the relevant check box and then Save & Close.
    

    
    You have now connected your Twitter account with AppsFlyer!
    Continue to Twitter's Attribution setup.

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

Ad account connected

Select the accounts to enable attribution.

Click-through attribution

This slider allows you 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 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.

Activate 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 events postback

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

1. Toggle In-App Event Postbacks to ON
2. Select the Sending Option for all SDK defined events.
   - Only events attributed to this partner for events coming only from users attributed to this partner
   - Events attributed to any partner or organic to have your entire user base available to be reported to the partner
3. Click Add Event to add an SDK Event to the list
4. Complete the following parameters:

Cost integration is not available for Twitter.

This section is relevant only if you are acting as a publisher, displaying ads of the partner to your users. 

Twitter (MoPub) provides ad revenue data as follows:

• Aggregate level data as described in this section.
• User-level by SDK 

User-level data by SDK

Before you begin:

• Integrate the user-level SDK in your app. 

To enable user-level data by SDK:

1. Go to the Ad Revenue tab.
2. Select User level integration.
3. Click Save Ad revenue.
   AppsFlyer will record Ad revenue reported by SDK. 

 To enable ad revenue aggregate data: 

1. Go to the Ad Revenue tab.
2. Select Aggregate integration.
3. Complete the credential and event fields:
   • API Key.
   • Inventory Report ID.
   • APP ID.
   • Event Source.
4. Click Save Ad Revenue.
   AppsFlyer will get ad revenue by API. 

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 setup 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 events data - only to the partner's own in-app events 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.

The user who is authorizing the integration between AppsFlyer and Twitter must have Twitter Account Administrator access.

All attributions are for campaigns on the selected account. If no accounts are selected, no in-app events or attributions are sent to Twitter, even if the in-app event mapping is still visible on the Twitter Configuration window.

No. The account owner sees all of the connected Twitter accounts. Team members only see their connected Twitter accounts.

You can disconnect AppsFlyer from your Twitter account. The following instructions assume that you are logged into your Twitter account using a desktop or laptop browser:

1. Sign in to Twitter.
2. On the left-hand side menu, click More > Settings and Privacy.
3. On the right-hand side, under Data and Permissions, click Apps and sessions.
4. Click AppsFlyer.
5. Click Revoke Access.

You can now go back to your AppsFlyer account and connect a different Twitter account if you want.

Yes, but it requires some actions on Twitter's end. But first some background is required:

You can connect only one handle (also known as a twitter user) to your AppsFlyer account. When you connect this handle, your Twitter Ads Account appears in the Twitter configuration in AppsFlyer dashboard.

If one of your team members also has a Twitter Ads Account, this means that they have a different handle than yours and cannot connect their handle to AppsFlyer. This is because your handle is the one that is already connected with the AppsFlyer account. In order for their Twitter Ad Account to also appear in AppsFlyer, they need to give your handle access as account administrator to their Twitter Ads Account.

Say your team member is Jenny and her handle is @jenny. Your handle is @nivi and is the handle that is connected to AppsFlyer. In order for her Twitter Ads Account to appear in the AppsFlyer account, she needs to give your handle access as account administrator to her Twitter Ads Account. Jenny needs to give access to Nivi to her Twitter Ads Account and not that other way around. When she does so, AppsFlyer looks at Nivi's handle, and sees all the ad accounts that it is associated with, Jenny's included.

Yes.
When an agency creates a new Twitter campaign, the campaign name must start with the agency name and an underscore (Example: "AgencyName_Campaign1").

For more details go here.

We are not allowed to provide raw data from Twitter to agencies, because agencies are regarded as third parties in terms of Twitter's terms of service.

If your app was subscribed to another attribution provider in the past, which was used to attribute Twitter installs, the following errors below when configuring Twitter on AppsFlyer's dashboard:

Error: The app is associated with a different attribution provider. Please associate it with AppsFlyer.

Alternatively, the following error may also appear:

Error: Error has occured while saving Twitter configuration. Some accounts failed to updated: XX Multiple provider ids to same (appid, conversionType) for event appid2872.

If the account selection does not save, this may be because the Twitter account in question was previously associated with a different provider at Twitter's end. To resolve this:

• Contact Twitter to remove the other provider from your end
• Select the Active Account name
• Click Save and Close.
• If this still doesn't solve the problem you will have to contact your previous measurement provider and ask to remove the past Twitter tags associated with your account.

By default Twitter does not provide campaign names on user level raw data. However, a permission to see campaign names on user level can be given if the advertiser has written approval from Twitter.
The Advertiser needs to ask Twitter's representative to send an approval email with the app package name and the advertiser's name to AppsFlyer (to the support team). Afterwards AppsFlyer is allowed to enable the Twitter user level data display.

For details of how to configure a Twitter Retargeting Campaign, click here.

Yes. If retargeting is turned on, AppsFlyer doesn't send the af_app_opened event postbacks to Twitter, as per Twitter's request.
Note that even if the Twitter setup window allows this selection, the af_app_opened postbacks are not sent with retargeting.

To deactivate the integration with twitter, uncheck all accounts and click Save & Close.

Yes!
To establish the connection between AppsFlyer and Twitter, the advertiser MUST select an active account in Twitter's partner page in AppsFlyer's dashboard, so at least one Twitter account is checked.
Afterwards, the agency needs to connect its Twitter account directly from its own agency dashboard.

Agencies cannot configure in-app events for Twitter. Similar to Facebook, these must be configured by the Advertiser.

Twitter requires attribution providers to delete its user-level data 3 months after the install. This means that the events performed by these users 3 months after they install the app are counted as organic.

Past aggregate data remains the same.