Choose your integration

Where your content lives and how you connect to Adzen are two separate choices. The surface — Static, UGC, or AI — decides what Adzen reads. The integration method decides how the ad reaches your page. Pick the method that fits your stack, not the one that happens to be documented next to your surface.

Methods at a glance

Available — documented and supported today. On request — talk to your Adzen contact and we will set it up with you. — — does not apply to this surface.

How to choose

Tag — one script in the page. No backend work: the tag requests placements for the page, places them, and handles impression tracking itself. Adzen reads the page on its side. Best when you control the page template and want the lightest possible install.

Direct API — your servers send content to Adzen and render the ad we return. Best when you need control over when matching happens, how the ad renders, or when the content never reaches a browser page in a form Adzen can read.

SDKs — packages that wrap the API for you: fetching, rendering and impression tracking. Currently for AI surfaces only — @adzenai/ai for any React or Next.js app, or CopilotKit if you build on it.