Kochava’s Marketers Operating System (m/OS) provides effective and accurate tracking of audiences across all connected devices. OTT and CTV measurement support provides the ability, depending on the device, to track installs, events, clicks and impressions.
OTT and CTV Attribution
OTT and CTV devices deliver content such as audio and video through the use of the internet without requiring users to subscribe to a traditional cable or satellite service.
The Kochava system provides deterministic and probabilistic matching. Depending on the device identifiers passed to Kochava (Device ID, Device UA, and IP Address) either deterministic or probabilistic (modeled) attribution will be employed. (see iOS 14+ restrictions)
Kochava collects (via momentary redirect or network server ping) device information when an impression is served or a user clicks on an advertisement served by a network. Each of these engagements are eligible for attribution. Once the app is installed and launched, Kochava receives an install ping (either from the Kochava SDK within the app, or from the advertiser’s server via Server-to-Server integration).
For more information about Kochava’s attribution engine, refer to our Attribution Overview support documentation.
Deterministic Attribution:
When an OTT or CTV passes Kochava unique device characteristics, which are identifiers that are completely unique to that individual device only, the Kochava attribution engine can provide authoritative attribution.
Probabilistic Attribution:
When an OTT or CTV does not pass Kochava unique device identifiers, but instead passes an IP address and/or Device UA, the Kochava attribution engine can provide a high likelihood of attribution. Although deterministic matches made with device IDs are superior to probabilistic matches with regard to attribution accuracy, probabilistic matches can be used in circumstances where the collection of device IDs is prohibited, as long as user consent allows.
Best Practices:
Tracking Link Placement in Partner Platforms:
- Create a campaign tracker for each platform the ad will target.
- Place the platform specific tracking URLs in the partner platform for each Kochava app that should receive clicks and impressions.
Example —
If a client is serving ads on Roku that target users to download a mobile app on iOS or Android, the client would need to create a tracker for both their iOS and Android apps in Kochava and provide them to the partner serving ads on OTT/CTV inventory. That partner would need to be able to trigger both iOS and Android URLs when the ad is viewed or clicked on the Roku device so that the ad interaction could convert on either iOS or Android.
Recommended Approach — Use CTV Equal Priority:
Kochava recommends CTV Equal Priority as the preferred way to attribute CTV impressions. CTV ads are rarely clicked. Users typically view an ad on a TV screen and then install or reengage on a secondary device, such as a mobile phone. Because clicks normally outrank impressions in Kochava’s attribution waterfall, an incidental click could win attribution over the CTV impression. CTV Equal Priority elevates qualified CTV impressions within a configurable window so they compete on the same priority tier as clicks, with the most recent touch generally winning.
To put CTV Equal Priority to work for a campaign:
- Confirm the media partner is a CTV Equal Priority-enabled partner. The default setting applies only to eligible CTV media partners. Refer to the CTV Equal Priority documentation for the current list.
- Make sure the impression includes the
ad_platform=ctvsignal. The media partner can send this signal with its impression data. If the partner does not send it, toggle CTV Inventory to ON when creating the tracker in Campaign Manager to add the signal to the tracker’s impression URL as a fallback. - Review the CTV Equal Priority window. It is enabled by default with a 6-hour window in an app’s Default Reconciliation Settings. The window can be set to Disabled or to a custom duration from 1 minute up to 24 hours at any of the following levels, and the most granular setting wins:
- App — Partner Configuration > Configure Default Reconciliation Settings
- Partner — Partner Tools (⋮) > Reconciliation
- Tracker (highest precedence) — Tracker Tools (⋮) > Tracker Overrides
- Leave Device Attribution Behavior set to Standard in the Partner Reconciliation settings. When CTV Equal Priority applies to an impression, Kochava automatically allows the cross-device match from the CTV impression to the mobile install or post-install event. Refer to Device Attribution Behavior and CTV Equal Priority below for details.
- If you also run Apple Ads campaigns for an iOS app, keep the App-Store Search Ads Exception in mind. It is enabled by default in the Apple Ads reconciliation settings and allows an eligible CTV-tagged impression to win attribution over a more recent Apple Ads search claim. It does not guarantee that every CTV impression will win.
Device Attribution Behavior and CTV Equal Priority:
The Device Attribution Behavior setting in Partner Reconciliation determines what Kochava does when a click or impression carries a device ID, but the subsequent install or post-install event has a different device ID. In that situation a deterministic match will not occur.
- Standard — Kochava does not proceed down the attribution waterfall to attempt a modeled or IP only match. This is intentional. Because the device IDs are mismatched, Kochava knows the click or impression and the install or post-install event came from two different devices.
- Inclusive — Kochava proceeds down the attribution waterfall to attempt a modeled or IP only match even though the device IDs do not match. This setting is intended to purposely allow a cross-device match.
When a CTV impression comes from a CTV Equal Priority-enabled media partner, Kochava uses Inclusive logic during attribution even if Device Attribution Behavior is set to Standard. CTV Equal Priority allows the cross-device match from the CTV impression to the mobile app install or post-install event, so there is no need to change the setting to Inclusive.
This is especially important when a single tracker is used for both CTV and mobile ad inventory. Leaving Device Attribution Behavior at Standard while relying on CTV Equal Priority allows CTV impressions to match across devices without requiring the Inclusive setting for the tracker’s other traffic.
Recommended Partner Reconciliation Settings — CTV Only:
Impression —
- Modeled Lookback = 24 hours
- IP Lookback = 24 hours
- Partial IP Lookback = Disabled
- Device Attribution Behavior = Standard
- CTV Equal Priority = 6 hours
Click —
- Device Lookback = 7 to 30 days
- Modeled Lookback = 7 days
- IP and Partial IP Lookback = 7 days
- Device Attribution Behavior = Standard
- Modeled Attribution Tier = Full IP Address
Recommended Partner Reconciliation Settings — CTV and Mobile:
Impression —
- Modeled Lookback = 24 hours
- IP Lookback = Disabled
- Partial IP Lookback = Disabled
- Device Attribution Behavior = Standard
- CTV Equal Priority = 6 hours
Click —
- Device Lookback = 7 to 30 days
- Modeled Lookback = 7 days
- IP and Partial IP Lookback = Disabled
- Device Attribution Behavior = Standard
- Modeled Attribution Tier = Standard
Recommended Tracker Overrides for CTV Trackers:
Impression —
- Impression Lookback Device = Default
- Impression Lookback Modeled = Default
- Impression Lookback IP = 24 hours
- Impression Lookback Partial IP = Disabled
- CTV Equal Priority = 6 hours
Click —
- Device ID Lookback Window = Default
- Modeled Equalizer = 24 hours to 7 days
- Modeled Lookback Window = Default
- IP Lookback Window = 24 hours
General:
- Event Association Lookback = Unlimited
- Omit Sub OS Version for Probabilistic Match = False
Referenced Support Documentation:
- CTV Equal Priority
- Default Reconciliation Settings
- Partner Reconciliation Settings
- Tracker Override Settings
Linked Network Documentation:
Streaming Boxes/Sticks
|
Native SDK
|
S2S
|
Device ID
|
Device UA
|
IP Address
|
Install
|
Events
|
|
|---|---|---|---|---|---|---|---|
| ✔ | ✔ | rida | ✔ | ✔ | ✔ | ✔ | |
| ✔ | ✔ | fire_adid android_id |
✔ | ✔ | ✔ | ✔ | |
| ✔ | ✔ | idfa | ✔ | ✔ | ✔ | ✔ | |
| ✔ | ✔ | source maid | ✔ | ✔ | ✔ | ✔ |
Smart TVs
|
Native SDK
|
S2S
|
Device ID
|
Device UA
|
IP Address
|
Install
|
Events
|
|
|---|---|---|---|---|---|---|---|
| ✔ | ✔ | tifa | * | ✔ | ✔ | ✔ | |
| * | ✔ | vida | * | ✔ | ✔ | ✔ | |
| ✔ | ✔ | adid | * | ✔ | ✔ | ✔ | |
| ✔ | ✔ | adid | ✔ | ✔ | ✔ | ✔ | |
| ✔ | ✔ | rida | ✔ | ✔ | ✔ | ✔ | |
| ✔ | ✔ | * | ✔ | ✔ | ✔ | ✔ | |
| ✔ | ✔ | android_id rida |
✔ | ✔ | ✔ | ✔ | |
| ✔ | ✔ | android_id | ✔ | ✔ | ✔ | ✔ |
* Kochava can accept, but platform is unwilling or unable to provide this data. Please reach out to your platform partner and include Kochava.
Game Consoles
|
Native SDK
|
S2S
|
Device ID
|
Device UA
|
IP Address
|
Install
|
Events
|
|
|---|---|---|---|---|---|---|---|
| ✔ | ✔ | msai | ✔ | ✔ | ✔ | ✔ | |
| * | ✔ | * | * | * | ✔ | ✔ |
* Kochava can accept, but platform is unwilling or unable to provide this data. Please reach out to your platform partner and include Kochava.