Hi,
I Integrated Ironsource SDK (7.3.0.1) and use bidding services with Ironsource + Adcolony + Liftoff + Unity Ads.
I do get consent of user regarding GDPR on startup of app and also give option to change their choice anytime in settings.
I update their choice with the code below. (They consent to being 16+ years of age and agreeing to data collection and personalized ads)
public void setConsent(bool consent)
{
_platformAgent.setConsent(consent);
}
My question:
By setting GDPR with Ironsource does it update all the bidding networks? Those 3 mentioned above (Adcolony + Liftoff + Unity Ads) are from the list of mapped networks and also the SDK versions are good.
Meaning I should ignore their relevant ways to update consent with their respective API calls, since it is mapped via Ironsource’s SDK?
“Mapping of consent integrated adapters versions per network (relevant only once using ironSource SDK V6.7.9 and above):”
from : ironSource SDK implementations under the GDPR - IronSource Knowledge Center
Thank you again
Hi @Brother_77
You are correct sir. For each downstream network in the Levelplay mediation waterfall that support it, the gdpr setConsent() parameter will be inherited.
Some networks like Meta handle it separately, but your three networks will be fine.
The documentation above still lists Liftoff and Vungle separately, but they’re one company now known as Liftoff.
Hi, how can you set up GDPR with Ironsource? Could you please share some document or tutorial about it?
Thank you so much!
I used :
= Simple GDPR Consent =
Online documentation & example code available at: https://github.com/yasirkula/UnitySimpleGDPRConsent
and there is still things to consider as Apple does not use GDPR and has a separate set up, but the above works for Android. From the messages I had with someone in Ironsource I hope this helps as it took me forever to figure the correct approach for Android vs Apple
Using the above mentioned GDPR plug in.
"The GDPR setConsent() as said is different to ATT (Apple) and should be requested from EU users despite the ATT status before the SDK init, please read for more https://developers.is.com/ironsource-mobile/general/making-sure-youre-compliant-post-gdpr
And then using the Apple’s own approach to prompt users, you pass it to Ironsource
As for ATT follow Apple guidelines. The ATT status change doesn’t depend on the SDK init, as it should be called after the SDK is initialised, so no additional actions are needed if the ATT status has been changed during the game session. "
Also Android / GDPR users have to have option to opt in out, anytime. You must have it in the menu somewhere, then pass the new value with setConsent() and reinitialise the IS SDK.
ITS AN ABSOLUTE NIGHTMARE 
last step of implementing advertising was the most horrible from all the development cycle