Migrating from PubMatic

PubMatic and Praevis Exchange both use OpenRTB. The protocol is compatible — migration is primarily a configuration and endpoint change.


Concept mapping

PubMatic conceptPraevis equivalent
Site / App (PubMatic)Supply Source
Seat IDSupply Source ID (UUID)
Deal IDDeal ID (same concept, different format)
Floor CPMFloor Price CPM (per supply source)
Ad slotImpression (per bid request)
Analytics dashboardDashboard → Supply
PubMatic SSP endpointrtb.praevis.com/rtb (OpenRTB POST)

Metric translation

PubMatic metricPraevis equivalentNotes
Total RequestsBid RequestsSame definition
Fill RateFill RateSame: filled / total
eCPMeCPM(Revenue / Impressions) × 1,000
Win RateWin RateWins / bid requests sent to demand source
RevenueRevenue (cents)Praevis shows in cents
Total Spend (DSP)Spend (cents)Same, displayed in cents

Migration steps

Export your supply source list from PubMatic

Export site/app list with: name, domain/bundle, floor CPMs, deal IDs.

Create supply sources in Praevis

For each PubMatic site/app, create a Praevis supply source:

POST /api/supply/sources
{
  "name": "Supply Source Name",
  "domain": "com.example.app",
  "type": "ctv",
  "floor_price_cpm": 3.00
}

Map PubMatic floor CPMs directly to Praevis floor prices.

Update your ad server / SSP

Replace the PubMatic RTB endpoint with Praevis:

Old: https://ow.pubmatic.com/openrtb/2.5/...
New: https://rtb.praevis.com/rtb
Auth: Add header X-Publisher-ID: {PUBLISHER_ID}

The bid request format (OpenRTB 2.5) is compatible. Verify:

  • publisher.id maps to your Praevis Supply Source ID
  • imp[0].bidfloor matches your Praevis floor price
  • app.bundle or site.domain matches your registered supply source

Migrate deal IDs

Private marketplace deal IDs must be re-registered in Praevis:

  1. Go to Supply → your supply source → Deals → Add Deal
  2. Set the same deal_id string you used in PubMatic (if buyers use the same ID)
  3. Notify your demand source partners of the new endpoint so they associate the deal ID with Praevis traffic

Run in parallel

Use traffic splitting at your ad server level:

  • 80% to PubMatic, 20% to Praevis initially
  • Scale Praevis up as fill rate establishes

Update app-ads.txt

praevis.com, {YOUR_PUBLISHER_ID}, DIRECT

Leave PubMatic’s line in place during transition:

pubmatic.com, {PUBMATIC_SEAT_ID}, DIRECT

Header bidding

If using PubMatic header bidding (Prebid.js), Praevis does not have a Prebid adapter at this time. Use the VAST tag or direct RTB integration instead.

Prebid adapter is on the roadmap. Contact [email protected] to be notified when available.

OpenRTB bid request format is largely compatible between PubMatic and Praevis. The main differences: Praevis uses X-Publisher-ID header (not a URL parameter), and Praevis returns VAST 4.0 by default (add vast_version=2 param for VAST 2.0 compatibility).