Traffic Overview
Once integrated, your DSP will receive full traffic from the Thrad SSP:- Average Volume: ~50,000 requests per hour
- Peak Traffic: Up to 30 requests per second
- Traffic Type: Real-time bid requests from active chat conversations
Be prepared to handle peak loads of 30+ requests per second. Ensure your infrastructure can scale to meet these demands.
Auction Process Flow
Here’s how the complete auction and ad delivery process works:1. Bid Request
The SSP sends a bid request to your DSP endpoint with conversation context and user information.2. Your Bid Response
Your DSP analyzes the request and returns a bid (or no-bid). Submitting a Bid:data object:
- ❌ Response is not a valid JSON object (e.g., Exception, None, string)
- ❌ Missing
bidIdfield when bid > 0 - ❌
bidis not a number (e.g., “three dollars”) - ❌
bidis below the floor price ($4.00 CPM)
3. First-Price Auction
The SSP runs a first-price auction across all DSP responses:- Highest bid wins
- Winner pays their own bid amount (first-price)
- Bids below the floor price are rejected
4. Render Request (Winner Only)
If your DSP wins, the SSP sends a render request to generate the ad creative.5. Ad Delivery
Your DSP returns the ad creative, which the SSP delivers to the publisher.Pricing & Commission
Floor Price
Minimum bid: $4.00 CPM (gross)- Any bid below $4.00 will be rejected before the auction
- The floor applies to your gross bid (before commission)
SSP Commission
Commission Rate: 10% of your bid- The SSP takes a 10% commission directly from your bid
- Your actual payout is bid amount × 0.90
- Commission is deducted before payment reaches the advertiser
- The floor price check is on the gross bid (before commission)
- You bid: $10.00 CPM
- SSP commission (10%): $1.00
- Net to advertiser: $9.00 CPM
Timeouts
Your endpoints must respond within strict time limits:| Endpoint | Timeout | Recommended Target |
|---|---|---|
| Bid | 2 seconds | < 300ms |
| Render | 1 second | < 300ms |
Integration Steps
Step 1: Implementation
-
Implement the required endpoints on your server:
- Bid endpoint: Receives bid requests, returns bid or no-bid
- Render endpoint: Generates ad creative for winning bids
- Ensure your endpoints return responses in the required format (see API Reference)
- Set up infrastructure to handle peak loads (30+ req/sec)
Step 2: Testing Phase (5% Traffic)
Once your implementation is ready:- Initial Testing: The SSP will direct 5% of traffic to your DSP
-
Monitoring: We monitor for:
- Response time performance
- Error rates
- No-bid rates
- Format compliance
- Duration: Testing continues until metrics are within acceptable thresholds
Step 3: Scale-Up
Once errors and no-bid rates are below the security threshold:- Traffic gradually increases from 5% → 100%
- Continued monitoring during scale-up
- Rollback capability if issues arise
Security Thresholds: Your error rate and no-bid rate must remain below acceptable limits. Work with the Thrad team to understand specific threshold requirements.
Payment and Billing
At the end of each calendar month, Thrad will send you an invoice for the amount due based on your winning bids.How It Works
- Monthly Calculation: We calculate your total winning bid amount for the calendar month
- Commission Deduction: The 10% SSP commission is deducted from your gross bids
- Invoice: You receive an invoice with the net amount due to the publisher
- Payment: Payment terms will be agreed upon during integration setup
- Total winning bids for the month: $10,000
- SSP commission (10%): -$1,000
- Net amount due to publisher: $9,000
The invoice will include detailed reporting of all winning auctions, impressions, and any applicable adjustments.