GDPR: Why passing users consent can increase your ad revenue
User consent = higher CPMs
Marketers have a strong preference for in-app traffic coming with user consent: in an era of audience-based targeting and personalized ads, personal data such as Advertising ID, IP address, or Geolocation are highly valuable. If a user has not consented or if the consent hasn’t been passed by the publisher to the monetization platform and thus to this advertiser, advertisers won’t be able to serve personalized ads to this user. As a consequence, advertisers will also bid less or won’t bid at all for traffic coming without consent.
In short, no consent (or lack of consent) imply lower CPMs and therefore it is critical that you as a publisher collect users consent and pass it to your monetization platform.
Now, you need to make it happen!
So, how should you pass StartApp your users’ consent?
First, download our latest SDK version.
Then, use this method in case the user has consented:
StartAppSDK.setUserConsent (this, "pas", System.currentTimeMillis(), true);
and use this method in case the user has not consented:
StartAppSDK.setUserConsent (this, "pas", System.currentTimeMillis(), false);
NOTE: the timestamp parameter should represent the specific time a consent was given by the user.
• You are only required to collect consent from users in countries by GDPR (EU member states). You are not required to collect consent from users based outside those countries.
• We recommend you to pass the consent flag to StartApp right after initializing the SDK.
• You must re-submit the relevant consent flag to StartApp if there is any consent change during the lifetime of the users’ activity.
• Older SDK versions (before 3.9.3): We’ll continue to support them with showing ads. If you cannot update the current SDK version and the user consent is false for GDPR users, do not initialize StartApp SDK for such users.
Read the full instructions by clicking here.