OpenRTB 2.6 Integration (beta)

AdPriva integrates with OpenRTB 2.6 to bring its proof and privacy layer into the programmatic ecosystem.

Advertisers can run campaigns through their existing DSPs and exchanges. AdPriva proofs are attached at the publisher/SSP layer and flow upstream, so every impression, click and conversion is cryptographically verified.

Why OpenRTB Support?

• Ecosystem Compatibility → Seamless with existing DSPs, SSPs and exchanges.
• Proof-First Programmatic → Every bid request, impression and conversion tied to cryptographic proofs.
• Privacy by Design → No cookies, device IDs or fingerprinting.
• Fraud Resistance → Prevents replay, spoofing and bidstream fraud at the protocol level.

How It Works

1. Bid Request → Publisher’s AdPriva Tag/SDK issues a standard OpenRTB 2.6 request with imp.ext.adpriva fields.
2. Bid Response → DSP responds with creative + price, including bid.ext.adpriva to acknowledge proof requirements.
3. Ad Delivery → Impression served, generating a ViewProof.
4. Engagement Tracking → Click → ClickProof; Conversion → ConversionProof (via S2S).
5. Settlement → Advertisers billed only for verified proofs. All proofs logged in the AdPriva Explorer.

Proof Extensions (Beta Spec)

Bid Request Extension (imp.ext.adpriva)

{
  "imp": [{
    "id": "1",
    "banner": { "w": 300, "h": 250 },
    "ext": {
      "adpriva": {
        "consent_ref": "CONSENT_HASH", 
        "bounded_use": ["sports","tech"],
        "nonce": "550e8400-e29b-41d4-a716-446655440000",
        "proof_required": true,
        "ttl_ms": 60000
      }
    }
  }]
}

Field Reference

Bid Response Extension (bid.ext.adpriva)

{
  "seatbid": [{
    "bid": [{
      "impid": "1",
      "price": 1.23,
      "crid": "CR_789",
      "ext": {
        "adpriva": {
          "view_proof": true,
          "click_proof": true,
          "conversion_proof": true
        }
      }
    }]
  }]
}

Flow

• Publisher sends bid request with consent_ref, bounded_use and nonce.
• DSP evaluates request and replies with creative + proof requirements.
• User sees ad → ViewProof generated.
• User clicks → ClickProof generated.
• User converts → ConversionProof issued via S2S.
• All proofs tied to OpenRTB transaction IDs, logged in Explorer.
• If required proofs are missing or invalid, the event is excluded from billing.

Fraud Protection in RTB

• Nonce + Expiry → Prevents replay of bid requests.
• Consent Binding → Ads only shown in categories explicitly approved by the user.
• Proof Enforcement → Invalid/missing proofs = excluded from settlement.
• Explorer Logging → Transparent audit trail for every bid, verifiable by all parties.

Beta Status

• Available in sandbox SSP/DSP integrations today.
• Production rollout planned 2026 with full ZK proof validation + on-device generation.
• Currently collecting partner feedback from DSPs/SSPs before broad release.

With OpenRTB 2.6 integration, AdPriva bridges today’s programmatic ecosystem with tomorrow’s proof-backed, privacy-first advertising.

Visual: OpenRTB + AdPriva Flow

{% @mermaid/diagram content="flowchart LR
P\[Publisher Tag/SDK] -->|Bid Request + imp.ext.adpriva| S\[SSP / Exchange]
S -->|Bid Request| D\[DSP]
D -->|Bid Response + bid.ext.adpriva| S
S -->|Bid Response| P
P -->|Ad Render| U\[User]
P -->|View/Click Event| PE\[AdPriva Proof Engine]
PE -->|ViewProof / ClickProof| EXP\[AdPriva Explorer]
PE -->|Validated Proofs| SET\[Settlement]" %}