Hi,
I have noticed that you have two methods of implementing consent for GDPR compliance.
Option 1 - When integrating the MobFox SDK directly
MobfoxRequestParams mfrp = new MobfoxRequestParams();
mfrp.setParam(MobfoxRequestParams.GDPR, "1");
mfrp.setParam(MobfoxRequestParams.GDPR_CONSENT,"1");
// add gdpr param to banner
banner.addParams(mfrp);
// add gdpr param to interstitial
interstitial.setRequestParams(mfrp);
Option 2 - When using AdMob for mediation
AdView mAdView = (AdView) findViewById(R.id.adView);
Bundle bundle = new Bundle();
bundle.putBoolean("gdpr", true);
bundle.putString("gdpr_consent", <your-consented-vendor-list>);
AdRequest adRequest = new AdRequest.Builder()
.addTestDevice("SEE_YOUR_LOGCAT_TO_GET_YOUR_DEVICE_ID")
.addNetworkExtrasBundle(MobFoxAdapter.class, bundle)
.build();
mAdView.loadAd(adRequest);
I am trying to understand why the GDPR_CONSENT value is different between the two versions? Ideally the AdMob version would have the option of passing in a "1" or "0" for personalized and non-personalized.
Regards,
Gavin Harwood
iWare Designs Ltd.
Hi,
I have noticed that you have two methods of implementing consent for GDPR compliance.
Option 1 - When integrating the MobFox SDK directly
Option 2 - When using AdMob for mediation
I am trying to understand why the GDPR_CONSENT value is different between the two versions? Ideally the AdMob version would have the option of passing in a "1" or "0" for personalized and non-personalized.
Regards,
Gavin Harwood
iWare Designs Ltd.