游戏付款
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
AdSense 代码应与游戏放置在同一文档中,即包含用于呈现游戏和画布元素的代码的文档(如果存在)。
因此,托管游戏的一方可控制此代码,并负责配置发布商 ID,以及传递到该代码的任何其他变现设置。从这个意义上来讲,他们是变现设置和付款事宜的“负责人”,负责与其他方的任何进一步收益分成。
H5 游戏的发行安排可能很复杂。目前,我们支持简单的单向收益分成(即由 AdSense 正常付款)。这是一个不断发展变化的领域。
发行示例
以下是一些发行示例:
发布商直接将游戏嵌入自己的网站。他们托管该游戏,因此是变现设置和付款事宜的负责人。
发布商利用 iframe 嵌入自己的游戏,将游戏托管在主网站以外的网址上。这种情况下依然由他们托管游戏并控制变现设置和付款事宜。
发布商 (A) 与发行商 (B) 托管的游戏相关联。在这种情况下,由发行商托管游戏,因此也由发行商控制代码、配置变现设置和收益分成方式:
注意事项
- 此代码和游戏应始终在同一文档中。
- 由托管游戏的一方控制游戏的变现设置。
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-07-26。
[null,null,["最后更新时间 (UTC):2025-07-26。"],[[["\u003cp\u003eThe AdSense code needs to be placed within the same document as the HTML5 game for monetization.\u003c/p\u003e\n"],["\u003cp\u003eThe entity hosting the game controls the AdSense settings, receives payments, and is responsible for any revenue sharing.\u003c/p\u003e\n"],["\u003cp\u003eCurrently, only simple one-way revenue shares (regular AdSense payments) are supported for HTML5 games distribution.\u003c/p\u003e\n"],["\u003cp\u003ePublishers embedding or iFraming their own games retain control over monetization, while using a distributor means the distributor controls monetization and revenue sharing.\u003c/p\u003e\n"]]],["The AdSense code must be in the same document as the game, and the host of the game controls the tag and monetization settings, including publisher IDs and revenue sharing. The host is responsible for payments. Distribution can vary, including direct embedding, using iframes, or linking to a distributor. In each case, the host of the game is responsible for the AdSense tag and its configurations. Current revshares are one-way, with further development planned.\n"],null,["# Game payments\n\nThe [AdSense code](https://support.google.com/adsense/answer/9955214) should be\nplaced in the same document as the game (the document with the code that renders\nthe game and the canvas element if one exists).\n\nWhoever hosts the game, therefore controls this tag and is responsible for\nconfiguring the publisher IDs and any other monetization settings passed to the\ntag. They therefore \"own\" the monetization settings and payments, and are\nresponsible for any further revenue sharing with other parties.\n\nDistribution arrangements for H5 games can get complicated. Right now we support\nsimple 1-way revshares (i.e. regular AdSense payments). This is an area of\nongoing development.\n\nDistribution examples\n---------------------\n\nHere are some distribution examples:\n\n1. Publisher embeds the game into their site directly. They host the game, and\n therefore own the monetization settings and payments.\n\n2. Publisher iFrame's their own game which they host at a different URL to their\n main site. Once again they host the game and control the monetization\n settings and payments.\n\n\n3. Publisher (A) links to a game that is hosted by a distributor (B).\n In this case the distributor hosts the game so *they* control the tag,\n configure the monetization settings and how the revenue is shared:\n\n\n### Remember\n\n1. The tag should always be located within the same document as the game.\n2. Whoever hosts the game controls the monetization of the game."]]