In a standard client-side environment, MFA detection relies on pixels firing in the user’s browser. An S2S (Server-to-Server) approach moves this logic to the backend. By integrating your Demand-Side Platform (DSP) directly with a verification provider’s API, you can filter out MFA inventory before a bid is even placed.
How S2S MFA Filtering Works
Unlike browser-based wraps, S2S integration uses a direct communication line between the ad server and the verification database.
- The Bid Request: An SSP sends a bid request containing the site URL and Publisher ID.
- The S2S Lookup: The DSP sends a pre-bid request to the verification server.
- The Verdict: The verification server returns a signal (e.g.,
MFA_Score: High). - The Action: The DSP automatically drops the bid, ensuring no spend is wasted on the low-quality site.
Key Technical Advantages of S2S
| Feature | Client-Side (Pixel) | S2S (Server-side) |
| Latency | Can slow down page load. | Near-zero impact on user experience. |
| Bypassing | Ad-blockers can stop pixels. | Impossible to block; happens at the server level. |
| Cost Efficiency | You pay for the impression, then see it was MFA. | You never bid on the MFA site in the first place. |
| Data Integrity | Vulnerable to spoofing. | More secure as it relies on direct API handshakes. |
