Designed to integrate.
Built to stay controlled.

This guide explains the intended publisher setup. Live SDK files, production embed snippets, and event endpoints will be published only after the delivery service is implemented and tested.

Register the website

The planned admin panel will let an administrator add a hostname, verify its ownership or control, and choose whether subdomains are permitted.

Create an ad unit

Each unit will have a stable identifier, format, status, sizing behaviour, and an explicit association with approved publisher sites.

Embed the unit

A versioned SDK and isolated iframe are planned. The eventual snippet will be generated by the admin panel so identifiers and integration details match the saved unit.

Review the measurement

Impressions and clicks will be distinct event types. Reporting is planned to include site, unit, ad, date, CTR, and separate traffic classifications.

TRUST BOUNDARIES

Integration is more than a script tag.

Server-side approval

Browser-origin headers alone are not treated as proof that a publisher is authorised.

Isolated creative

Creative formats and remote URLs will be validated, with the initial scope excluding executable HTML and JavaScript ads.

Measurable events

Event IDs, UTC timestamps, validation, and duplicate prevention are part of the planned measurement layer.

BEFORE YOU INTEGRATE

Check the product status first.

These pages document the architecture direction; they do not expose a working ad-serving API.

Explore features Read the privacy policy