VAST and VMAP considerations
This page lists the areas to pay attention to when creating an integration using VAST or VMAP requests.
Resolve geotargeting when using proxies
In case you have a setup that involves a type of proxy to request and serve ads in your content, you must make sure that the correct IP address is forwarded for geotargeting purposes.
For example, a publisher A
uses a third-party company B to stitch ads into any of their live content, which means that all
content and ad requests and responses are routed through company B's services. To correctly
route the traffic, the parties or proxies in the chain add
information to the HTTP header. The way this information is added may differ between proxies,
and may cause issues to determine where the original request came from in Pulse and eventually
lead to wrong geolocation resolution and geotargeting.
The solution to this problem is to add
the HTTP header of the request forwarded from the proxy. The proxy solution must implement
X-Videoplaza-Forwarded-For in their application(s), and fill this parameter with the IP address
of the client's device.
X-Videoplaza-Forwarded-Forin the HTTP header when triggering the tracking URLs, even when they are routed through a proxy, because the location information is added to the URLs at the time the VAST or VMAP response is created. The information is in the
locparameter in the URLs, and is Base64 encoded.