Publisher Trust & Compliance · March 2026

Your inventory.
Protected at every step.

When you integrate Metrux, your data is protected, your users' privacy is respected, and your ad inventory is handled to the highest standards in programmatic advertising.

IAB TCF v2.3 Compliant
12-Month IVT Log Retention
GDPR · CCPA · COPPA
DPA Available on Request
Data Deleted in 14 Days
// Privacy Architecture

Consent signals flow through unchanged.

We act as a transparent conduit — your CMP's TCF string reaches every DSP buyer exactly as your user set it. We add signals. We never remove them.

👤
User
Visits your site
🔒
Your CMP
TCF v2.3 consent
Metrux
Signal enrichment
Pass-Through ✓
🎯
DSP Buyers
Full TC string intact
🛡️
TC String Never Altered
Your CMP's consent string is passed through to all demand partners exactly as set. Metrux enriches bid signals in-flight — never stripping or modifying consent data.
Hard Guarantee
🌍
Contextual Fallback for EU
EU users without valid Purpose 1 consent receive contextual-only ads. No behavioural enrichment applied. IP addresses truncated, user IDs removed.
GDPR Compliant
🔍
Full Signal Transparency
Every signal Metrux adds is documented and disclosed. Publishers can request a full sub-processor list and signal inventory at any time.
On Request
// Invalid Traffic Protection

Four-layer shield against IVT clawbacks.

Multi-layer detection with full evidence retention and capped publisher liability — so you're never exposed.

01
GIVT Filtering
Known bots and crawlers blocked before the auction using IAB / ABC spider lists.
Pre-auction
02
SIVT Detection
Behavioural analysis via MRC-accredited HUMAN Security / Pixalate catches sophisticated fraud.
Real-time
03
12-Month Logs
Full IVT evidence retained — available for dispute resolution with any DSP clawback claim.
12 months
04
Clawback Cap
Your liability capped to Metrux's revenue on disputed impressions — never your gross payment.
Capped ✓
// Data Handling

What happens to your audience data.

Metrux enriches bid signals in-flight. We never build user profiles, never sell data, and delete everything within 14 days of contract termination.

0
User profiles built
14d
Data deletion SLA
0
3rd party data sales
6
Signal categories
Enriched in-flight, never stored
Signal enrichment happens per bid request. No persistent storage of audience data at any point in the pipeline.
🚫
No data sold to third parties
Your audience data is not sold, brokered, or used outside the ad auction. Sub-processor list available on request.
🗑️
Data deleted when you leave
All publisher data deleted within 14 days of contract termination. Nothing retained beyond your relationship with Metrux.
Signal accuracy guaranteed
We never misrepresent inventory attributes, URLs, or user characteristics in bid requests. Accuracy is a hard contractual guarantee.
// Regulatory Coverage

One integration. Global compliance.

Metrux handles the compliance complexity across every major privacy framework, so your legal team doesn't have to.

🇪🇺Active Coverage
GDPR
Full TCF v2.3 Support
Consent string pass-through; contextual-only fallback for non-consented EU/EEA traffic.
🔒Active Coverage
ePrivacy
Cookie Consent Honoured
No persistent ID storage without valid Purpose 1 consent. Cookie signals fully respected.
🇺🇸Active Coverage
CCPA / CPRA
California Compliance
GPC signal detection; opt-out routing; no behavioural targeting for opted-out users.
🗺️Active Coverage
US State Laws
20+ State Coverage
California standard as floor; IAB GPP string support for multi-state compliance.
🛡️Active Coverage
COPPA
Children's Privacy
No behavioural enrichment for child-directed inventory; COPPA flag passed to all buyers.
🇮🇱Active Coverage
ILPPA 2025
Israeli Privacy Law
EU adequacy status — Israel's privacy framework fully aligned with GDPR standards.
// What We Need From You

Publisher obligations.

A short checklist to ensure full compliance and optimal performance throughout your Metrux integration.

Add Metrux to your ads.txt RESELLER entry: metrux.com, [your-account-id], RESELLER — required on every monetised domain.
Use a TCF v2.3 compliant CMP Any IAB-registered CMP works: Quantcast, OneTrust, CookieBot, etc.
Pass consent strings in ad calls Your CMP's TC string must reach Metrux's integration endpoint on every ad call.
No child-directed inventory COPPA-covered content must be flagged or excluded from the Metrux integration.
Notify us of traffic source changes Any changes to traffic origin or site content require 30 days' notice.
Maintain accurate site categorisation IAB content categories declared at onboarding must remain accurate throughout.
// Service Level Agreement

Our commitments, in writing.

Most vendors talk about reliability. We publish it. These are the numbers we hold ourselves to — and what happens if we don't.

99.9%
Uptime SLA
Measured monthly. Excludes scheduled maintenance windows communicated 48h in advance.
<50ms
P95 Enrichment Latency
95th percentile enrichment time per impression. Auto-fallback to passthrough if exceeded.
<1hr
Critical Incident Response
First response for any incident affecting revenue or auction delivery. Direct line to founders.
24hr
Standard Support Response
All integration, reporting, and billing queries answered within one business day.
Commitment Target If We Miss Status
Service uptime 99.9% monthly Pro-rata service credit applied automatically to next invoice Operational
Enrichment latency <50ms at P95 Automatic passthrough — your auction fires unchanged, zero impact to revenue Operational
Revenue reporting Real-time dashboard Manual reconciliation delivered within 24h of any reporting gap Operational
Payment Net-30 from month close 1.5% monthly interest on any late payment, credited to publisher Net-30
Data deletion 14 days post-termination Written confirmation of deletion with audit log provided to publisher GDPR
Critical incident response <1 hour first response Direct escalation to founders. Incident post-mortem within 48h. 24/7
// The Real Concerns

