HTML5 game publishing
Measure Your Games Section With Your Own Analytics
What your analytics can and cannot see around an embedded game, how to use them next to the partner dashboard, and where the terms draw the line on artificial launches.
The partner dashboard counts launches from the domain you registered, but it is limited by design: only visitors who accepted cookies are counted, and the numbers are estimates. Most site owners also run their own analytics. This post explains how to measure your games section with your own tools, what you can learn from them, and the line the Partner Terms draw around "artificial" launches.
What your own analytics can see
The game runs inside a frame from another origin. Your page cannot look inside it and cannot see what the player does in the game. You can measure everything on your side of the frame:
| Measure | How |
|---|---|
| Views of a game page | Your normal page-view tracking |
| Clicks on game cards | An event on the card link |
| Which categories people open | Page views of category pages |
| Time on the page | Standard engagement metrics, read with caution |
| Return visits to the games section | Your analytics tool's returning visitor reports |
| Where visitors come from | Referrer and campaign data |
What you cannot see is whether a visitor pressed Play inside the frame. That is what the PlayKovo launch count is for, with its own limits; see why the dashboard shows fewer launches.
Use both, for different questions
- Your analytics: "Which game pages attract visitors? Which categories do they open? Which sources send them?"
- The dashboard: "How many launches and players came from my domain, among those who accepted cookies?"
A game page with many views and few launches may have a weak first impression or a game that is hard to start. A page with few views and many launches is a good game that needs more visibility. Comparing the two is more useful than either alone, as long as you remember that they count different things.
Consent first
If your analytics use cookies or similar technology, the rules for consent in your region apply to them. The terms say you must have a privacy policy and, where required, consent notices for your own data collection. See cookie notices and a privacy policy. Your numbers will also have gaps wherever visitors decline.
Do not feed personal data to PlayKovo
Section 8 says not to pass personal data about your visitors to PlayKovo or to place the embed in a way that makes PlayKovo collect it for you. Do not add visitor identifiers to game addresses, and do not try to attach your analytics user IDs to the frame. Your analytics stay on your side.
The line on artificial launches
Section 7 forbids generating launches or visits artificially, including bots, scripts, auto-play, purchased or incentivized traffic, and repeated self-launches, to influence statistics. It also forbids tricking or rewarding visitors into launching a game. That has consequences for how you test and promote:
- Test your embed a few times to check it works. Do not run scripts that press Play repeatedly.
- Do not offer prizes, points or discounts for launching games.
- Do not buy traffic that is not real people interested in the games.
- Do not use auto-play tricks to start a game without the visitor's action.
Honest promotion is fine: a newsletter, a social post, a good page in search results.
A simple monthly review
- List your top ten game pages by views from your analytics.
- Compare with launches per game if your dashboard shows them.
- Pick two games to promote and two to retire.
- Look at the sources: which bring visitors who stay?
- Write down what you change, so you can compare the next month.
The dashboard and registration are explained in registering your website and reading the dashboard.


