Setting Up Twitter Attribution Tracking

Last Updated: May 03, 2016 09:06PM PDT
Apsalar's integration with Twitter now allows you to accurately track the conversion and monetization of your Twitter campaigns along with all of your other network sources.

Currently, Apsalar supports tracking Twitter App Install Campaigns, Twitter App Engagement Campaigns, organic Twitter installs, and Twitter Audience Platform traffic.

Note: The Twitter integration should be enabled from your main Apsalar account.

Setting Up Install Tracking for Twitter

1. Create a Twitter App Install Campaign.

Using Twitter's helpful guide, create your App Install Campaign. If you have any questions about configuring a Twitter campaign, please see their thorough support documentation or open a Twitter Support Ticket from your Twitter Ads Dashboard using the Help? button in the top right corner.

2. Authorize Apsalar to Access your Twitter Campaigns

  • In your Twitter Ads Dashboard, select the Conversion tracking option at the top of the page
  • Select the Mobile App Events tab.
  • On the resulting page, click the Go To Apsalar button located under the Apsalar logo.
  • You'll be re-directed to Apsalar's site where you'll need to read and accept Twitter's Mobile App Conversion Tracking agreement. Please note, you will be prompted to log-in to your Apsalar account if not already signed in.
  • After accepting the agreement by clicking the checkbox and then selecting the Sign in with Twitter button, you will be redirected back to your Twitter Ads Dashboard.
  • On the resulting Twitter page, you must click the Sign In button to complete the process. Your Apsalar and Twitter integration will now be able authorized.

3. Configure Postbacks to Twitter

In order for Twitter Campaigns to be tracked, you must configure postbacks to Twitter. If not configured, campaigns will not be tracked. To configure postbacks to Twitter, please use the steps below:
  • Navigate to the Attribution Tracking page and select the Twitter Integration tab.
  • Click the Create New Postback button.
  • On the resulting Create New Postback page, enter the necessary information for your Install postback:
    • Application: Select applicable application
    • Event Type: Install
    • Postback Status: Active
    • Attribution Rules: Send all events from all sources
    • Twitter Conversion Type: INSTALL
    • (iOS Only) iTunes Application ID: Your iTunes App ID
  • Click the Create Postback button.
  • Your newly created postback should now appear in your Apsalar account and on your Twitter Ads Dashboard under the Conversion Tracking section.

4. Adjust Twitter Attribution Windows.

To help ensure compatible attribution counts between Twitter and Apsalar, adjustments to the attribution windows for your Twitter campaign are required. After configuring postbacks to Twitter from your Apsalar account, this change can be made using the short steps below:
  • In your Twitter Ads Dashboard, navigate to the Conversion Tracking section.
  • Here, all of the postbacks you've configured from Apsalar to Twitter should be listed in the Mobile App Events tab. Next to the applicable entry, select the Edit option.
  • On the resulting Settings page, make the following adjustments:
    • Post-engagement attribution window: 30 days
    • Post-view attribution window: Off
    • Assisted conversion attribution: Unchecked
    Please note, you may use different settings than the suggestions above, but it will result in reporting discrepancies between Apsalar and Twitter.

5. Track your Twitter Campaigns on your Apsalar account.

After completing the above steps, you can begin tracking your Twitter campaigns in your Apsalar account from all applicable reports, including your Traffic Report.

In Apsalar's reporting, the name, group, creative, and source information will map like so:
Apsalar Label Twitter Value Example
Campaign Name Campaign Name:Campaign ID Sample App Installs:00a00
Group Name Twitter Line Item ID 00aa0a0
Creative Tweet ID 000000000000000000
Source/Publisher N/A - Static value of Twitter, Twitter Audience Platform Twitter, Twitter Audience Platform

Please note, for organic Twitter installs, the Campaign Name and Group Name will be Twitter Organic.

Please note, for Twitter Audience Platform installsthe Publisher value will be Twitter Audience Platform.

 

Reporting Additional Events to Twitter

Twitter can accept notifications for events beyond installs for their own conversion tracking. Using their pre-defined Conversion Types, you can configure postbacks for any of your revenue or custom Apsalar Events to Twitter.

To send Twitter notification of custom or revenue events:

1. Configure the Postback

  • Navigate to the Attribution Tracking page and select the Twitter Integration tab.
  • Click the Create New Postback button.
  • On the resulting Create New Postback page, enter the necessary information for your revenue or custom event postback:
    • Application: Select applicable application
    • Event Type: 'Any revenue event' or 'Custom event'
      • If Custom event, select the applicable event from the resulting drop-down menu
    • Postback Status: Active
    • Attribution Rules: Send events attributed to Twitter for all campaigns
    • Attribution Lookback: 30 days
    • Twitter Conversion Type: Select applicable Conversion Type from the drop-down menu.
    • (iOS Only) iTunes Application ID: Your iTunes App ID
  • Click the Create Postback button.
  • Your newly created postback should now appear in your Apsalar account and on your Twitter Ads Dashboard under the Conversion Tracking section.

2. Adjust Twitter Attribution Windows.

To help ensure compatible counts between Twitter and Apsalar, adjustments to the attribution windows on Twitter are required. After configuring your revenue or custom event postback to Twitter from your Apsalar account, this change can be made using the short steps below:
  • In your Twitter Ads Dashboard, navigate to the Conversion Tracking section.
  • Here, all of the postbacks you've configured from Apsalar to Twitter should be listed in the Mobile App Events tab. Next to the applicable entry, select the Edit option.
  • On the resulting Settings page, make the following adjustments:
    • Post-engagement attribution window: 30 days
    • Post-view attribution window: Off
    • Assisted conversion attribution: Unchecked
    Please note, you may use different settings than the suggestions above, but it will result in reporting discrepancies between Apsalar and Twitter.

Frequently Asked Question Regarding Twitter Ads and the Apsalar Integration

What is an organic Twitter install?

Twitter can track app installs that originate from a Twitter Card, in addition to tracking installs that originate from your Twitter campaigns. After you've implemented Twitter Cards, if a follower clicks on the included content link and then downloads and launches your app, Twitter will count that as an organic Twitter install. All organic Twitter installs will show the Campaign Name and Group Name as Twitter Organic in your Apsalar reports.

How long before my Twitter campaign information is available on my Apsalar account?

Once you've setup tracking, as outlined above, you should immediately begin to see data for your approved Twitter campaigns. Please note there is 24 hour approval period for new campaigns created on your Twitter Ads Dashboad. Please contact Twitter's Support Team, via the Help? button on your Twitter Ads Dashboard, if you have any questions regarding the approval period for your Twitter campaign. 

Can I send Twitter attribution information from Apsalar to an Ads API Partners or my own servers?

Twitter's terms of use do allow sending anonymised, aggregate attribution information to other recipients, including Ads API Partners from Apsalar. You can find the relevant postback macros here.

Please note, if any of Twitter's specific campaign macros are included in a postback configured for traffic attributed to Twitter for an endpoint other than twitter.com, any device or custom user ID macros will not be populated. Please be sure to consider this restriction when configuring postbacks for Twitter attributed traffic.

More generic postbacks which include data attributed to other networks, such as a postback for all installs, will report Twitter installs as if they were organic if device ID or custom user ID macros and campaign macros are used. Postbacks such as these which contain campaign macros, but not device macros, will populate with the corresponding Twitter campaign data.

If you have any outstanding questions regarding configuring postbacks to 3rd parties or your own servers for Twitter campaigns, please contact Apsalar's Product Support Team for more help.

Does Apsalar support Custom ID Targeting with Twitter?

Custom ID Targeting can only be supported through an Ads API Partner. Please contact your preferred Ads API Partner or Twitter's Support Team,via the Help? button on your Twitter Ads Dashboard, for more information regarding Custom ID Targeting with Twitter.

What if I have access to multiple ads.twitter.com accounts?

If your Twitter account has access to multiple Twitter Ads accounts, you can control which Twitter Ads accounts will populate campaign data on your Apsalar account and receive your configured Twitter postbacks. To do so, simply click the Manage Account Access  button located on the Twitter Integration tab:

On the resulting screen, you can select which of your ads.twitter.com accounts are enabled to receive postbacks and send campaign data.
Please note, disabling all Twitter Ads accounts will cause all postbacks with Twitter as the recipient to be paused immediately. Disabled Twitter Ads accounts will no longer populate new campaign data in your Apsalar account.
.

Disabling the Twitter/Apsalar Integration

To disable the integration between Apsalar and Twitter for your account, click the Disable Twitter Integration  button located on the Twitter Integration tab:
 
Please note, clicking the Disable Twitter Integration button will cause all postbacks with Twitter as the recipient to be removed immediately. This action cannot be reversed. 

If you wish to restart your Twitter integration after disabling it, you will need to re-do all of the integration steps outlined above. 
support@apsalar.com
http://assets1.desk.com/
apsalarinc
Loading
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
about
Invalid characters found
/customer/en/portal/articles/autocomplete