We know what you're actually worried about.

These aren't FAQ-style questions. They're the real reasons publishers in this industry say no to new vendors — and we think you deserve a direct answer to each one.

🤝 Your SSP relationships are completely untouched.
"What if this damages my SSP relationships? Those took years to build."
THE REALITY

Metrux operates upstream of your SSP relationships — we enrich the bid request before it reaches them, then step aside. We never impersonate an SSP, never modify auction mechanics, and never touch your deal IDs or PMP commitments. Your Magnite rep, your Index Exchange account manager, your Google relationship — none of them see us at all. We're invisible to demand. The only thing that changes is the bid request arrives richer than before.

We don't sit between you and your SSPs — we sit before the request leaves your server.
⏱️ Sub-50ms enrichment. Auto-fallback if we ever exceed it.
"If latency spikes even slightly, my auction dynamics break and CPMs drop."
THE REALITY

Enrichment runs in under 50ms — below the threshold your bid timeouts will ever notice. And it's non-blocking: if Metrux exceeds its time budget for any reason, the bid request fires unchanged and your auction proceeds exactly as it would without us. We've architected specifically for this constraint because we know the economics. A 10ms increase in latency costs more than it gains. We monitor P95 latency per publisher and alert before it becomes a problem.

Auto-fallback to passthrough if we ever exceed 50ms. Zero broken auctions.
📊 A/B holdback from day one. Your numbers, not ours.
"Vendors always show lift in the first 30 days. Then it quietly disappears."
THE REALITY

We run a controlled A/B holdback from day one — a portion of your traffic goes through Metrux enrichment, a matched control group does not. The lift is measured against your own baseline, using your own auction data, not ours. You can cross-reference against your SSP reporting and GAM independently. If the lift isn't there after 30 days, you see it in your own numbers before we do. There's no honeymoon period we can hide behind.

Your numbers. Your reporting. Your call to pull the tag.
🏗️ Remove our tag in 60 seconds. Your stack returns to exactly how it was.
"You're a new company. What happens to my stack if you shut down?"
THE REALITY

The tag takes 60 seconds to remove. Your entire ad operation continues without us — all your SSP relationships, all your demand, all your GAM line items remain completely intact. We don't create dependencies by design. We don't store your audience segments on our servers, we don't hold any data that your operation relies on, and we don't touch your ad server configuration. The only thing that disappears if we disappear is the yield lift.

Remove our tag in 60 seconds. Your stack returns to exactly how it was.
// Publisher FAQ

Questions publishers actually ask.

We've answered the questions your legal, ops, and monetisation teams will raise before signing anything.

QWhat happens if Metrux goes down? Will my ad serving break?
No. Metrux operates as a non-blocking wrapper. If our service is unavailable for any reason, bid requests automatically pass through to your existing demand stack unchanged — no lost impressions, no timeout errors, no revenue gap. Our SLA is 99.9% uptime with sub-50ms added latency under normal operation.
QHow long does integration take? Do I need developer resources?
Under 30 minutes, no developer required. Integration is a single wrapper tag — the same process as adding any SSP to your header bidding stack. We provide step-by-step onboarding documentation and a dedicated integration engineer for the first 48 hours. Most publishers are live in a single session.
QCan I run Metrux alongside Prebid, Google Open Bidding, or other wrappers?
Yes — Metrux is designed for this. We integrate as a transparent enrichment layer upstream of your existing auction setup. Prebid, Google OB, Amazon TAM, and direct demand all continue to function normally. We don't require exclusivity and don't interfere with your existing demand partners.
QWhat are the payment terms? When do I get paid?
Net-30, transparent revenue share. Publishers receive 80% of the incremental yield generated by Metrux enrichment. Revenue is calculated monthly based on verified auction data, reconciled against DSP reporting, and paid within 30 days of the billing period close. A detailed revenue dashboard is available in real time.
QCould signal enrichment cause brand-unsafe ads on my site?
No — we enrich supply signals, not demand targeting. Metrux adds contextual and audience signals to bid requests so DSPs can price more accurately. We do not override your existing brand safety controls, block lists, or category exclusions. Every signal we add is auditable and documented. Your floor prices and content category declarations remain fully in your control.
QWhat are the contract terms? Is there lock-in?
Month-to-month, cancel anytime. There is no long-term commitment required to get started. You can pause or terminate the integration with 30 days' notice — and your tag can be removed from your ad stack instantly at any time. We win by delivering results, not by locking you in.
QWho built this? Can I speak to the founders?
Yes — we're reachable directly. Metrux was founded by a team with deep roots in ad-tech — spanning publisher monetisation, programmatic infrastructure, and data engineering. We're an early-stage company, which means your questions go directly to the people who built the product, not a support queue. Reach us at idan@metrux.com
QHow do I verify the yield improvement is real and attributable to Metrux?
A/B testing from day one. We run a controlled holdback experiment during your first 30 days — a percentage of your traffic goes through Metrux enrichment, a control group does not. The lift is measured against your own baseline, using your own auction data. You can also reconcile against your SSP and GAM reporting independently.
// See It In Action

Metrux in 90 seconds.

Watch how we integrate into your existing stack, enrich your bid stream, and lift yield — without touching your waterfall.

// Get Started

Ready to integrate with full confidence?

Questions about compliance, DPA requests, or sub-processor details — our compliance team responds within 24 hours.

Contact Compliance Team Request Early Access →
compliance@metrux.com · metrux.com/sellers.json · DPA available on request