遊戲付款
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
AdSense 程式碼應放在與遊戲相同的文件中 (也就是含有程式碼的文件,可轉譯遊戲和畫布元素 (如有))。
因此,遊戲主機擁有者會控管這個代碼,並負責設定傳遞至代碼的發布商 ID 和任何其他營利設定。因此,他們「擁有」營利設定和款項,並負責與其他方分享收益。
H5 遊戲的發行安排可能相當複雜。目前我們支援簡單的單向收益分享 (即一般的 AdSense 付款)。這項功能仍在開發階段。
發布範例
以下列舉幾個發布範例:
發布商直接將遊戲嵌入網站。他們會代為託管遊戲,因此擁有營利設定和款項。
發布商使用 iFrame 嵌入自己的遊戲,但遊戲代管網址與主要網站不同。他們會再次主辦遊戲,並控管營利設定和款項。
發布商 (A) 連結至由發布商 (B) 代管的遊戲。在這種情況下,發布商會代為託管遊戲,因此他們會控管代碼、設定營利設定,以及收益分潤方式:
記住
- 標記應一律位於與遊戲相同的文件中。
- 遊戲主辦人可控管遊戲的營利方式。
除非另有註明,否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權,程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間:2025-07-26 (世界標準時間)。
[null,null,["上次更新時間: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."]]