GDPR & ATT using flutter

[magpie]

I am implementing the GDPR message in Flutter. From what I've read ATT also needs to be displayed at some point. It does not appear the flutter google_mobile_ads package handles this. Is that correct?

When should ATT be displayed, before or after GDPR?

[Mobile Ads SDK Forum Advisor]

Hi,

Thank you for contacting the Mobile Ads SDK Support team.

Upon reviewing your concern, I understand that you need to know about GDPR & ATT using flutter.

ATT should be displayed before GDPR. This is because ATT is a system that allows users to control how their data is used for advertising, while GDPR is a law that regulates the collection and use of personal data. By displaying ATT before GDPR, you are giving users the opportunity to make informed decisions about their privacy before their data is collected.

Please refer to the help center article About IDFA messages for more information about it.
 

This message is in relation to case "ref:!00D1U01174p.!5004Q02qCArB:ref"

Thanks,
 

Mobile Ads SDK Team

[magpie]

Thanks, can you confirm the following please?

Q1) ATT has to be handled manually in Flutter? UMP can't display it automatically if configured in admob like it does for native ios?

Q2) If user does not allow tracking and then consents to GDPR. What ads would they see? Non-personal?

[Mobile Ads SDK Forum Advisor]

Hi,

Thank you for getting back to us.

1. Yes, ATT has to be handled manually in Flutter. UMP cannot display it automatically if configured in AdMob like it does for native iOS. This is because Flutter apps are not native iOS apps, and they do not have access to the same APIs. 
2. Yes, If users choose to not consent at all, then the ads that will display will be non-personalized ads.

Kindly refer to the Non-personalized ads documentation for more information about it.

Please reach out to us, if you need any further assistance.

[Test Dvd]

Answer 2 is a lie, if the user does not give consent, NO ads will be shown.

[Mobile Ads SDK Forum Advisor]

Hi,

Thank you for getting back to us.

We regret the inconvenience caused. I understand that your query is related to UMP consent. I confirm that the user does not give consent, no ads will be shown.
 

[magpie]

My query is about the combination of ATT and GDPR and what affect Allow/No track has when the user consents to GDPR

If the user does not consent on GDPR msg then I would expect no ads to be shown which is fine

However, my question was if the user does not allow tracking on the ATT msg but then consents on the GDPR msg. What happens?

Is the following correct?

ATT > Allow > GDPR > Consent > Personal ads

ATT > Allow > GDPR > Manage > Select All items required for non-personal ads > Non-personal ads

ATT > Allow > GDPR > Do not consent > No ads

ATT > No tracking > GDPR > Consent > Non-personal ads

ATT > No tracking > GDPR > Manage > Select All items required for non-personal ads > Non-personal ads

ATT > No tracking > GDPR > Do not consent > No ads

Thanks

[Mobile Ads SDK Forum Advisor]

Hi Magpie,

Thank you for getting back to us.

Your understanding of the interplay between ATT and GDPR is correct. Here's a breakdown of the scenarios you've outlined:

• ATT > Allow > GDPR > Consent: When the user allows tracking on ATT and then consents to GDPR, they are essentially giving permission for both personalized and non-personalized ads. This allows advertisers to target them based on their interests and browsing behavior.

• ATT > Allow > GDPR > Manage > Select All items required for non-personal ads: If the user opts for this option, they are still allowing tracking but are limiting the type of data that can be used for targeting. They will still see ads, but they will not be personalized based on their specific profile.

• ATT > Allow > GDPR > Do not consent: This scenario indicates that the user does not want to share any data for advertising purposes. Consequently, they will not see any ads, regardless of whether they allow tracking on ATT.

• ATT > No tracking > GDPR > Consent: When the user disallows tracking on ATT but then consents to GDPR, they are essentially overriding the ATT setting and allowing data collection for non-personalized ads. This means they will still see ads, but they will not be personalized based on their individual profile.

• ATT > No tracking > GDPR > Manage > Select All items required for non-personal ads: Similar to the previous scenario, the user is allowing data collection for non-personalized ads, even though they have disabled tracking on ATT. They will still see ads, but they will not be targeted based on their personal information.

• ATT > No tracking > GDPR > Do not consent: If the user disallows tracking on ATT and also declines consent on GDPR, they are essentially opting out of any data collection for advertising purposes. Consequently, they will not see any ads.

In summary, the combination of ATT and GDPR allows users to control how their data is used for advertising purposes. By understanding the interplay between these two regulations, advertisers can ensure they are complying with user preferences and data privacy laws.

[Test Dvd]

Hello, so, on iOS, the ATT has to be shown first and then the GDPR??

[Mobile Ads SDK Forum Advisor]

Hi,

Thank you for getting back to us.

IDFA (Identifier for Advertisers) is an Apple iOS feature that identifies a user's mobile device. You can use Privacy & messaging to show your users an IDFA message immediately before the iOS ATT alert. IDFA explainer messages give users more context and help them understand what their data might be used for.

Kindly refer to the help center article About IDFA messages for more details about it.

Please reach out to us, if you need any further assistance.
 

[Mobile Ads SDK Forum Advisor]

To provide updated information on this thread - If using the UMP SDK, please see our Help center article for Which message users will see for the possible outcomes of using ATT & GDPR. The UMP SDK has the ability to handle the presentation of both forms automatically.

For the order of the forms:
If a user is eligible for the GDPR form and does not consent for purpose 1, the UMP SDK will not subsequently show the ATT form. If the user does consent to purpose 1, the ATT form will subsequently appear. If the user consents for purpose 1 later in your app's lifecycle, for example, from the privacy options form, then the ATT form will subsequently appear. 

No consent:
In the absence of consent for purpose 1, which happens when a user selects the "No consent" option from the UMP SDK, for example, Google will attempt to serve Limited ads. That being said, this will more than likely result in a "no fill" with no ad returned. 
 

ref:!00D1U01174p.!5004Q02qCArB:ref

[uayo]

It is assumed that if someone does not consent to ATT or GDPR, or either of the two, ads would appear, right? Obviously not personalized. But this thing about no ads appearing seems new to me, is that true?

It wouldn't make any sense because if so, wouldn't everyone who doesn't want to see ads deny access to these consents? And just like that, they would get rid of seeing ads?

[Mobile Ads SDK Forum Advisor]

Hi uayo,

Thank you for getting back to us.

I will check with our team regarding your issue and one of my team members will reach out to you once we have an update on this. Meanwhile, your patience is highly appreciated.

 
This message is in relation to case "ref:!00D1U01174p.!5004Q02qCArB:ref"
Thanks,

[Mobile Ads SDK Forum Advisor]

@uayo

"It is assumed that if someone does not consent to ATT or GDPR, or either of the two, ads would appear, right? Obviously not personalized. But this thing about no ads appearing seems new to me, is that true?" This only applies to to no consent for GDPR. please see my response to your last question. 

No consent:
In the absence of consent for purpose 1, which happens when a user selects the "No consent" option from the UMP SDK, for example, Google will attempt to serve Limited ads. That being said, this will more than likely result in a "no fill" with no ad returned. 

Thanks,
Justin 

ref:!00D1U01174p.!5004Q02qCArB:ref