SSPs and Traffic Sources Explained
In this lesson, we're diving into the traffic settings of Epom White-label DSP to learn how to configure and manage your traffic sources. It covers the two primary ways to connect traffic — via Epom's traffic hub or manual SSP integration — and provides a detailed walkthrough of setting up SSP endpoints, linking connectors like Google or Xandr, and validating requests. Additionally, you'll discover how to label endpoints for better campaign organization and manage bid requests seamlessly.
Useful terms:
| SSP (Supply-Side Platform) | technology for publishers to manage, sell, and optimize their ad inventory programmatically in real-time. |
| SSP endpoint | specific URL or entry point used to connect an SSP to a DSP, which facilitates the flow of bid requests and responses. |
| OpenRTB (Open Real-Time Bidding Protocol) | protocol standard for real-time bidding, allowing SSPs and DSPs to exchange ad request data in a unified format. |
| Billable event | a predefined action (e.g., an ad impression or click) that triggers a financial transaction between advertisers and SSPs. |
| Traffic hub | a centralized marketplace or network where traffic sources are aggregated and made available for advertisers to purchase. |
| Connector | a pre-configured integration feature in the DSP that simplifies connecting to specific SSPs, such as Google or Xandr, by meeting their technical requirements. |
| Bid request | a signal sent by an SSP to a DSP containing information about an ad impression available for auction, including user data and context. |
| Request validator | a tool within the DSP used to test and confirm that incoming bid requests from an SSP are correctly formatted and compatible with the platform. |
| Endpoint labeling | a feature allowing administrators to categorize traffic sources (e.g., banner, push, or sensitive) for better organization and targeting clarity. |
Additional materials:
Blog articles
Help Center articles
Course content