If the retailer already is running ads using an ad server, it is possible to run it alongside Topsort using a fallback logic. This allows retailers to compare ad servers performance and increase fill-rates.Documentation Index
Fetch the complete documentation index at: https://docs.topsort.com/llms.txt
Use this file to discover all available pages before exploring further.
Use Cases
Fallback Logic
Use a secondary ad server when Topsort returns no winners, ensuring maximum
fill rate
A/B Testing
Compare ad server performance using audience segments or traffic splits
How It Works
For instance, if the retailer is running banner ads using GAM (Google Ad Manager), they can set Topsort as the primary ad server to make sure their direct sold campaigns have priority over GAM’s demand. Ad requests and interactions coming from ads not served by Topsort can be reported to Topsort to see and compare metrics in one place.Integrate with Topsort
Set up Topsort as your primary ad server using any of the integration
methods (API, SDK, or low-code).
Implementation Example
A/B Testing Approach
For A/B testing, modify the selection logic using:- Audience Segments - Route specific user segments to different ad servers
- Traffic Split - Randomly assign a percentage of traffic to each ad server
Report all ad interactions (including from secondary ad servers) to Topsort to
compare metrics in one unified dashboard.