The Tapdaq SDK will forward these settings to each network which is initialised each time they are set (either at initialisation or mid session).
These values should be set when they are known, whether they are True or False, if left in their default Unknown state then each network will handle the user in their own way, therefore it is best to provide as much data as possible.
For users within the EU.
TapdaqConfig config = new TapdaqConfig(); config.setUserSubjectToGDPR(STATUS.TRUE); //GDPR declare if user is in EU config.setConsentGiven(true); //GDPR consent must be obtained from the user config.setIsAgeRestrictedUser(false); //Is user subject to COPPA or GDPR age restrictions Tapdaq.getInstance().initialize(this, "<APP_ID>", "<CLIENT_KEY>", config, new TapdaqInitListener());
Consent can be updated mid session as well as at initialisation, it can be set and unset.
Tapdaq.getInstance().setUserSubjectToGDPR(MainActivity.this, STATUS.TRUE); Tapdaq.getInstance().setContentGiven(MainActivity.this, true); Tapdaq.getInstance().setIsAgeRestrictedUser(MainActivity.this, true);
If you are using Mintegral you must carefully set these values or you will not receive ads.
For users outside the EU UserSubjectToGDPR must be set to FALSE.
For users inside the EU UserSubjectToGDPR must be TRUE with ConsentGiven also TRUE to receive ads.
Please do not leave UserSubjectToGDPR in an UNKNOWN state or you will not receive ads.
For all users, Tapdaq's GDPR settings must be set to something other than unknown before initialising for YouAppi to function. For users outside of the EU UserSubjectToGdpr should be set to false For users inside of the EU UserSubjectToGdpr should be set to true, also Consent should be provided for YouAppi to intialise. Note the consent MUST be obtained from the user.
If any other settings are provided, YouAppi will not be initialised and will not display ads.
We will pass the AgeRestrictedUser flag to the following networks:
The AgeRestrictedUser flag can be used to help you comply with COPPA and other applicable age restrictions.
TapdaqConfig config = new TapdaqConfig(); config.setIsAgeRestrictedUser(true); //Is user under 16 Tapdaq.getInstance().initialize(this, "<APP_ID>", "<CLIENT_KEY>", config, new TapdaqInitListener());
As of Tapdaq SDK 7.0.0, an AdMob content rating will be forwarded for every ad request to AdMob, to do this, set the value in the config either before Tapdaq has initialised or after like so:
//Before Tapdaq initialises TapdaqConfig config = new TapdaqConfig(); config.setAdMobContentRating("MA"); // G, PG, T, MA config.setIsAgeRestrictedUser(true); // GDPR/COPPA flag //After Tapdaq initialises Tapdaq.getInstance().config().setAdMobContentRating("MA"); // G, PG, T, MA Tapdaq.getInstance().config().setIsAgeRestrictedUser(true); // GDPR/COPPA flag
The tag_for_under_age_of_consent flag will be sent to AdMob if the user is subject to GDPR and AgeRestrictedUser is set. The ChildDirectedTreatment COPPA flag will be sent if user is not known to be subject to GDPR and AgeRestrictedUser is set. Read more about AdMob Targeting here.
Developers may set a UserId within Tapdaq, this will be used for Server-side Rewards and can optionally be forwarded to other networks. It should be set on initialisation and can be changed at any point during a session.
TapdaqConfig config = new TapdaqConfig(); config.setForwardUserId(true); config.setUserId("USER_ID"); Tapdaq.getInstance().initialize(<CurrentActivity>, "APP_ID", "CLIENT_KEY", config, new TMInitListener());
Tapdaq.getInstance().config().setForwardUserId(true); Tapdaq.getInstance().setUserId(MainActivity.this, "User_Id");
ForwardUserId must be set to true before setting the UserId during a session in order to pass the UserId to networks
If you are having any problems integrating, feel free to contact us on [email protected] and we will be more than happy to help.