AXE Integration
AXE (Agentic eXchange Engine) is Scope3’s real-time data and optimization platform that enables AI buyer agents to make intelligent bidding decisions. This guide covers technical integration for various ad server combinations.Overview
Scope3 expects an OpenRTB-compatible request and returns a list of segments for inclusion, exclusion, and macros. These segments should be passed into the ad server for targeting. This integration can happen client-side (typically through Prebid) or server-side (which requires development work). For server-side integration, please contact Scope3 to discuss technical requirements.Decide on AXE Key Names
Scope3 will use these default key names:axei
- Inclusion segments (1P audience matching)axex
- Exclusion segments (brand safety blocks)axem
- Creative macros
Prebid.js Implementation
Install Scope3 AXE Module in Prebid
Scope3 was added to Prebid in version 10.9.0. If building Prebid.js from source, include the Scope3 RTD module:Configuration
Add the Scope3 RTD provider to your Prebid configuration using this config snippet:Prebid Server Implementation
Add the Scope3 Prebid Server module to your Prebid Server setup and add the config snippet to your configuration file. (Scope3 todo: add a full example here)Server-to-server Implementation
See Scope3 RTD DocumentationTesting and Validation
For testing purposes, Scope3 will send a test segment until live segments are available (should betest-dnu
or something similar)
Check that AXE Segments are flowing into Prebid
- Open your browser’s developer tools
- Navigate to a page with ads
- Look for Scope3 RTD activity in the console
- Verify segments are being passed through Prebid into the ad server