Ad Serving & SDK Integration

Once a placement is booked, the publisher's page needs to embed Advero's ad-serving script so the booked creative actually appears to visitors.

How serving works

The script requests a creative for a given placement ID; Advero's ad-serving engine checks the placement's eligible, active campaigns and returns the one that should be shown, along with its click URL.

Authentication

Requests are authenticated against the property's verification token and the page's Referer header, so a placement ID cannot be embedded on a domain other than the verified property it belongs to — see the domain verification step in the Publisher Guide.

Impressions and clicks

Every serve is logged as an impression; a visitor following the click URL is logged as a click tied to that impression. Both feed directly into the wallet ledger described in Wallet & Billing.

Integration

Phase 1 supports web placements only, via a lightweight script tag; native Android/iOS SDKs are planned for a later phase.