Create a Twitter Campaign

Contents

The following document defines the process for creating a Twitter campaign within Kochava. This setup allows Kochava to send installs to Twitter to allow for attribution.

Data Needed Before Beginning Process:

Twitter Ads account.

NOTE: If during the connect process an error is shown “No twitter ads account connected to your account” it means that the account has been authenticated with is not an ads account and can not run traffic.

App Bundle ID (i.e., Package Name).

NOTE: The App Bundle ID may be entered when the app was added to Kochava. If the App Bundle ID is entered when an app is created or edited, you do not need to add the ID to the tracker.

Use Cases for Twitter Campaign:

An app marketing campaign needs to be created for Twitter network.

NOTE: The Twitter setup process for iOS and Android is similar and therefore this document will cover the setup for both operating systems, with specific differences noted.

NOTE: Twitter is one of Kochava’s network partners which claims its own installs, this type of network is known as a SAN. Twitter will always claim its own installs, with the exception of mobile web inventory or any inventory that does not have access to a device ID. This means that conversions claimed by Twitter may subsequently be attributed by Kochava to other networks. It is therefore expected for Kochava to show fewer installs than are shown in the Twitter system.

CAUTION: With a recent Twitter update, a key/value pair was added called is_granular_data_sharing_allowed. When the value for this key is set to false, the Advertiser has not yet agreed to Twitter’s AMM terms. Kochava will honor the claim, but be forced to redact the Twitter campaign metadata associated to the row level device details. If/when Twitter’s AMM terms are agreed to (in the Twitter platform), Kochava will be able to replace those redacted values with the campaign metadata.

NOTE: Twitter users have the ability to control what is shared with Twitter partners which can lead to inconsistencies in censoring, regardless of the AMM agreement.

Twitter AMMP:

Kochava HIGHLY recommends that advertisers join the Twitter Advanced Mobile Measurement Program (AMMP) > Mobile App, Conversion Tracking & Audience Manager > Advanced Mobile Measurement Program Agreement Form. Once the advertiser has joined AMMP, Twitter can provide the data needed for accurate measurement and you may receive expanded device-level data after granting Twitter the right to perform an audit to ensure that Twitter data is being used exclusively for measurement purposes. This is consistent with common practices throughout the industry. By joining Twitter’s AMM Program, you will receive more complete device-level data, which will in turn reduce the discrepancy between our report and Twitter’s dashboard. If AMMP is not joined, discrepancies between Kochava and Twitter reporting will exist.

Authenticating with Twitter

Log into a Twitter Ad Account.
Click App Installs
Choose an app to promote.
If Conversion Tracking has not been set up for the app, Click Set up conversion tracking.

NOTE: If previous campaigns have been set up within Twitter Ads, Conversion Tracking may be navigated to by Selecting Tools > Conversion Tracking.

Click Go to Kochava.

NOTE: After clicking on Go to Kochava, a pop-up box will appear warning that you will be redirected from Twitter Ads to Kochava. The page will be redirected to the Kochava log in screen.

A. Link to set up Conversion Tracking.

In the pop-up box, Click Go to Kochava.
Enter Kochava log in credentials.
Select Account Options > Twitter Connect.
Click Connect for the desired Twitter account.

NOTE: Multiple Twitter accounts may be connected at the same time, for more information refer to Twitter’s Multi-User login support documentation.

Create a Twitter Campaign

BEST PRACTICES: It is HIGHLY recommended that a Tracker ID be appended to the partner campaign name e.g., the campaign name within the Twitter UI. The Tracker ID can be easily located within Kochava’s Campaign Manager, expand the section below for instructions on locating the ID.

Locate Tracker ID:

Once a tracker has been created, navigate to Campaign Manager.
Locate and click on the desired Campaign.
Select the desired Segment.
Locate the desired Tracker, and Check the associated selection box.
Locate and copy the Tracker ID.

Log in to Kochava.
Select the desired Account and App.
Select Engagement > Campaign Manager.

Feature Note: To add this menu item to your Favorites Menu, select the “+” sign that appears when you hover over the menu. The Features Menu provides quick access to your most frequently visited areas of the Kochava UI.

Click + Add (Tracker) or Select Segment Tools (⋮) > Add a Tracker.
Enter a unique Tracker Name.
Select Tracker Type > Acquisition. (default setting)
Select Select a Network > Twitter:
1. Twitter—Android (Android)
2. Twitter—iOS (iOS)
Select the desired Twitter account(s).

NOTE: Multiple Twitter accounts may be selected.

