AdMob欧盟用户同意政策合规疑问：SDK使用与实现方式咨询

Hey there, let's walk through your AdMob compliance questions clearly, based on Google's official guidelines:

1. Do I have to use Google's Consent SDK, or can I build my own consent request system? #

Google strongly recommends using their official Consent SDK (part of their Consent Management Platform, CMP) because it's pre-configured to align with global privacy regulations like GDPR and Google's own policies. It handles edge cases automatically—like detecting if a user is in a region that requires consent, and presenting the correct consent prompt.

That said, it's not strictly mandatory to use the official SDK. If you choose to build a custom solution, you must ensure it fully meets all compliance requirements:

• Clearly present users with options to opt in or out of personalized ads
• Properly store and persist the user's consent choice
• Correctly communicate the consent status to AdMob in every ad request
• Adapt to regional privacy rules (e.g., different requirements for EEA vs. non-EEA users)

Keep in mind: Building a custom system means you take on full responsibility for any compliance gaps, so the official SDK is the safer, low-effort option.

2. Can I request consent in any way, as long as I tell AdMob if the user rejected personalized ads? #

No, you can't use any method to request consent. Your consent request flow must meet Google's policies and relevant privacy laws:

• The prompt must be clear, transparent, and not misleading—users need to easily understand what they're agreeing to (or rejecting)
• You can't force users to consent to personalized ads to access your app's core features
• Users must be able to easily opt out without friction

Once you have a compliant consent flow, yes, you do need to pass the user's choice to AdMob via ad request parameters. For example, in Android, you'd use RequestConfiguration.Builder().setTagForDirectedTreatment(0) to signal that a user has opted out of personalized ads (use 1 if they opted in).

3. What other compliance points should I keep in mind? #

Here are key additional details to stay compliant:

• Regional targeting: Only request consent from users in regions where it's required (like the EEA, UK, Brazil, etc.). For users in other regions, you can serve personalized ads without consent, but always stay updated on new regional privacy laws.
• Privacy policy clarity: Your app's privacy policy must explicitly explain how AdMob uses user data for personalized ads, and how users can change their consent settings.
• Underage users: If your app is targeted at or likely used by minors, you must disable personalized ads entirely—don't request consent from these users.
• Consent updates: Give users a way to change their consent choice at any time (e.g., a settings menu option), and immediately sync this new choice with AdMob.
• Testing: Use AdMob's test ads to verify that your consent logic works correctly—make sure personalized ads are only served when the user has opted in, and non-personalized ads when they've opted out.

内容的提问来源于stack exchange，提问作者Philip