Third-party consent manager
Ogury requires an explicit consent from the user to use their personal data. We collect this consent through Ogury Choice Manager. This is the easiest way to collect consent for Ogury and other vendors.
If you already have your own consent notice to collect user consent, we provide a procedure to transmit the consent to us.
Requirements
You have a registered application on your Ogury dashboard. If not, you can refer to the Getting started.
Step 1: Pass consent to Ogury
To pass consent status to Ogury, call the following method after the consent has been collected:
The setConsent
method takes the following parameters:
the
Application
context.the Asset Key of your application. If you do not have one, please refer to the getting started section.
the IAB-specified Consent String generated by third-party CMP to transmit the consent of the vendors that are registered inside the IAB Vendor list.
an integer array containing the ids of accepted vendors you need that are not registered in the IAB Vendor list. The id corresponding to a vendor can be found inside our vendor list.
The IAB-specified Consent String must be valid and be generated by a whitelisted CMP. Otherwise the call to the setConsent
method will be ignored.
If, at any point, user consent is changed, call this method again with updated values.
Integration example
Step 2: Finish your integration
You can go back to the getting started to finish your integration.
Last updated