Direct integration
Prebid or header bidding
- Lowest latency
- Full control over your setup
- Maximum transparency on what is bought and why
For publishers
One tag, no rebuild.
Two paths, one quality standard: direct through Prebid, or through the SSPs you already use.
Integration takes one of two paths, and both end in the same place. Integrate directly through Prebid or header bidding, or reach our demand through the SSPs you already work with, Index Exchange and partners. Whichever path you take, every impression passes the same quality layer. Both start the same way: with the crawler.
Your inventory
Publisher ad requests
SSP integration
Index Exchange and partners
- Quick activation
- The SSP relationships you already have
- The same quality standards
The C Wire quality layer
Both paths pass through it. No impression skips a step.
Domain approval
Audited at page level before it carries a campaign
MFA detection
Monitored continuously, not once at onboarding
Context analysis
Every page read and vectorised before we buy
Layout signals
Where the slot sits and how visible it is
Demand
Advertiser budgets, bought against the page
Impact formats, built with you
Impact formats, built with you
Impact formats, built with you
Impact units are built into the page itself, so they run on directly contracted publishers only. Our team maps the unit to your layout, your ad ops team reviews how it sits, and nothing runs before that review. Because Impact units take more space and hold more attention, they carry higher CPMs for the publishers who run them.
Three ways in
Three ways in
Prebid.js
A drop-in adapter for the header bidding wrapper you already run.
Prebid Server
Server-side bidding, kinder to Core Web Vitals and mobile performance, with sub-50ms response times.
C Wire script
A single JavaScript tag for publishers without header bidding infrastructure. No rebuild, no template change.
What integration can add
Set your own numbers. The assumptions behind the estimate are stated beside it.
Your inventory today
1,000,000
CHF 2
75%
Estimate
- Current monthly revenue
- CHF 1,500
- Estimated incremental revenue
- +CHF 300
- Revenue increase
- +20.0%
per month with C Wire
How this is calculated
- Contextual premium25 percent higher CPM on C Wire impressions
- Privacy-first trafficSafari and Firefox are roughly 30 percent of pageviews and carry little addressable demand
Start with the crawler
Everything we run starts from reading your pages, so allowlisting the crawler is the first step. The user agent, IP ranges, crawl rate and per-vendor instructions are published on the crawler page, with nothing behind a form. Until we can read a page we will not run on it.
What we need from you
The crawler allowlisted on every host we should read, the adapter or script in place on the page types you want to carry advertising, and an ad ops contact for the integration review. That is the whole of it.
Questions
Integration, explained
What does integration involve?
Either a Prebid.js or Prebid Server adapter, the C Wire script, or your existing SSP. For Impact formats, a mapping of the unit into your layout, done with your ad ops team and reviewed by you before launch. No rebuild.
What do you need from us?
The crawler allowlisted so pages can be read, a technical contact, and for Impact formats a review of how the units sit in your templates.
Does the SSP path get lower quality demand?
No. The quality layer is the same on both paths: domain approval, MFA monitoring, context analysis and layout signals apply to every impression.
Who is my contact?
A named person in Publisher Success for your market, not a ticket queue. Contacts are listed on the publisher contact page.
Next step
Talk to us about integration.
One tag, no rebuild, and a review of how our formats sit in your layout. Or simply allowlist the crawler and start there.