Documentation

Kochava Identity Link

Suggest Edits

📘

This integration is currently in beta. Contact your MetaRouter support team to get started.

What Is Kochava IdentityLinkâ„¢?

Kochava IdentityLinkâ„¢ is a server-side endpoint that enables you to associate anonymous device identifiers with known user identifiers such as user ID. It allows mobile app marketers to bridge the gap between anonymous acquisition and known engagement by linking device-level data to user profiles. This linkage supports more accurate measurement, targeting, and suppression for advertising and analytics.

Product Type: Mobile Attribution

Integration Type: Starter Kit

Event Source Type: Web & Mobile

Event Scope: Identify

Capabilities

  • Links anonymous device IDs with known user identifiers
  • Enables cross-device and cross-platform user recognition
  • Facilitates downstream attribution and suppression logic
  • Sends identify events via server-to-server integration

Considerations

  • Requires both userId and a device advertising ID to trigger the linkage
  • Device type must be either iOS or Android for proper ID formatting
  • Only identify events are supported by this integration
  • May require additional mapping logic to normalize device ID formats

Limitations

  • Does not support conversion or behavioral events.
    • Please see the Kochava integration for this use case
  • Only supports iOS and Android devices; desktop devices are not linked

Starter Kit Setup Guide

1. Gather Credentials

  • Ask vendor representatives for the following credentials:
    • KOCHAVA_APP_ID: Your Kochava App GUID from the Kochava dashboard

2. Add a Kochava Identity Link Integration

  • From the integration library, add a Kochava Identity Link integration. Then, fill out the Connection Parameters:
Connection ParameterDescription
KOCHAVA_APP_IDUnique application ID used to identify your app within Kochava

3. Configure Event Mapping

  • MetaRouter provides all of the event mappings that Kochava IdentityLinkâ„¢ integrations typically require. You may add custom events, parameters, or mappings in accordance with Kochava’s API documentation.

4. Deploy to Pipeline

  • In the Pipelines tab, add your Kochava Identity Link integration.
  • Select the correct integration revision
  • Click Add Integration to finalize deployment.

Event Mappings

Global

Global mappings will be applied to all events. If your parameter names do not match the Expected Inputs provided, you will need to overwrite the Inputs provided with your own.

Output KeyDescriptionExpected Input
kochava_app_id
Required		String: Kochava App ID used for event attribution.Enrichment – $$KOCHAVA_APP_ID$$
kochava_device_id String: Anonymous device ID for session linking.anonymousId

Event Specific

Identify

Output KeyDescriptionExpected Input
data.app_userid
Required		String: Known user ID to be linked.userId
device_id
Required		Object: Advertising ID object formatted by device type.Expression – maps IDFA or ADID from context.device.advertisingId based on platform

Required & Recommended Identifiers

These identifiers must be mapped to Kochava Identity Link in order for successful user matching to occur. Without these IDs, any events sent to Kochava may not be accurately reflected in reporting.

AttributeExampleSync Injector Required?
userId
Required		abc123No
advertisingId
Required		AEBE52E7-03EE-455A-B3C4-E57283966239No
device_id
Required		{ idfa = "AEBE52E7..." }No
anonymousId
Recommended		e72f4567-91c3-4bcf-b128-489fa81d6edcNo

Integration Validation

To validate your integration, contact your Kochava representative to confirm that Identity Link events are being received and processed correctly on their backend.

Additional Kochava IdentityLinkâ„¢ Documentation

Updated about 17 hours ago