When defining an Ad Server as Source in broadpeak.io, it is necessary to set an URI (Tag) which will allow the system to interrogate the Ad Server. The Ad tag usually contains what is often referred to as Macros, placeholders that broadpeak.io will replace with real values when requesting the Ad server.
The Tag and the necessary Macros will be provided by the Ad Technology partner that acts as your Ad server or SSP.
When defined an Ad Server as source, you are given the possibility to enter the Ad tag coming from the Ad Technology provider of your choice. You can enter a URL and some query parameters also called Macros.
Part of the concept of targeting requires the Ad Technology provider to retrieve dynamic values so personalization can be best achieved. This is done through these Macros.
Some values can be retrieved from the system directly:
- Cachebuster value:
- Live break Duration in seconds:
- Client Ip:
- Live break Duration in ms:
- Signal ID:
Some values can be directly retrieved from the client/CDN request query parameters or headers.
By default, the following headers are forwarded from the Client/CDN request to the Ad Server:
- X-Forwarded-For: The client IP can be retrieved from here if the CDN is configured to pass it over.
- User-Agent: The user-agent of the device if provided by the CDN in the request.
Header value mapping to Query parameters
When defining the ADS configuration (Source->ADS), it is possible to map the information received in the Client/CDN request as header to Macro values into the defined ADS tag.
To retrieve "value" of the header "header" sent to broadpeak.io in the client/CDN request, you need to use the following variable scheme:
Example: we need to retrieve the value of the header "user-agent" in the client/CDN request and pass it to the Ad server under the Macro "user-agent". The ADS Tag configuration should contain the following:
- Headers that contain a dash
-character should transform the dash in underscore
_as done for
- ⚠️ Capital letters should not be used in macros, only lowercase is accepted.
When defining the Ad Server configuration, it is possible to map the information received in the Client/CDN request as query parameter to Macro values into the defined ADS tag.
Query parameter mapping to Query parameters
To retrieve "value" of the parameter "key" sent to broadpeak.io in the client/CDN request, you need to use the following variable scheme:
Example: we need to retrieve the value of the query parameter "user" in the client/CDN request and pass it to the Ad server under the query parameter "user_id". The ad server tag configuration should contain the following macro:
⚠️ Capital letters should not be used in macros, only lowercase is accepted.
Updated about 2 months ago