Kochava Destination

1. If you have not already, create your app within the Kochava dashboard. Check out Kochava's documentation for information on creating your app.
2. From your Segment UI's Destinations page click on "Add Destination".
3. Search for "Kochava" in the Catalog, select it, and choose which of your sources to connect the destination to.
4. In the Kochava app, grab your Kochava App GUID (Globally Unique Identifier)
5. Copy the Kochava GUID into the Segment Destinations Settings UI under "API key".

Additional information from Kochava on setting up your first campaign within Kochava.

If you're not familiar with the Segment Specs, take a look to understand what the Track method does. An example call would look like:

1
[[SEGAnalytics sharedAnalytics] track:@"Item Purchased"
2
                           properties:@{ @"item": @"Sword of Heracles", @"revenue": @2.95 }];

Kochava is able to accommodate any post-install track event that is passed into its system. Events, when received for the first time, will auto provision into the Kochava dashboard. There is no need to create / provision the post-install track event ahead of time. When enabling Kochava in the Segment dashboard, you should expect to see any / all actions you're tracking with Segment appear in your Kochava account.

context.device.type (has value of 'ios' or 'android'), context.device.advertising_id (IDFA on iOS and adID on Android) and context.device.id are required in all calls to Kochava.

To automatically collect context.device.advertising_id, on Android you must include the Google Mobile Ads component of Google Play services as described in the Google Play services setup documentation. On iOS, you must include the AdSupport and Ad Tracking Transparency frameworks.

If making calls outside of Segment's iOS or Android library (eg post-install events sent from a server-side library), you'll need to ensure that you collect and send context.device.type, context.device.advertising_id and context.device.id.

Note that if you are sending data from mobile devices using one of our mobile libraries as well as server-side, context.device.id and context.device.advertising_id need to be the same for the same user regardless of where the data originates. Below is a Ruby example of how to pass the required context information in the track call.

1
Analytics.track(
2
  user_id: '019mr8mf4r',
3
  event: 'Subscription Charge',
4
  properties: {
5
    subscription_type: 'Premium',
6
    revenue: '9.99'
7
  },
8
  context: {
9
    device: {
10
      id: '176779B9-8C07-4E53-B3EA-ABBFAA40C829',
11
      advertising_id: '017D76B5-85F8-4E3C-8CCE-8B29CCEACB1D',
12
      type: 'ios' # or 'android'
13
    }
14
  }
15
)

To create a Kochava-Certified Postback that will send campaign information to Segment after attributing an Application Installed event, follow Kochava's Postback set up documentation.

This occurs when the user has limited ad tracking enabled on their iOS mobile device.

You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule a demo.

For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property order_completed_last_30days: true. When the user no longer satisfies this condition (for example, it's been more than 30 days since their last order), Engage sets that value to false.

When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.

Segment lets you change these destination settings from the Segment app without having to touch any code.