Versions Compared

Old Version 8

changes.mady.by.user Hendrik Vermeylen (KASRL) (Unlicensed)

Saved on

compared with

New Version Current

changes.mady.by.user Hendrik Vermeylen (KASRL) (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

#TitleUser StoryImportanceNotes
1Tracking pixelsThe broadcasters need to be delivered a tracking pixel with placeholders that they can fill with the correct data.1
  • It needs to be cleared which ad-servers macros deliver exactly that which is needed/expected in the pixel.
  • Responsibility for filling the variables with the correct information need to be clearly stated.
2Test DataBroadcasters to cooperate and send testdata with which development can be done.1
3VAST>StreamingConvert VAST-requests into streaming requests.2
34Output format specThe output data are required to be in Emedia format, both for census and for VM-usagedata.3This depends on if we are able to convert the VAST tracking requests into standard streaming requests.
45Census data deliveryDLA-team to set up a full census data delivery. Requirement is for the data to be in Emedia format.4If the development for converting VAST-requests into Streaming-requests is possible and done, this task will be trivial.
56VM panel extractionDLA-team to set up UK panel extraction. Requirement is for the data to be in Emedia format.4If the development for converting VAST-requests into Streaming-requests is possible and done, this task will be trivial.

...

  • We are currently not having in scope the possibility that multiple mobile identifiers are delivered in the VAST-data. Current assumption is a single variable ("mobid") to contain both iOS and Android IDFA's.
    This might change in the future.
  • We are currently not having in scope the possibility to do a JOIN over the app-cookie with TVPR-data.