使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
常见问题解答
是的,您可以通过您的 Ad Manager/AdSense 账号实现平台变现。例如,您可以使用在 Ad Manager/AdSense 账号中找到的广告代码照常植入广告。如果您要向用户的内容添加自己的广告单元,请务必明确指出这一点,因为这可能会影响您与您的用户之间的整体收益分成。
AFP 与 AdSense Host API 有何不同?
AdSense 过去曾提供了一款名为 AdSense Host API 的产品,该产品用于启用三方收益分成。AFP 类似于 Host API,但采用 AFP 后,AdSense 账号属于子发布商,且平台无需执行任何账号管理任务。此外,AFP 还提供了无需 API 的选项。
我是否可以借助 AFP 实现 AMP 网页变现?
可以。请注意,AFP 报告目前无法显示按网页和 AMP 细分的数据,且不完全支持自动广告 AMP。
这取决于您选择从哪个账号获取广告设置。
广告设置来自子账号:如果您选择从子账号获取广告设置,系统将合并(统一)平台和用户账号中的广告设置,并在广告竞价期间应用相应设置。大多数屏蔽控制功能都可累加,也就是说,如果某个类别在一个账号中遭到屏蔽,但在另一个账号中没有遭到屏蔽,那么在合并生成的设置中,该类别将显示为“已屏蔽”。请参见下面的示例:

您的用户将可以使用一整套 AdSense 屏蔽控制功能,这样一来,他们就可以查看和屏蔽特定广告、广告客户网址、广告类别和广告联盟。平台将获得一套类似的工具,但不包括 AdSense 查看中心(仅面向用户账号提供)。
《欧盟地区用户意见征求政策》、《加州消费者隐私法案》和“广告投放”等部分下的布尔值设置仅来自子账号。
广告设置来自父级账号:
如果您选择从父级账号获取广告设置,我们将仅应用父级账号中的屏蔽设置。这也适用于《欧盟地区用户意见征求政策》、《加州消费者隐私法案》和“广告投放”部分下的设置。
我需要实施 ads.txt 吗?
您并不一定要拥有 ads.txt 文件。但是,如果您选择实施 ads.txt,请查看 ads.txt 部分。
需要遵守哪些 GDPR 规定?
对于由您所有并经营的网域,在使用 AFP 时,需要遵守标准的 GDPR 条款,不需要遵守额外的 GDPR 规定。如需详细了解 GDPR,请参阅有助于发布商遵守 GDPR 的工具,其中简要介绍了您和您的用户如何遵守 GDPR。
对于第三方网域上的嵌入式内容,由第三方网域负责依照 GDPR 征求用户意见。然而,由于广告投放并非由第三方控制,因此会产生一系列复杂的问题。我们当前的产品不能针对这种情况提供全面的支持。
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
[null,null,[],[[["\u003cp\u003eAdSense for Platforms (AFP) enables revenue sharing without platform account management responsibilities, unlike the previous AdSense Host API.\u003c/p\u003e\n"],["\u003cp\u003ePlatforms can continue using their Ad Manager or AdSense accounts alongside AFP for monetization.\u003c/p\u003e\n"],["\u003cp\u003eAFP supports AMP pages for monetization, although reporting and Auto ads functionalities have limitations.\u003c/p\u003e\n"],["\u003cp\u003eUser ad-blocking control options within AFP depend on the chosen ad settings configuration, affecting how platform and user preferences are combined.\u003c/p\u003e\n"],["\u003cp\u003eGDPR compliance largely follows standard AdSense guidelines, with considerations for embedded content on external domains.\u003c/p\u003e\n"]]],["Platforms can monetize using Ad Manager/AdSense ad code, with clear disclosure about user ad unit additions. AFP differs from the AdSense Host API by enabling child publishers to own their AdSense accounts without platform management. AFP supports AMP pages, though reporting breakdowns are limited. Blocking controls either merge settings from parent and child accounts or solely use parent account settings. Ads.txt is optional. Standard GDPR terms apply for the platform's domain, while third-party domains handle consent.\n"],null,["FAQs\n----\n\n### Can I still monetize my platform with Ad Manager or my own standard AdSense ad units?\n\nYes, you can monetize your platform with your Ad Manager/AdSense account. Implement ads as normal i.e., using the ad code that you can find in your Ad Manager/AdSense account. If you're adding your own ad units to your users' content, make sure that this is clear as this may affect the overall revenue share between you and your users.\n\n### How is AFP different from the AdSense Host API?\n\nIn the past, AdSense offered a product called AdSense Host API which enabled 3-way revenue sharing. AFP is similar to the Host API, however with AFP, the AdSense account belongs to the child publisher and the platform doesn't need to undertake any account management tasks. AFP also offers an API-less option.\n\n### Can I monetize AMP pages with AFP?\n\nYes, you can. Note, it's currently not possible to show the breakdown between Web and AMP in AFP reporting, and Auto ads AMP is currently not fully supported.\n\n### What blocking controls are available for users on the platform?\n\nThis will depend on your choice of [which account ad settings](/adsense/platforms/transparent/initial-tasks#choose_your_initial_configuration) will come from.\n\n**Ad settings come from child accounts:**\nIf you've chosen for ad settings to come from child accounts, ad settings from the platform and user accounts are merged (union) and applied during the ad auction. Most blocking controls are additive, meaning for instance if a category isn't blocked in one account but is blocked in another, the resulting settings merge will have that category listed as blocked. See the example below:\n\nYour users will have access to the full suite of [AdSense blocking controls](https://support.google.com/adsense/answer/180609), which will enable them to review and block specific ads, advertiser URLs, ad categories and ad networks. Platforms will have a similar suite of tools with the exception of the [AdSense review center](https://support.google.com/adsense/answer/2369326), which is only available for user accounts.\n\nBoolean settings under sections such as EU user consent, California Consumer Privacy Act and Ad serving will come from the child account only.\n\n**Ad settings come from the parent account:**\n\nIf you have chosen for ad settings to come from the parent account, we only apply the blocking settings from the parent account. This also applies to the settings under the EU user consent, California Consumer Privacy Act and Ad serving sections.\n\n### Do I need to implement ads.txt?\n\nIt's not mandatory for you to have an ads.txt file. However, if you choose to implement ads.txt, please review the [ads.txt section](/adsense/platforms/transparent/ads-txt).\n\n### What are the GDPR implications?\n\nFor your owned and operated domain, there are no additional GDPR implications, the standard GDPR terms apply to AFP. For details on GDPR, see [Tools to help publishers comply with the GDPR](https://support.google.com/adsense/answer/7666366) which outlines how you and your users can comply with GDPR.\n\nFor embedded content on third-party domains, GDPR consent collection becomes the responsibility of the third-party domain. However complications arise since ad serving isn't controlled by a third party. Our current product doesn't fully support this scenario."]]