Support Home > Campaign Management > Create a Twitter Campaign

Create a Twitter Campaign


Feature Summary: 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.
  • App Bundle ID (i.e., Package Name).

 

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. It also means that Kochava does not impose the lookback window setup within Kochava on install claims, so the effective lookback window for post-impression and post-click installs will be the settings configured within the Twitter UI.

 

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 end user has requested that their data not be shared with the advertiser and Kochava will reject the claim and move to the next best attribution fit. Kochava HIGHLY recommends that advertisers join the Twitter Advanced Mobile Measurement Program (AMMP). 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’ll 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

  1. Log into a Twitter Ad Account.
  2.  

     

  3. Click App Installs
  4.  

     

  5. Choose an app to promote.
  6. If Conversion Tracking has not been set up for the app, Click Set up conversion tracking.

     

    A. Link to 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.

  7. Click Go to Kochava.
  8.  

     

    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.

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

     

    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

  1. Log in to Kochava.
  2. Select the desired Account and App.
  3. Select Links > Campaign Manager.
  4.  


     

  5. Click Add a Tracker or Select Segment Tools () > Add a Tracker.
    1. Select the Campaign.
    2. Select the Segment.

    NOTE: In order to streamline the Campaign/Segment/Tracker creation process a feature has been added to allow the creation of campaigns and segments while creating a new tracker. For more information about creating a campaign or segment while adding a new tracker, refer to our Create an Install Campaign support document.

     

     

  6. Enter a unique Tracker Name.
  7. Select Tracker Type > Acquisition. (default setting)
  8. Select Select a Network > Twitter:
    1. Twitter—Android (Android)
    2. Twitter—iOS (iOS)
  9. Select the desired Twitter account(s).
  10. NOTE: Multiple Twitter accounts may be selected.

  11. Enter the App Bundle ID. For further information about locating the Bundle ID, click here.
  12. Select a Target Event. (optional)
  13. Select a Post-Click Attribution Window. (optional)
  14. Select a Post-View Attribution Window. (optional)
  15. Click Save. (If no further trackers need to be created).
  16. Click Save & Add Another Tracker. (If additional trackers need to be created).
  17. Click Save & Create Postback. (To navigate directly to the Partner Configuration page).
  18.  

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

 

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

  1. Select Apps & Assets > Partner Configuration.
  2.  


     

  3. Click Add a Configuration.
  4. Select Network Partner > Twitter:
    1. Twitter—Android (Android)
    2. Twitter—iOS (iOS)
  5. Click Go.
  6.  

     

  7. Click Install > Postback Tools () > Edit.
  8. Enter the App ID:
    1. iTunes App ID (iOS)
    2. Package Name (Android)
  9. Select a Delivery Delay. (optional)
  10. Select the number of Retry Attempts. (optional)
  11. Click Save.
  12.  

    A. Enter App ID (iOS) or Package Name (Android)


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