App Tracking: Consent Handling

This article outlines how to handle consent when tracking with the JENTIS SDK. Expertise in app development and access to your JENTIS Platform will be needed.

General

JENTIS supports consent handling to ensure compliance with data privacy regulations. To track and send data to various endpoints, you must obtain user consent for each vendor (e.g., Google, Meta, TikTok, etc.). This means that, when configuring each one of those vendors, you should define exactly how to treat and send your data based on your users' consent choice.

We recommend using a Consent Management Platform (CMP) in your app environment to do this. When a user interacts with your CMP, you must pass the current consent status to the JENTIS SDK. This process should be repeated each time consent is changed in the app.

If you are not using a CMP to track data in your app, ensure consent is set appropriately in collaboration with your Data Protection Officer (DPO).

In this article, you’ll learn how to correctly configure and handle your app tracking based on user consent.

Setting User Consents

Vendor ID

For the setConsents function, you need to obtain the internal JENTIS vendor_id from your JENTIS Platform. You can find this information under Legal Hub > Vendors. You will see a field labeled Id by clicking on the respective vendor connected to your tool (e.g., Google Ads). This is the vendor_id you must use as the key in the JSON object passed to the function.

Consent Status

We have already received feedback on how to improve this in the JENTIS APP SDK to make it less dependent on the JENTIS Platform configuration. We are actively working on implementing these improvements for the next product release.

After the user interacts with your consent bar, you must set the appropriate consent status for the corresponding vendor and the configured Consent Settings in the JENTIS Platform. The following table guides setting the consent status correctly:

CMP Decision	JENTIS Platform Consent Settings	setConsents - Consent Status
Consent Given	Consent Enabled	CODE `.allow \|\| "allow"`
Consent Given	Consent Enabled (Essential Mode)	CODE `.allow \|\| "allow"`
Consent Given	Disabled Consent	CODE `.allow \|\| "allow"`
Consent Declined	Consent Enabled	CODE `.deny \|\| "deny"`
Consent Declined	Consent Enabled (Essential mode)	CODE `.ncm \|\| "ncm"`
Consent Declined	Disabled Consent	CODE `.allow \|\| "allow"`

APP Implementation

iOS

To set user consents for different vendors, use the setConsents method on TrackingService:

CODE

TrackingService.shared.setConsents(
    vendorConsents: [
        "google_analytics_4_server-side": .allow,
        "facebook": .deny,
        "awin": .ncm
    ]
)

Android

To set user consents for various vendors, utilize the setVendors method on the JentisTrackService instance: