If you’ve ever stared at a dashboard full of ad requests and wondered whether your supply-side platform (SSP) is actually performing the way it should, you’re not alone. An SSP check is a routine but essential review of your SSP’s traffic quality, fill rate, latency, and revenue impact. This isn’t just about spotting errors—it’s about making sure every impression you pass through has a fair chance to earn. In this guide, I’ll walk you through the core steps of an SSP check, what to look for, and how to act on what you find.
What Is an SSP Check?
An SSP check is the process of auditing your supply-side platform integration to confirm that it’s sending the right requests to the right demand sources, at the right time, and without technical leaks. For publishers and ad ops teams, this means verifying that your SSPs are not only filling inventory but also doing so in a way that protects user experience and maximizes yield. A proper check covers everything from bid response times to blocklisted domains, and it should be done on a recurring basis—not just when something breaks.
Why Regular SSP Checks Matter
SSPs are supposed to be your sell-side allies. But if you don’t check them, you can end up with issues like:
- High timeout rates that cause lost bids
- Inconsistent ad formats that hurt viewability scores
- Traffic quality problems (bots, data centers, or suspicious activity)
- Revenue leakage from poor auction logic or hidden fees
I’ve seen publishers assume their SSP is working fine because revenue looks stable. But stable isn’t the same as optimal. Running a monthly ssp check can uncover small inefficiencies that, if fixed, might lift profit by 10% or more.
How to Perform an SSP Check
There’s no single “official” method because every setup is different. But these five steps give you a solid framework.
1. Verify Your SSP Endpoints and Request Logs
Start at the ground level. Look at your ad server’s request logs or your SSP’s reporting dashboard. Confirm that every SSP you’ve configured is actually receiving requests. It sounds basic, but I’ve found cases where a partner’s endpoint was silently deprecated, and the SSP was still appearing in the UI with zero traffic. Check for:
- Correct endpoint URLs (http vs. https)
- Request volume trends over the past 7–30 days
- Any sudden drops or spikes that don’t match your site traffic
2. Analyze Fill Rate and Timeout Patterns
Fill rate is the percentage of requests that return a bid. A low fill rate could mean your demand sources aren’t interested, your targeting parameters are too narrow, or your timeout is too short. Most SSPs recommend a timeout between 350ms and 700ms. If you see timeout errors, check whether the SSP is just slow or if your own server is delaying the request. Use browser dev tools or server-side logs to compare median response times. An SSP check should always include a latency breakdown—because a bid that arrives after your ad server has moved on is worthless.
3. Audit Bid and Creative Quality
Not all bids are good bids. When you run an SSP check, look beyond the win rate. Examine the creatives that actually served:
- Did they match your site’s ad sizes and policies?
- Were there any broken or blank impressions?
- Did any creatives load heavy scripts that slowed down your page?
You can pull this data from your SSP’s creative reporting or from Google Ad Manager’s “demand channels” report. If you see repeated issues, it’s worth contacting your SSP account manager with specific examples. They often can’t fix issues they don’t know about.
4. Check Traffic Quality Signals
This is the part most people skip. An SSP check isn’t just about money—it’s about safety.
