|Partner Type||Self-attributing Ad Network|
|View-Through||Supported for Installs|
|Click Tag||No (Self-attributing)|
|Receiving All Installs||Recommended (Self-attributing)|
|Receiving All Events||Recommended (Self-attributing)|
Singular is a Twitter Mobile App Conversion Tracking (MACT) Partner and therefore can allow you to track and measures installs and re-engagements for your Twitter campaigns.
Setting Up Twitter Attribution Tracking
To set up Twitter attribution tracking:
- Integrate the Singular SDK or S2S (see Getting Started with the Singular SDK/S2S).
- Create and provision your Twitter Ads account. Note that the account must be Twitter Ad enabled. For more information, see Twitter Help or contact your Twitter account manager.
Proceed to set up your Partner Configuration on Twitter:
Note: This next step will provision Singular as an app Mobile App Conversion Tracking partner, associated with your Twitter ads account. Only one MACT partner can be provisioned for an app at any given time.
- Accept Twitter's Terms and Conditions.
Log in and link your Twitter Ads account with Singular. This should be the Twitter Ads account that is permitted to manage campaigns for all your Twitter ad accounts if you have more than one.
Select the authorized accounts that are promoting your app and select Next.
Configure the Twitter integration like any other partner.
By default, installs are reported to Twitter to enable install attribution tracking. Select the Enable Re-engagement Tracking checkbox to have sessions reported to Twitter, to allow Singular re-engagement tracking.
You can also have Singular report post-install events to Twitter for conversion optimization and reporting. To enable this option, you must map the event to the desired Twitter Conversion event.
Partner Data Policies
As a Twitter Mobile App Conversion Tracking partner, Singular adheres to the following data handling requirements required by Twitter:
Twitter user-level data is removed after 6 months of original attribution. After 6 months, users attributed to Twitter as treated/marked as "Organic" and reflected as such in both aggregate and user-level reporting in Singular.
Twitter's end-users have the ability to opt out of sharing data with thirds parties. Singular respects this value by not reporting these users as attributed to Twitter in user-level data (BI postbacks, exports), but they are still included in aggregate reporting.
Twitter Reporting in Singular
|Singular Dimension||Name in Twitter
|Tracker Campaign Name||Twitter Campaign Name||“MyCampaign”|
|Tracker Campaign ID||Twitter Campaign ID||2xzbi|
|Tracker Ad Group Name||Twitter Line Item ID||aied2|
|Tracker Creative ID||Tweet ID||351166379755724804|
Singular also tracks attributions from organic tweets through the Twitter integration. These appear in reports under the source "Twitter Organic".
Why do I see differences between Twitter data in my report and in user-level exports?
Twitter allows users to opt out of sharing data with third parties. Singular respects this value by not reporting these users as attributed to Twitter in user-level data (BI postbacks, exports), but they are still included in aggregate reporting.