Adzen Developer Documentation
Adzen reads what a piece of content is actually about, and places advertising that belongs there.
Not who the reader is. Not where they have been. What is on the page, right now, in front of them.
We understand the content
Most ad systems match on the person. They follow a reader across the web, assemble a profile, and use it to guess. That approach is getting less accurate every year as identifiers disappear — and it was never the strongest signal in the first place.
Adzen matches on the content itself. When someone writes:
“Our water heater finally died. Anyone know a plumber in Brooklyn who can come out this week?”
…we do not need to know who wrote it. The post already says what they need, where they need it, and how soon. That is a better buying signal than any behavioural profile, and it is available the instant the words are published.
That comprehension is the product. Everything else in these docs — the endpoints, the tag, the SDKs — is delivery.
Contextual by construction. No third-party cookies, no cross-site tracking, no user identifiers to collect, store, or defend. Privacy is not a feature we added; it is a consequence of matching on content instead of people.
Start where you are
Monetize with us — you run a site, a community, or an AI product, and you want the content you already host to earn. Covers static display placements, user-generated content, and AI assistant surfaces.
Advertise with us — you have something to sell and you want it in front of people at the moment they are describing the problem it solves. Advertiser documentation is coming soon.
Also here
- API reference — every endpoint, field, and error code