Integrations

Mocktioneer integrates with popular ad tech platforms for testing header bidding and programmatic advertising flows.

Forks Required

The Mocktioneer adapters are not yet merged upstream. Use the Stackpop forks:

• Prebid.js: github.com/stackpop/Prebid.js
• Prebid Server: github.com/stackpop/prebid-server

Supported Integrations

Platform	Type	Description
Prebid.js	Client-side	Browser-based header bidding
Prebid Server	Server-side	Server-to-server bidding
Trusted Server (EC)	Identity	Edge Cookie sync and identity graph

How Integration Works

Mocktioneer acts as a drop-in replacement for real bidders during development and testing:

┌─────────────────┐     ┌─────────────────┐     ┌─────────────────┐
│   Prebid.js     │     │  Prebid Server  │     │ Trusted Server  │
│   (Browser)     │     │    (Server)     │     │   (Identity)    │
└────────┬────────┘     └────────┬────────┘     └────────┬────────┘
         │                       │                       │
         │    OpenRTB 2.x        │                       │
         │    Bid Request        │    EC Sync (Pixel     │
         │                       │    + Pull + Bidstream) │
         ▼                       ▼                       ▼
┌──────────────────────────────────────────────────────────────────┐
│                         Mocktioneer                               │
│                      (Edge or Local)                              │
└──────────────────────────────────────────────────────────────────┘
         │
         │    OpenRTB 2.x
         │    Bid Response
         ▼
┌──────────────────────────────────────────────────────────────────┐
│                       Ad Server (GAM)                             │
└──────────────────────────────────────────────────────────────────┘

Benefits

Deterministic Testing

• Same request always produces same response
• No flaky tests due to bidder variability
• Fixed $0.20 bids for predictable floor testing

No External Dependencies

• No API keys or credentials needed
• Works offline
• Fast response times

OpenRTB Banner Support

• OpenRTB 2.x banner requests and responses
• Compatible with standard OpenRTB banner clients
• Valid creative URLs

Quick Start

Prebid.js

pbjs.setBidderConfig({
  bidders: ['mocktioneer'],
  config: {
    endpoint: 'http://localhost:8787/openrtb2/auction',
  },
})

Prebid Server

adapters:
  mocktioneer:
    enabled: true
    endpoint: http://localhost:8787/openrtb2/auction

Deployment Options

Local Development

Run Mocktioneer locally for fastest iteration:

cargo run -p mocktioneer-adapter-axum

Shared Test Environment

Deploy to Fastly or Cloudflare for team-wide access:

• https://mocktioneer.edgecompute.app (Fastly)
• https://mocktioneer.your-domain.workers.dev (Cloudflare)

CI/CD

Include Mocktioneer in your test pipeline (build and publish your own image first):

# GitHub Actions example
services:
  mocktioneer:
    image: mocktioneer:latest # replace with your published image
    ports:
      - 8787:8787

Common Use Cases

Testing Bid Adapters

Verify your Prebid adapter handles responses correctly:

1. Configure adapter to use Mocktioneer
2. Run test page
3. Inspect bid responses in Prebid debug

Validating Creative Rendering

Test creative rendering pipeline:

1. Get bid response with creative URL
2. Load creative in iframe
3. Verify SVG displays correctly

Price Testing

Test price handling and floor logic:

{
  "imp": [
    {
      "id": "1",
      "bidfloor": 1.0,
      "banner": { "w": 300, "h": 250 }
    }
  ]
}

Mocktioneer always bids at a fixed $0.20 CPM and does not evaluate bidfloor itself. Use this predictable price to test that your SSP or mediation layer correctly filters bids below the floor threshold.

Identity Pipeline Testing

Test Edge Cookie sync and identity decoration:

1. Register Mocktioneer with trusted-server
2. Trigger pixel sync via /sync/start
3. Verify pull sync via /resolve
4. Send decorated bid requests with user.eids
5. Inspect creative metadata for EC info

See the Trusted Server integration guide for details.

Error Handling

Test error scenarios:

• Empty APS responses when all sizes are non-standard (OpenRTB coerces to 300x250)
• Malformed requests
• Timeout simulation (not built-in, use network tools)