The EU KIDS Act proposes mandatory age verification at the app store level and names push notifications and reward mechanics (streaks and daily-reward loops) directly, among the most common retention mechanics in mobile gaming. The verification step lands inside the install funnel itself, so a compliance requirement can look identical to a performance regression unless a studio can see exactly where the drop happened. Still a proposal, consultation pending, but worth watching now.

Last week the European Commission published the EU KIDS Act. Buried in the Commission’s own FAQ is the sentence that should have every mobile gaming studio in Europe paying attention: app stores will be required to age rate every app, including games, block underage users from apps deemed inappropriate for their age, and carry an EU age verification app. Video Games Europe responded the same day, arguing PEGI and USK should remain the standard instead, and warning against sweeping age assurance rules applied to every game and player in Europe.

Most of the coverage this week framed this as a privacy story or a child safety story. It is both of those things. It is also something narrower and more immediately practical for anyone running UA and retention on a mobile game: this is a proposal about product mechanics, and among the mechanics it names are push notifications and reward loops.

Push notifications and reward loops are not a side detail in this proposal. They are two of the most universal re-engagement tools in mobile gaming. Nearly every free to play title runs some version of a login streak or a daily reward loop, and nearly every retention strategy leans on push to bring lapsed players back. If a regulation starts touching how those mechanics can work for a defined age group, it is touching the thing that makes a day seven retention curve look the way it does.

There is a second layer to this that matters just as much. An age assurance requirement at the store level does not sit off to the side of your funnel. It sits inside it, as a new step between the ad click and the first open. Today that journey is click, store page, install, first session. Add a mandatory age verification step and it becomes click, store page, verify, install, first session. Every one of those extra steps is a place where a user can drop off, and every drop off shows up as a mechanical decline in install to open conversion that has nothing to do with your creative or your targeting.

Diagram comparing today's 4-step mobile install funnel (ad click, store page, install, first open) with a proposed 5-step funnel under EU age assurance rules, adding a new age verification step between store page and install.

This is not an isolated European move either. The week before, California signed Assembly Bill 1709, which prohibits exposing under 16s to features designed to maximise engagement and potentially lead to compulsive use, naming infinite scroll feeds and autoplay explicitly, with more features to be added by future regulation. California and Utah and Arkansas and Louisiana and Ohio and Texas and Florida and New York on one side of the Atlantic, the European Commission on the other, and both landing on the same target in the same few weeks. This is a pattern, not a headline.

To be clear about where this actually stands. The EU KIDS Act is a proposal, not law, and a public consultation is still to come. Nobody needs to redesign their streak mechanic this month. But the direction is now visible enough that it is worth watching closely rather than filing away as a compliance footnote.

Here is the part that is actually useful to know now, before any of this becomes binding. If age assurance does land on top of the install funnel, the studios who will read it correctly are the ones who can already see acquisition and retention as one continuous line, not two separate exports that get stitched together after the fact. A mechanical dip in conversion at the verification step will look identical to a real performance problem unless you can see exactly where in the funnel the user dropped and compare it against what the same channel produced the week before the rule applied. That is not a new argument from me. It is the same one I made about tool fragmentation a few months ago, just showing up in a new place.

Watch the consultation. Read what Video Games Europe pushes for. And if your measurement setup would leave you guessing whether a conversion drop next year is regulation or is you, that is worth fixing before you need the answer, not after.

Built for studios that want to win. Not just measure.

Start your free trial today, or talk to us first. Either way, we’ll give you a straight answer about what justtrack looks like for a studio at your scale.

No credit card required