Kochava

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

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

Signal events are mapped to Kochava S2S events via your blueprint. Common mappings include:

Signal Event	Kochava Event Name	Notes
`purchase`	`Purchase`	Requires `price`, `currency`, and `order_id`
`add_to_cart`	`Add to Cart`	Map product ID and quantity
`sign_up`	`Registration Complete`	Map registration method and user identifier
`app_open`	`Session`	Used for session and engagement tracking
`level_complete`	`Level Complete`	For gaming apps, map level number and score

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.

Testing

Install your app on a test device and generate a Kochava device ID.
Send a test event through Signal using the Test Event button on the integration detail page.
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.
Check Live Logs in Signal to confirm delivery returned 200 OK.

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.

InMarket Kochava IdentityLink