Introduction

The goal of this document is to make the link between the variables that are defined in the VAST tracking pixel from Kantar on the one side, and the macros that are available in the FreeWheel ad-server that can provide the information that is required in each variable on the other side. It is important to note that this document has a hard dependency on the tracking pixel specification.

Official FreeWheel Documentation

Document for FreeWheel macros can be found at http://adssn.com/FW/creativecheck.html.

Binding FreeWheel-specific macros to Kantar Variables

• #e{ad.externalId}. Returns external ID of the returned Ad Unit. The external Id is configurable on the ad unit in the Traffic Tab. This macro was used in the POC test; it is used to deliver the ClockID. The “e” in the macro is to get it url-encoded except for the slashes which are not encoded. We do not believe it is really needed to url-encode the ClockID since it should alphanumeric already. In the tracking pixel, will look like:
  ...+cq=#e{ad.externalId}+...
• #{request.videoRandom}. Random number from request that should change per content stream (vprn in some requests)
  This looks like the random number that Kantar requires for the "uid". Kantar expects the broadcaster to clear this up! A test of this is pending. In the tracking pixel, will look like:
   ...+uid=#{request.videoRandom}+...
• #{request.deviceId}. This macro returns the value of either key "_fw_did_idfa" or "_fw_did_google_advertising_id" included in the request. For example if had been specified, 404018DD-42C0-4410-99FE-2E2C0880EC85 would be returned. This looks like it could provide the information for the mobid=macro_1, for doing matching to the VM-panel. However, we still expect Channel 4 to clear this up! In the tracking pixel, will look like:
  ...+mobid=#{request.deviceId}+...