XML Feed Overview
The XML feed is the simple wire. You send one HTTP GET describing the visitor,
we run the auction on our side, and we answer with the ad that won: a destination
URL, a price and the notice to fire. There is no bid object for you to build and
no response for you to construct.
It exists for supply that has no natural auction surface, such as direct link rotators, pop and tab-under traffic, and push subscriber bases. If you are selling banner, video, audio or native inventory, use the RTB exchange instead.
The endpoint
GET /v1/feed/{feed_key}?ip=203.0.113.44&ua=Mozilla%2F5.0... HTTP/1.1
Host: dsp.xml.adon3.com
Accept: application/json
{feed_key} is issued per supply endpoint by the adon3 integration office. It
identifies the account, the supply type and the payout terms, so treat it as a
credential. Keep it server side and never put it in client-side code.
Both HTTP and HTTPS are accepted. Responses are JSON by default; append
format=xml for an XML body. The fields are identical either way. See
Response Formats.
Supply types
A feed key is bound to exactly one supply type. The type decides which fields come back in the response and which parameters we expect from you.
| Type | Token | Inventory | Response carries |
|---|---|---|---|
| Direct link | link | Rotators, redirects, in-content links | Destination URL and price |
| Pop | pop | Pop-under, tab-under, click-triggered windows | Destination URL, price, pop type and frequency cap |
| Push | push | Push notification subscriber bases | Title, body, image, icon and URL |
Ask the integration office for a second feed key rather than mixing types on
one. Sending push-shaped traffic to a link key returns 403. See
Status & Errors.
Billing model
The XML feed settles on cost per click. We return a price with each ad, that
price is what a valid click earns you, and the figure is net of the exchange fee.
There is nothing further to deduct.
Two things follow from CPC settlement:
- Impressions do not pay. Fire the impression notice anyway. We use it to measure fill quality and to catch feeds that request far more ads than they show.
- Clicks are filtered. Bots, duplicates inside the dedupe window and traffic
from datacentre ranges are removed before payout. Reporting shows
clicksandbillable_clicksseparately so you can watch the gap.
Request handling
| Rule | Value | Notes |
|---|---|---|
| Method | GET | POST is not supported on the feed endpoint |
| Request rate | Provisioned per feed key | 429 above it, and the ceiling can be raised |
| Dedupe window | 30 minutes | Keyed on rid, or on ip and ua when rid is absent |
| Ad expiry | 15 minutes | A destination URL not clicked inside this window stops resolving |
Use keep-alive. At any real volume a fresh connection per request costs more than the auction itself.
What to read next
Quick Start takes you from a feed key to your first paid click. Bid Endpoint is the full parameter reference, and SSP Report covers pulling your figures.