An HTML5 game can run on the developer's own site, a distribution portal or inside another publisher's page. The playable title may be the same while its commercial setting changes. Counting every visible ad as the developer's inventory can overstate both control and expected income.
Separate the two surfaces
The host page can carry portal display advertising beside the game. Inside the canvas, a supported rewarded or interstitial opportunity follows the game's own transition and integration. The host may control the surrounding page without controlling every in-game moment.
| Surface | Allocation to establish | Evidence to retain |
|---|---|---|
| Surrounding portal page | Who owns the page placement and sells it? | Page delivery and the applicable owner share. |
| Game canvas | Who controls the moment, integration and seller? | In-game delivery and the agreed allocation. |
| Distribution arrangement | What can each party change or prohibit? | Placement rules, reporting and remittance terms. |
A distribution contract can reserve a placement, prohibit duplicate integrations or define a revenue split. The actual agreement governs each implementation. An iframe or a link to the game does not establish a commercial right by itself.
Diagnose each delivery path
On the page, investigate whether the placement is reached, a request is valid and an ad renders. In the game, investigate whether the transition occurs, the request completes, the ad plays and gameplay resumes correctly. Embedded contexts, device behaviour and consent handling can affect the two paths differently.
For example, imagine a portal whose surrounding banner performs well while the game's reward button often receives no usable ad. Combining them into one fill figure hides the in-game fault. The publisher and developer need a shared event trail and separate allocations before deciding who can fix it.
Compare the amount each owner retains
Reported gross revenue, the contractual split, delivery costs and remittance should be reconciled for the relevant party. Adding page and canvas totals is useful only after defining the scope and checking for duplicate records. A higher combined figure does not necessarily mean the developer receives more.
Test one distribution context
For a first route, confirm the permissions, integration and commercial allocation on one host before extending to other portals. For an earning title, select the page or canvas gap with the clearest evidence and an authorized team able to act.
Agree on the device group, delivery definitions, return-to-play behaviour and retained-income comparison. H5 / Browser Games covers this environment, while How We Work sets out the limited pilot and owner decision.