Select Default Tracker:
1. On
2. Off (default)

NOTE: Selecting On will allow SAN network traffic to funnel to the default tracker when no tracker ID is present. If a default tracker is not set up and the tracker ID is not appended to the partner campaign name, that data will be bucketed in the most recently set up tracker for that network.

Enter the App Bundle ID (If not entered during app creation/editing). For further information about locating the Bundle ID, click here.

NOTE: The App Bundle ID may be entered when the app was added to Kochava. If the App Bundle ID is entered when an app is created or edited, the ID will be automatically populated into the tracker.

A. Campaign and Segment selection/creation section.
B. Select a Twitter Account. Multiple Accounts may be selected.

Select a Target Event. (optional)
Select a Post-Click Attribution Window. (optional)
Select a Post-View Attribution Window. (optional)
Click Save. (If no further trackers need to be created).
Click Save & Add Another Tracker. (If additional trackers need to be created).
Click Save & Create Postback. (To navigate directly to the Partner Configuration page).

BEST PRACTICES: Attribution Windows – When Twitter trackers are created in the Kochava dashboard, lookback windows are set within Kochava and the Twitter dashboard. These lookback windows should align or Twitter can surface installs in their platform but not report those installs to Kochava based off the lookback windows set in Kochava.

NOTE: In order to post events back to Twitter, a reengagement tracker must be created regardless if the event is a true reengagement event or simply posting an event back to Twitter. For more information on creating a reengagement tracker, refer to our Create a Twitter Reengagement Campaign.

Create a Twitter Postback Configuration

Select Apps & Assets > Partner Configuration.

Feature Note: To add this menu item to your Favorites Menu, select the “+” sign that appears when you hover over the menu. The Features Menu provides quick access to your most frequently visited areas of the Kochava UI.

Click + Add a Configuration.
Select Network Partner > Twitter:
1. Twitter—Android (Android)
2. Twitter—iOS (iOS)
Click Go.
Click Install > 🖉 (Edit).
Enter the App ID:
1. iTunes App ID (iOS)
2. Package Name (Android)
Select a Delivery Delay. (optional)
Select the number of Retry Attempts. (optional)
Click Save.

SKAdNetwork Reporting

Under Apple’s SKAdNetwork Twitter will receive the postbacks directly from Apple, and then forward those SKAdNetwork postback to Kochava with some additional metadata for reporting.

NOTE: For additional questions related to how SKAdNetwork impacts your Twitter campaigns, refer to their support documentation.

NOTE: The Kochava – Twitter API hooks programmatically pull in your conversionValue model and schema

Attribute	Format	Description
in_timestamp	string	Install timestamp in milliseconds. This is when the postback was received by Twitter.
transaction_id	string	Unique ID used for deduplication tied to a conversion.
app_id	string	ID for the advertised app.
redownload	boolean	Flag for a reinstall.
source_app_id	string	ID of app where ad was served. Twitter’s App ID for Twitter Ads inventory. For more information on TAP refer to Twitter Audience Platform (TAP).
conversion_value	string	0-63, must be sent in incremental values by the advertised app. This will be null for v1 postbacks or v2 postbacks without a conversion value due to Apple’s privacy minimum threshold.
conversion_value	string
version	string	Version of install validation postback. Will be 1.0 if source app uses pre-iOS14 SDK and 2.0 for all apps running iOS14.
partner_campaign_id	string	Twitter campaign ID.
partner_campaign_name	string	Twitter campaign name.
sub_campaign_id	string	A reference to the line item in Twitter Ads that produced the ad event.
sub_campaign_name	string	Name of the line item in Twitter Ads that produced the ad event.
fidelity_type	boolean	SKAdNetwork parameter indicating the type of conversion. 0 indicates a view, 1 indicates a click.
did_win	boolean	SKAdNetwork parameter indicating if the forward was the last touch before action or an influencing ad exposure (true, false).

Parameter Mapping:

in_timestamp maps to timestamp
partner_campaign_id maps to campaign_id
partner_campaign_name maps to campaign_name
sub_campaign_id maps to line_item_id
sub_campaign_name maps to line_item_name

Updated on February 20, 2025

Was this article helpful?

Yes No

Marketers

Developers

Partners

Create a Twitter Campaign

Data Needed Before Beginning Process:

Use Cases for Twitter Campaign:

Authenticating with Twitter

Create a Twitter Campaign

Create a Twitter Postback Configuration

SKAdNetwork Reporting

Parameter Mapping:

Was this article helpful?