Migrating from Xandr / Microsoft

Export your Xandr publisher configuration

From Microsoft Monetize: Publishers → export to CSV. Key fields needed:

• Publisher name
• Placement ID
• Domain or app bundle
• Current floor CPMs
• Active deal IDs

Map placements to Praevis supply sources

Xandr uses placements as the primary inventory unit. In Praevis, the supply source is the unit. Recommended mapping:

• 1 Xandr placement → 1 Praevis supply source (cleanest, easiest reporting)
• Multiple placements on same domain → 1 supply source with content_genre differentiation (reduces supply source count)

Create supply sources in Praevis

POST /api/supply/sources
{
  "name": "Xandr Placement Name",
  "domain": "com.example.streamingapp",
  "type": "ctv",
  "floor_price_cpm": 4.00,
  "content_genre": "drama"
}

Migrate floor rules

Xandr floor rules can be complex (geo-based, time-based, buyer-based). Praevis uses a single floor per supply source. Simplify:

• Use your blended average floor from Xandr as the Praevis starting floor
• Demand sources with Delegate strategies can apply their own bid logic on top

Migrate deal IDs

Private Marketplace (PMP) deals must be re-negotiated with your demand source buyers:

1. Create deals in Praevis: Supply → supply source → Deals → Add Deal
2. Agree on a new deal_id string with your buyer (or reuse the same ID if the buyer supports multi-platform deal IDs)
3. Demand source buyer updates their Delegate strategy or bidder to include the new deal_id condition

Map inventory packages to Praevis pools

Xandr inventory packages group supply sources for targeting. Recreate this as Praevis pools:

• Create a pool for each major Xandr package
• Assign equivalent supply sources to each pool
• Invite the same demand sources who were buyers in the Xandr package

→ Pool management guide

Update app-ads.txt

# Add Praevis
praevis.com, {YOUR_PUBLISHER_ID}, DIRECT

# Keep Xandr during transition
appnexus.com, {XANDR_MEMBER_ID}, DIRECT