Supply Source & Pool Management
As a platform partner, you have full control over your supply source roster and how inventory is organised into pools for demand source targeting.
Your 11 default pools
When your partner account is created, Praevis automatically provisions 11 pools — 8 production pools and 3 sandbox pools. You never need to create pools from scratch.
Production pools (8)
| Pool | Type | Auction | Floor | Supply source visibility | Use for |
|---|---|---|---|---|---|
| Anonymized Pool | Standard | Second-price | $0.50 | Hidden (YouTube model) | Main pool — 4.3× revenue vs transparent |
| Transparent Pool | Standard | First-price | $1.00 | Visible (PMPs) | Direct deals where buyers need source IDs |
| Colocation Pool | Colo | Second-price | $0.75 | Hidden | Low-latency local demand sources (<5 ms) |
| PMP Pool | PMP | First-price | $2.00 | Visible | Invite-only demand sources, premium pricing |
| Programmatic Guaranteed | PG | Fixed price | $3.00 | Visible | Fixed-CPM guaranteed delivery deals |
| Floor Testing Pool | Standard | Second-price | $0.50 | Hidden | A/B test floor strategies before applying broadly |
| Geo-Specific Pool | Standard | Second-price | $0.75 | Hidden | Regional inventory (US, EU, APAC) |
| Brand Safety Pool | Standard | Second-price | $1.00 | Hidden | Extra-strict content filtering for premium advertisers |
Sandbox pools (3)
| Pool | Mirrors | Use for |
|---|---|---|
| Sandbox Anonymized | Anonymized Pool | Test anonymized auction behaviour — excluded from billing |
| Sandbox Transparent | Transparent Pool | Test PMP / direct-deal flows — excluded from billing |
| Sandbox Colocation | Colocation Pool | Test colo integration — excluded from billing |
Sandbox pools are completely isolated from billing and production metrics. Traffic through sandbox pools never generates revenue or spend — they exist purely for integration testing.
Which pool should a supply source go into?
Start every new supply source in the Anonymized Pool — it’s the default and highest-revenue option. Move supply sources into specialist pools once they meet the criteria:
| If the supply source… | Move to |
|---|---|
| Is part of a direct deal where the buyer needs to know the source | Transparent Pool |
| Has extremely low-latency requirements | Colocation Pool |
| Is in a private, invite-only arrangement | PMP Pool |
| Has a guaranteed fixed-CPM agreement with a buyer | Programmatic Guaranteed |
| Is being evaluated for floor price changes | Floor Testing Pool |
| Has strong geo-specific traffic (US/EU/APAC) | Geo-Specific Pool |
| Is a brand-safe, premium content environment | Brand Safety Pool |
A supply source belongs to exactly one pool. Reassigning is immediate.
Adding supply sources
Supply sources are added and managed the same way as the standard supply workflow — the only difference is that they’re automatically scoped to your partner account.
Dashboard: Supply → Add Supply Source → fill in details → Save.
API:
POST /api/supply/sources
X-API-Key: {YOUR_KEY}
X-User-Partner-ID: {PARTNER_UUID}
{
"name": "My Supply Source",
"domain": "com.example.streamingapp",
"type": "ctv",
"floor_price_cpm": 3.00
}All supply sources created under your partner API key are automatically scoped to your partner account.
→ Full supply source documentation
Impression tracking configuration
Each supply source has an impression_tracking setting in exchange_settings that controls how impressions are confirmed. Getting this right is critical for accurate billing reconciliation with your partners.
Available modes:
| Mode | Behavior | Use when |
|---|---|---|
all (default) | nurl + burl + adm pixel — all three fire the same idempotent endpoint | Web display, VAST video players, mobile webview — most publishers |
adm_pixel | Only the pixel in the adm HTML confirms — nurl/burl omitted from response | In-game SDKs or any SDK that fires nurl server-side before rendering the ad |
How to set:
PUT /api/supply/sources/{publisher_id}
{
"exchange_settings": {
"impression_tracking": "adm_pixel"
}
}Onboarding question for every new supply source: “When does your SDK fire impression notifications — on auction win (server-side) or on ad render (client-side)?”
If the answer is server-side (e.g. the SDK fires nurl when the bid is won, before deciding to render), set impression_tracking: "adm_pixel". Otherwise, leave the default (all).
Getting this wrong causes impression overcounting — you will report more confirmed impressions than the publisher actually rendered, leading to billing disputes.
Assigning a supply source to a pool
PUT /api/supply/pools/{pool_id}/assign
X-User-Partner-ID: {PARTNER_UUID}
{
"publisher_id": "pub-uuid"
}You can also reassign supply sources from the dashboard: Supply → Pools → click a pool → Assign Supply Source.
Inviting demand sources to subscribe to your pools
Demand sources don’t automatically see your pools — you invite them or they subscribe via the dashboard.
To share a pool with a demand source:
- Go to Supply → Pools → click your pool
- Click Invite Demand Source
- Enter the demand source’s registered email or demand source ID
- They receive an invite and can subscribe
Alternatively, demand sources can browse available pools under Demand → Pools and request access.
Only demand sources registered under your partner account can subscribe to your pools. Praevis prevents cross-partner pool access automatically.
Sandbox isolation
Each platform partner has a separate sandbox namespace. Your sandbox supply sources and demand sources are isolated from:
- Other partners’ sandbox data
- Your own production data
To run a full sandbox test for a new supply source:
- Create the supply source with
"sandbox": true - Use the sandbox VAST URL (
sandbox=trueparam) - Check metrics in the dashboard (Sandbox tab)
- When ready: update the supply source to
"sandbox": false
Supply source verification
app-ads.txt / ads.txt verification runs automatically every 24 hours for all supply sources. The verification status is visible per supply source in your dashboard.
Partners are notified by email when a supply source’s verification fails — before fill rate is impacted.
Managing supply source access
Supply sources log into your white-label dashboard (yourname.praevis.com) and see only their own data. They cannot see other supply sources’ data, your demand source roster, or partner-level stats.
To add a supply source as a dashboard user:
- Supply → click supply source → Users tab
- Add User → enter email → set role (
viewerormanager) - They receive an invite email
Supply source users with viewer role can see their own metrics. manager role can edit their supply source settings (floor price, sandbox mode, etc.).