[null,null,["最后更新时间 (UTC):2025-08-27。"],[[["\u003cp\u003ePublishers in the EEA and UK must obtain user consent for cookies, data collection, and ad personalization as per Google's EU User Consent Policy and the GDPR.\u003c/p\u003e\n"],["\u003cp\u003eA Google-certified Consent Management Platform (CMP) integrated with the TCF framework is required to present consent choices to users within your app.\u003c/p\u003e\n"],["\u003cp\u003eGoogle serves personalized ads only with user consent for specific purposes, while non-personalized ads require consent for cookies and mobile identifiers but not for ad personalization.\u003c/p\u003e\n"],["\u003cp\u003eLimited ads are served when consent for cookies or mobile identifiers is not obtained but still require legitimate interest and/or consent for other purposes.\u003c/p\u003e\n"],["\u003cp\u003eTechnical ad delivery is used as a solution to deliver ads in compliance with GDPR when consent and legitimate interest for non-special purposes are not available, relying on IAB TCF v2.0 Special Purpose 2 and IP addresses.\u003c/p\u003e\n"]]],["Publishers in the EEA and UK must adhere to Google's EU User Consent Policy, obtaining user consent for cookies and personal data use. Compliance involves using a Google-certified Consent Management Platform (CMP) integrated with the TCF framework. The CMP presents consent choices for various purposes and vendors. Different ad types (personalized, non-personalized, limited, technical ad delivery) are served based on user consent for purposes and vendors. Non-personalized ads require consent for cookies and identifiers, and limited ads require no consent for Purpose 1.\n"],null,["# Ad serving modes\n\nSelect platform: [Android](/admob/android/privacy/ad-serving-modes \"View this page for the Android platform docs.\") [iOS](/admob/ios/privacy/ad-serving-modes \"View this page for the iOS platform docs.\") [Unity](/admob/unity/privacy/ad-serving-modes \"View this page for the Unity platform docs.\") [Flutter](/admob/flutter/privacy/ad-serving-modes \"View this page for the Flutter platform docs.\")\n\n\u003cbr /\u003e\n\nUnder Google's [EU User Consent Policy](//www.google.com/about/company/user-consent-policy.html),\nyou must make certain disclosures to your users in the European Economic Area\n(EEA) and the UK, and obtain their consent for the use of cookies or other local\nstorage where legally required, and for the collection, sharing, and use of\npersonal data for ads personalization. This policy reflects the requirements of\nthe EU ePrivacy Directive and the General Data Protection Regulation (GDPR). To\ncomply with this policy, publishers are required to adopt a\n\n[Google-certified consent management platform](//support.google.com/admob/answer/13554116#zippy=%2Cgoogle-certified-cmps)\n\n(CMP) that has integrated with the\n[TCF framework](//iabeurope.eu/transparency-consent-framework/) such as the\n[User Messaging Platform SDK](/admob/ios/privacy). Once adopted, the CMP presents\nconsent choices, known as purposes, in your mobile app.\n\nThe exact UI for the consent choices is kept up-to-date by Google, but here's an\nearlier version for reference:\n\n| **Important:** In addition to collecting purposes consent, you also need to collect vendor consent. Both purposes consent and vendor consent are required for any vendor, such as Google, to serve appropriate ads.\n\nThe different types of ads that can be served are:\n\n- [Personalized ads](#personalized_ads)\n- [Non-personalized ads](#non-personalized_ads)\n- [Limited ads](#limited_ads)\n- [Technical ad delivery](#technical_ad_delivery)\n\n### Personalized ads\n\n[Personalized ads](//support.google.com/admob/answer/7676680) are ads that make inferences about a user's interests based on the sites they visit or the apps they use. Google considers ads to be personalized when they are based on previously collected or historical data to determine or influence ad selection.\n\n\u003cbr /\u003e\n\nGoogle will serve personalized ads when all of the following criteria are met.\nRead\n\n[requirements for personalized ads](//support.google.com/admob/answer/9760862#consent-policies)\n\nfor more information.\n\n| Purpose | User consent choice |\n|------------|---------------------|\n| Purpose 1 | ✅ |\n| Purpose 2 | ✔ or ✅ |\n| Purpose 3 | ✅ |\n| Purpose 4 | ✅ |\n| Purpose 7 | ✔ or ✅ |\n| Purpose 9 | ✔ or ✅ |\n| Purpose 10 | ✔ or ✅ |\n[Legend: ✅ Consent ✔ Legitimate interest]\n\n### Non-personalized ads\n\n[Non-personalized ads](//support.google.com/admob/answer/7676680) are ads that are not based on a user's past behavior. Per the EU User Consent policy, **non-personalized ads still require consent for cookies mobile identifiers** .\n\n\u003cbr /\u003e\n\nGoogle will serve non-personalized ads when all of the following criteria are\nmet. Read\n\n[requirements for non-personalized ads](//support.google.com/admob/answer/9760862#consent-policies)\n\nfor more information.\n\n| Purpose | User consent choice |\n|------------|---------------------|\n| Purpose 1 | ✅ |\n| Purpose 2 | ✔ or ✅ |\n| Purpose 7 | ✔ or ✅ |\n| Purpose 9 | ✔ or ✅ |\n| Purpose 10 | ✔ or ✅ |\n[Legend: ✅ Consent ✔ Legitimate interest 🚫 No consent]\n\n### Limited ads\n\n[Limited ads](//support.google.com/admob/answer/10105530) are ads in the absence of consent for cookies or mobile identifiers. Limited ads don't access cookies, user identifiers, or equivalent local storage on the user's device.\n\n\u003cbr /\u003e\n\nGoogle will serve limited ads when all of the following criteria are met:\n\n| Purpose | User consent choice |\n|------------|---------------------|\n| Purpose 1 | 🚫 |\n| Purpose 2 | ✔ or ✅ |\n| Purpose 7 | ✔ or ✅ |\n| Purpose 9 | ✔ or ✅ |\n| Purpose 10 | ✔ or ✅ |\n[Legend: ✅ Consent ✔ Legitimate interest 🚫 No consent]\n\n### Technical ad delivery\n\n[Technical ad delivery](//support.google.com/admob/answer/14216517) is a solution to help deliver ads [in adherence to GDPR](//support.google.com/admob/answer/7666366) when consent and legitimate interest for non-special purposes aren't present. Technical ad delivery relies on [IAB TCF v2.0 Special Purpose 2 (SP2)](//iabeurope.eu/iab-europe-transparency-consent-framework-policies/#Special_Purpose_2__Technically_deliver_ads_or_content) and will utilize IP addresses for the technical delivery of ads. If you set up your CMP to call AdMob on traffic without legitimate interest or consent, AdMob will attempt to serve technical ad delivery-eligible ads.\n\n\u003cbr /\u003e"]]