setConsent API call.
This method is suitable when:
- You are not using an IAB TCF v2.x compliant Consent Management Platform (CMP).
- You have built your own consent collection mechanism.
- You need fine-grained control over when and how consent signals are passed to the SDK.
- You are implementing consent requirements for regulations other than GDPR (though it can be used for GDPR if implemented correctly).
- You want to integrate with a non-TCF CMP or custom privacy solution.
How it Works
- SDK Configuration: You initialize the Zeotap SDK with specific options to indicate you will be managing consent manually.
- User Interaction: Your app presents a consent mechanism (e.g., a dialog, settings screen) to the user.
- Capture Consent: Your app’s code captures the user’s consent choices (e.g., accepting tracking, accepting specific data uses).
- Call
setConsent: Your code calls thesetConsent()function, passing a dictionary representing the user’s consent status. - SDK Action: The Zeotap SDK receives this consent object, stores it locally, and uses it to determine whether subsequent tracking calls should proceed.
Configuration
To enable Custom Consent Management, you must configure the SDK during initialization as follows:Testing Custom Consent
Related Documentation
- Consent Configuration Options: Detailed configuration options for consent management
- Set Consent API: Complete API reference for the setConsent method
- Choosing a Consent Strategy: Guide to choosing the right consent approach
- GDPR/TCF Integration: Alternative approach using TCF-compliant CMPs