Kochava IdentityLink
Datafly Signal links your own user identifiers to Kochava devices through Kochava’s IdentityLink server-to-server API, so Kochava attribution and analytics can be joined to your customer data. IdentityLink is a paid Kochava feature.
Prerequisites
Configure in Signal
Configuration Fields
| Field | Required | Description |
|---|---|---|
app_guid | Yes | The Kochava App GUID (kochava_app_id) of the app whose devices you link. It identifies the app on the IdentityLink endpoint. |
api_key | No | Not used: the IdentityLink endpoint authenticates by the App GUID. Kept for existing installs. |
partner_id | No | Not used by the IdentityLink API. Kept for existing installs. |
Management UI Setup
- Go to Integrations > Add Integration > Kochava IdentityLink.
- Choose a preset: Default (
default). - Fill in the fields above and click Save.
Request format
POST https://control.kochava.com/v1/cpi/identityLink.php
{"kochava_app_id":"<App GUID>",
"device_id":{"idfa":"29DDE430-...","idfv":"59E27F41-..."},
"data":{"user_id":"crm-user-9","email_sha256":"86e0b9e5..."}}Event Mapping
| Signal event | Vendor event | Presets |
|---|---|---|
identify | identityLink | Default |
sign_up | identityLink | Default |
login | identityLink | Default |
Identity
device_id carries the IDFA and IDFV (iOS) or the GAID (Android). data.user_id is your user ID and data.email_sha256 the SHA-256 of the trimmed, lower-cased email; the raw address is never sent. Events without a device ID, or with neither a user ID nor an email, are not sent.
Consent
Assign a consent category to the integration if your policy requires one for identity linking.
Blueprint
The Kochava IdentityLink blueprint version is 0.3.0. It was last reviewed against the vendor’s documentation on 2026-09-23.