SDK Integration
Kochava’s software development kit (SDK) seamlessly retrieves and transmits the consent string on install and event payloads when the SDK is implemented to send the install or event after the user has provided consent, and when you utilize a consent management platform that supports the Transparency & Consent Framework (TCF) v2.2 or the Global Privacy Platform API v1.1. The consent string is parsed upon receipt to populate Google’s required consent signals.
Supported SDK versions:
Server-to-Server
Advertisers using a server-to-server integration to syndicate app installs and events to Kochava have the option to include a gdpr_privacy_consent object, supporting Google’s consent requirements. Kochava offers advertisers the flexibility to choose between passing the complete consent string or solely Google-specific consent signals.
Parameter Details
| Key | Required | Notes |
|---|---|---|
| gdpr_privacy_consent | Yes | Object to support Google’s Consent Signals requirement. |
| gdpr_applies | Yes/No | Required if not passing user IP. |
| tc_string | Yes/No | Required if not passing ad_user_data & ad_personalization. |
| ad_user_data | Yes/No | Required if not passing tc_string |
| ad_personalization | Yes/No | Required if not passing tc_string |
NOTE: Refer to our Server-to-Server Install Notification Setup and Post-Install Event Setup documents for further information and examples.
