Google UA Hints Attribution Methods

Google Chrome is limiting browser data that is shared through the user agent causing a decrease in probabilistic attribution for app users that use Google Chrome as their web browser. This document describes the process for attribution utilizing the Google UA hints provided by Google Chrome when they are present.

Google has minimized the identifying information shared in the user agent string which is used for attribution. With this change, all resource requests have a reducedUser-Agent header which reduces the values from certain Navigator interfaces.

NOTE: Advertisers who use the Kochava SDK have this handled automatically — the SDK makes the necessary calls for user-agent client hints on your behalf. Advertisers who do not use the Kochava SDK and instead integrate via our server-to-server APIs will need to use the Client Hints API to request the OS version and device model, and include those when sending events to Kochava.

NOTE: For more information on Google’s user agent Reduction, refer to Google’s support documentation.

NOTE: For more information on Kochava’s Partner Reconciliation settings, refer to our support documentation.

---

Adding Chrome UA Hints

When user agent hints are provided on ad traffic Kochava will collect and store those parameters. However, for attribution to occur, the same hints will need to be added to install traffic using one of the two methods:

Adding Chrome UA Hint to the Header of Request

• Sec-CH-UA-Model
• Sec-CH-UA-Platform
• Sec-CH-UA-Platform-Version

Adding Chrome UA Hints to the Request Body

{
    "action": "install",
    "data": {
        "device_ids": {
            "adid": "{adid}"
        },
        "ip_address": "93.194.32.68",
        "usertime": 1694304000,
        "device_ua": "{User-Agent}",
        "ko_device_model": "{Sec-CH-UA-Model}",
        "ko_device_os": "{Sec-CH-UA-Platform}",
        "ko_device_os_version": "{Sec-CH-UA-Platform-Version}"
    },
    "kochava_device_id": "",
    "kochava_app_id": "ko-app-guid"
}