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.
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:
andNonIABVendorsAccepted a NSNumberArray containing the Integer ID value 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 setConsentForTCFV2WithAssetKey method will be ignored.
If, at any point, user consent is changed, call this method again with updated values.
We recommend to only start the Ogury SDK once you have collected the consent of the user even in case of an error of the third-party consent manager. Otherwise it will limit the inventory we are able to choose from for the first impressions.
You must initialize the Ogury SDK after passing the user consent through the setConsentWithAssetKey method. Otherwise we will serve non-personalized ads.