Age assurance and the acquisition funnel

Age assurance used to be a compliance afterthought. The UK's Online Safety Act and a lengthening list of US state laws have moved it into the acquisition funnel itself, ahead of the point where a UA team's usual measurement even starts, and that placement is the detail worth sitting with.

The term means verifying or reasonably estimating a user's age before granting access to certain content or features, which is not the age gate most studios already run. One difference matters. A self-declared birthdate that a user can simply type wrong no longer satisfies regulators in the jurisdictions moving fastest. The Online Safety Act pushes platforms, and by extension the apps operating on them, toward highly effective age assurance for content that could harm minors, a standard that has already driven some platforms to require document verification or facial age estimation instead of a typed date of birth. Several US states have passed their own verification requirements for specific categories of content, and in some cases for app stores themselves to check a user's age at the account level before a download can happen.

Where in the funnel this actually bites

For a UA team the practical effect shows up at the moment a new user arriving from a paid install first tries to create an account or reach core content. An age assurance step dropped in there behaves like any other onboarding friction: it cuts the completion rate between install and the first meaningful action a UA team measures. That action might be a registration event or a tutorial completion; it might equally be the first SKAN or AdAttributionKit conversion value to fire. Add document-based or facial-estimation age assurance without budgeting for that drop, and a paid campaign's apparent conversion rate falls. Worse, if postback timing shifts as a result, the conversion value schema starts reporting a less accurate picture of early cohort quality.

App store level age signals add a second layer. Where a store verifies age at the device or account level rather than leaving it to individual apps, a studio inherits a benefit and a constraint at once: a verified signal nobody on the team had to build, plus a store-level requirement that no simpler in-app age gate design will get around. Both major app stores have moved toward more centralised age signalling rather than less.

Treat that as the durable trend and plan around it instead of waiting it out.

US states have not converged on a single mechanism, which is its own operational headache. Some require verification only for specific content categories, such as material a state defines as harmful to minors, while others push the obligation onto the app store rather than the developer. A studio distributing nationally cannot assume one compliance build satisfies every state. The safer approach makes age assurance a configurable step that tightens or relaxes by region, because applying the strictest state's requirement everywhere adds friction in markets that do not ask for it yet.

The cost, and the data that leaves the studio

Age assurance is not free, in either sense of the word. Vendors offering facial age estimation or document verification charge per verification, and that cost scales with install volume in a way most UA budgets do not currently model, so a studio adding the step should run it alongside CPI as a genuine acquisition expense rather than parking it on a separate compliance line. The privacy side carries its own bill. Document or biometric verification means the studio, or its verification vendor, now holds a category of personal data considerably more sensitive than anything a standard mobile UA stack usually touches, with retention and deletion obligations an existing data map may not yet cover.

The UA teams handling this well treat age assurance as a funnel step to measure and optimise like any other, tracking its specific drop-off rate apart from general onboarding friction. Fold it invisibly into a broader conversion number and you lose the ability to tell a creative problem from a compliance step doing exactly the job someone built it to do.

Related archive reading

These articles provide related context and remain subject to their stated review status.

• Liftoff pulls its IPO. Moloco hires banks. The DSP tier is sorting itself
• Niantic's Mobile Game Studio Acquisition Talks With Scopely