Authenticated traffic
Authenticated traffic comes from readers who are signed in. It gives you a stable first-party identity for targeting and reporting, with the reader’s consent.

Registration walls, sign-up prompts and social login turn regular readers into registered users.
A reader who logs in on their phone and laptop is one profile, not two unknown visitors.
Profiles and audience sharing follow the reader’s consent choices.
Authenticated traffic is the pages viewed by readers who are logged in. Because you know who the reader is, you can target and measure that traffic without third-party cookies.
Ask the readers most likely to register, at the moment they are most engaged.

Registered readers and their segments can be shared with your ad server and used across your own channels.
It does not depend on third-party cookies, and advertisers can buy audiences built from what logged-in readers actually read, with their consent.
Registration, single sign-on, data collection and audience segments are part of the same product, so the identity and the data come from the same place.
Yes. UniSignIn reads the reader’s TCF consent choices and only builds profiles and shares audiences where consent allows it.
Create an account and add the tag, or ask us to walk you through it.
Identity, consent, audience, and subscription insights for publishers. A few emails a month, no spam.