Kochava

Send conversion and event data to Kochava server-to-server for mobile attribution, audience segmentation, and cross-device measurement.

⚠️

This blueprint is currently alpha — schema and behaviour may change before GA.

Prerequisites

Complete these steps in the Kochava dashboard before configuring Signal.

Create a Kochava account

Register your app

Click Add App in the Kochava dashboard. Enter your app name, platform (iOS, Android, or web), and store details. Each app you track needs its own registration.

Find your App GUID

After registering your app, navigate to the app’s Settings page. Your App GUID is displayed in the app details section. This is a unique identifier for your app within Kochava.

Find your API key

Navigate to Account Settings > API Keys or look under the app’s Settings > API Credentials. Copy your API Key. This key authenticates server-to-server event delivery.

Find your Account ID

Go to Account Settings (or click your account name in the top navigation). Your Account ID is displayed in the account details. This identifies your Kochava organisation.

Configure events

In the Kochava dashboard, navigate to your app’s Events configuration. Define the event types you want to track (e.g. purchase, registration, level complete). These event names must match what you configure in your Signal blueprint.

Configuration

Field	Type	Required	Description
`app_guid`	string	Yes	The Kochava App GUID from your app’s settings.
`api_key`	secret	Yes	The Kochava API key for authenticating server-to-server calls.
`account_id`	string	Yes	Your Kochava account ID from Account Settings.

Signal Setup

Quick Setup

Navigate to Integrations in the sidebar.
Open the Integration Library tab.
Find Kochava or filter by Attribution.
Click Install, select a variant if available, and fill in the required fields.
Click Install Integration to create the integration with a ready-to-use default blueprint.

API Setup

curl -X POST http://localhost:8084/v1/admin/integration-catalog/kochava/install \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Kochava",
    "variant": "default",
    "config": {
      "app_guid": "koexample-app-guid-1234",
      "api_key": "your_api_key",
      "account_id": "12345"
    },
    "delivery_mode": "server_side"
  }'

Event Mapping

The Retail variant maps the following Datafly events to Kochava event names:

Datafly Event	Kochava Event	Notes
`Product Viewed`	`View`	Product details as event data
`Product Added`	`Add to Cart`	Product details as event data
`Order Completed`	`Purchase`	Requires `price`, `currency`, `order_id`
Custom events	Passed through	Add the Kochava event name in the blueprint event map

Identity

The default blueprint forwards the following identifiers to Kochava:

Source	Kochava field
`vendor_ids.kochava_device_id`	`device_id`
`context.ip`	`device_ip`
`context.user_agent`	`device_ua`

For mobile traffic, capture device_id (Kochava device ID), idfa (iOS), or gps_adid (Android) from your app and pass them via the Datafly mobile SDK. Web events can pass the Kochava device ID directly so attribution joins to the mobile install.

Default consent category: advertising. Gate behind advertising consent and respect platform tracking preferences (ATT on iOS, ad ID opt-out on Android).

Kochava requires a device identifier on every S2S event. Include device_id (Kochava device ID), idfa (iOS), or adid (Android) in your event payload for accurate attribution.

Verify it’s working

Install your app on a test device and generate a Kochava device ID.
In the Signal Management UI, open your Kochava integration and watch the Live Events stream as you trigger events.
In the Kochava dashboard, navigate to Analytics > Event Viewer and filter by your test device.
Verify the event name, revenue, and custom parameters match expectations.
Confirm 200 responses in Signal’s Live Events log.

Troubleshooting

Symptom	Cause	Resolution
`401 Unauthorized`	Invalid API key	Verify `api_key` in Kochava Account Settings > API Keys and update Signal.
`400 Bad Request`	Missing or invalid App GUID	Confirm `app_guid` matches the value in your app’s settings.
Events not appearing	Missing device identifier	Ensure a valid device ID (Kochava ID, IDFA, or ADID) is included in the event.
Wrong app	Incorrect `app_guid`	Verify you are using the App GUID for the correct platform and app.
Revenue not tracked	Missing `price` field	Map your revenue field to `price` (numeric) and include `currency` (ISO 4217).

Visit Kochava documentation for full API reference and credential setup instructions.

Blueprint

The Kochava blueprint version is 0.1.0 (alpha). It ships with a Retail variant covering View, Add to Cart, and Purchase events.