Create an X Install Campaign

Contents

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

Data Needed Before Beginning Process:

X Ads account.
App Bundle ID (i.e., Package Name).

NOTE: X is one of Kochava’s network partners which claims its own installs, this type of network is known as a SAN (Self-Attributing Network). X 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 X may subsequently be attributed by Kochava to other networks. It is therefore expected for Kochava to show fewer installs than are shown in the X system.

CAUTION: With a recent X 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 X’s AMM terms. Kochava will honor the claim, but be forced to redact the X campaign metadata associated to the row level device details. If/when X’s AMM terms are agreed to (in the X platform), Kochava will be able to replace those redacted values with the campaign metadata.

X AMMP (Advanced Mobile Measurement Program):

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

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

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

Authenticating an X Account

Log into Kochava
Navigate to Account Options > Account Configurations > X Connect.
Select Connect.

Select Sign In.
Enter your X Account credentials.
Select Authorize App.

NOTE: Upon authorizing the app, you will be routed back to the Kochava dashboard where you will see your authorized X account listed in the X Connect page.

Select the Action toggle to enable the account.

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

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

NOTE: Only a user who has authenticated an X account in the Kochava UI will be able to proceed with the steps outlined below as the X authentication is tied to an individual user in Kochava.

Create an X Install Tracker

BEST PRACTICES: It is HIGHLY recommended that a Tracker ID be appended to the partner campaign name e.g., the campaign name within the X 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.

Select the desired Campaign & Segment, or create new ones.
Click + Add (Tracker).
Enter a unique Tracker Name.
Select Tracker Type > Acquisition. (default setting)
Select a Network > X:
1. X—Android (Android)
2. X—iOS (iOS)

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.

NOTE: A destination URL is not necessary as X handles the click redirects.

Only a user who has Authenticated with X will have access to the “X Accounts and Setup” section to complete the Tracker Setup.

Select the desired X account(s).

NOTE: Multiple X accounts may be selected as long as they have been authenticated.

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.

Select a Target Event. (Default to “Install” for Acquisition Trackers)
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 X trackers are created in the Kochava dashboard, lookback windows are set within Kochava and the X dashboard. These lookback windows should align or X can surface installs in their platform but not report those installs to Kochava based off the lookback windows set in Kochava.

Create an X Install Postback Configuration

Select App Configurations > 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 Partner.
Select Network Partner > X:
1. X—Android (Android)
2. X—iOS (iOS)
Click Next.
Verify Status: Active.
Click Save.
Expand the X Partner Configuration.
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.

NOTE: As soon as you save your Install Postback for X, Kochava’s system will begin sending Install claim requests to X as soon as Installs are tracked for the app in Kochava.

As soon as the first Install claim request is sent to X for the app, you will see the Install event appear in your Events manager page in your X Ads Account dashboard as seen in the screenshot below.

NOTE: In order to create an App Install campaign in your X Ads account for a given app, you first need to have the install event connected to your X Ads account. This means that you need to go through all the steps outlined in this document up to this point in order to configure and launch an X App Install campaign. If you attempt to create an X App Install campaign without going through the steps listed above, you will see the message below when you select your App to promote.

“To use the app installs goal with this app, you need to add an install event via your mobile measurement partner.”

NOTE: The same applies to post-install events. Once they are sent to X, you will see them show up in your X Ads Event manager page. In order to send post-install events to X, a Kochava reengagement tracker and corresponding event postback must be configured. For more information on creating a reengagement tracker, refer to our Create an X Reengagement Campaign.

NOTE: After you have successfully Authenticated your app with your X account, you will be able to select the Manage MMP button in your X Ads Event manager page and will see Kochava appear as “Connected”.

SKAdNetwork Reporting

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

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

NOTE: The Kochava – X 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 X.
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. X’s App ID for X Ads inventory. For more information on TAP refer to X 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.
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	X campaign ID.
partner_campaign_name	string	X campaign name.
sub_campaign_id	string	A reference to the line item in X Ads that produced the ad event.
sub_campaign_name	string	Name of the line item in X 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 June 26, 2026

Was this article helpful?

Yes No

Marketers

Developers

Partners