Privacy

Consent and in-app advertising, what changes for publishers

A consent signal that arrives late, or not at all, changes which demand is allowed to bid. Here is what publishers should check before the next release.

By TapMind Team 1 min read
Consent and in-app advertising, what changes for publishers

In-app consent is no longer a banner you add after the mediation stack is finished. Demand partners read the signal, and a missing or late signal simply removes them from the request.

What the SDK needs before the first ad request

The consent state has to exist before the first auction. If the app asks for an ad and only then asks the user, the first sessions monetize against a smaller set of partners than the rest of the day.

What publishers should confirm

Check that the choice the user made is the choice the adapter forwards, including “no” and “not yet.” A default that looks like a yes will not survive a partner audit, and it will not match the privacy choices you publish.

Get the TapMind newsletter

Practical insights on publisher monetization, demand and AdTech, without the noise.