The Twitter Attribution integration with Localytics functions like most of our other ad network integrations. To understand how they work, check out the ad network attribution article.
Localytics can track the users you receive from Twitter campaigns as your Twitter mobile measurement partner. It’s important to note, due to Twitter policies, you cannot add Localytics as your Twitter mobile measurement partner if you already have a different mobile measurement partner.
So before you begin, make sure you don’t already have a mobile measurement partner set up with Twitter.
If you’re setting up Twitter attribution with an Android app, make sure you’re on Localytics SDK 2.6+. The Twitter integration used the Google Advertising ID (GAID) to identify new users, which is a feature of this SDK release.
To set up your attribution integration, head to the Attribution section of your Localytics dashboard. From there select the ellipsis, and choose Settings from the drop-down menu.
Don’t forget to make sure you’re setting up the correct app by checking the app’s name at the top of the page (ie, Android vs. iOS).
Check the box for Twitter. Enter your Twitter handle (@username) to authenticate. Make sure you’re authenticating whichever handle has access to all of the ad accounts you want to track through Localytics.
You’ll be asked to accept the terms and conditions. After accepting, your Twitter handle is authenticated within Localytics and all connected ad accounts will display.
Select the ad account(s) you want to track. Scroll down to the bottom of the page and hit the Save button. Then you’re all set!
Once you’ve integrated Localytics with Twitter, you’ll run any new ad campaigns through the Twitter interface. Just like all of the ad network campaigns, Localytics can’t know about the campaign until the first user is acquired. Once that’s done, the campaign will appear in Localytics.
|Twitter's single MMP policy||Twitter only allows a single mobile measurement partner to receive attribution data. If you have another partner connected to Twitter, you should expect that Localytics will not receive attribution data.|
|Authentication||Localytics asks you to authenticate your Twitter @handle when getting set up. We then display all ad accounts that the @handle is permissioned to view. If Localytics doesn't display an expected ad account, it's likely a permission issue. Additionally, Twitter authentication expires after 30 days, so you'll be prompted to authenticate again if you change your Attribution Settings. This doesn't affect your Localytics integration.|
|Twitter vs. Twitter Organic vs. Twitter Audience Platform||Twitter detects three types of installation: (1) installs from paid ads displayed in the Twitter app (reported as Twitter installs in Localytics) and (2) installs from unpaid tweets that generated a user (reported as Twitter Organic installs in Localytics), and (3) installs from paid ads displayed on the Twitter Audience Platform (reported as Twitter Audience Platform installs in Localytics).|
|Event Postbacks||We have a custom integration with Twitter that allows us to communicate to Twitter when selected post-install Events are recorded by Localytics. Per Twitter's specifications, each in-app event that you choose to post back to Twitter must be categorized into one of Twitter's event names. For more on setup and best practices, see our help article.|
|Comparing Localytics to Twitter data||There are a number of valid reasons Twitter might show a larger number of installs than Localytics due to different measurement techniques, as detailed in this help article.|