Ad formats we support
Pick the path that fits your stack. Most networks start with Traforama — it's the fastest way to get live.
Our open marketplace. Sign up, fund your account, launch a campaign — you pick exactly which traffic to buy.
For networks that want to be listed in our pre-integrated catalog so publishers can connect you directly. Requires API integration on your side.
Before you spend two weeks on integration, make sure the program matches your setup. Three quick checks on each side.
You operate an ad network or DSP and buy publisher traffic to run your demand.
You expose (or can build) REST endpoints for zones, ad code, and traffic statistics.
$1,000 onboarding deposit and 5% revenue share fit your business model.
You don't expose endpoints for zones, ad code, or statistics — and don't plan to build them.
$1,000 upfront isn't workable for your business right now.
Your offers can only fill a small slice of routed traffic — integration won't pay for itself.
Apply anyway — or start with Traforama and switch later.
The same terms apply to every pre-integrated network — whether you applied directly or were referred by a publisher.
Once the deposit hits zero, you receive a monthly invoice for 5% of that month's traffic revenue.
From application to live in the catalog. Roughly two weeks if your API matches our spec.
Use the form below. Tell us about your network, traffic volume, and inventory types.
Our BD team confirms partnership terms and requests technical contacts on your side.
We send the invoice. Technical integration begins as soon as payment is received.
Our engineers plug into your API: zones, ad code, statistics.
Your inventory becomes available to AdSpyglass publishers. First check-in scheduled at week 2 to review performance.
Three pieces of data over HTTPS. Path names, parameter names, and response shape are up to you — what matters is that this information is available.
The publisher sites you operate, each with their ad zones — zone identifier and a human-readable name per zone.
We fetch this once on integration and refresh occasionally as your inventory changes.
HTML snippet or URL for serving the zone. Must support {SUB_ID} and {KEYWORDS} macros — we substitute tracking and targeting values before rendering.
Macros are critical: without them we lose source attribution and contextual targeting.
Impressions, clicks, and revenue per zone — grouped by date, country, and sub_id. Field names can be anything (shows, views, earnings).
Pulled nightly to reconcile billing and show publishers their performance.
Detailed expectations, example payloads, and what we need from a test account.
Fill in the form and our BD team will get back to you within 2 business days.
Write us to demand@adspyglass.com in case of any integration questions.