Getting started

Neuwo reads a page and works out what it is about, then hands that back as standard IAB categories, subject tags and a brand safety verdict. Attach those to your ad requests and the inventory can be sold on the subject of the page rather than on its address, with nothing about the reader involved.

That holds whether Neuwo runs inside your header bidding setup, inside your ad server, or in your own code. This page is the part that is the same in all of them: what comes back, how it reaches your pages, and how to get access.

What Neuwo returns

For any page or any piece of text:

Everything carries a relevance score, so you can keep the categories Neuwo is confident about and drop the long tail. The same four blocks come back on every route. What changes is who reads them and where they end up.

How Neuwo reaches your pages

Neuwo offers three integrations. Two of them, the Prebid module and the Google Ad Manager route, are Bid Enrichment, and both call the EDGE API. The third hands the selling to Neuwo instead. Each is written up in full on Choose your integration, which is where to go to pick between them:

Or skip the integrations: the API returns the same categories for any page or any text, and what you do with them from there is yours.

Get access

An endpoint URL and a token. Both are issued by Neuwo together, and there is no self-service signup: contact Neuwo or email adops@neuwo.ai, and say which sites you want analysed. Keep the token out of anything public.

Which token depends on the route. Anything running in the browser, the Prebid module included, uses the EDGE API, which is the API Bid Enrichment runs on; anything running on your own servers uses the Auto-Tagging API. They take separate tokens, and a token issued for one does not work on the other. The API section has the detail.

If Neuwo is selling the inventory, there is nothing for you to hold: the setup is arranged with Neuwo and the credentials stay on their side.

Where to go next