Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Target release
Epichttps://jira.spring.de/browse/IAM-1835
Document status
DRAFT
Document owner

Hendrik Vermeylen (KASRL) (Unlicensed)
Ralf Cornehl (KASRL) (Unlicensed)

DesignerFrank Kammann
DevelopersChristopher Kirch (KASRL) (Unlicensed), TBD
QALeonhard Keller (KASRL) (Unlicensed)
DLAClaudia Gross (KASRL) (Unlicensed)

Goals

  • Measure video commercials played out using the VAST-standard
  • Report full census session-based data
  • Report panel usage from these data

Subpages

Background and strategic fit

BARB requires the service provider to set up a system that will measure VAST compliant video adverts within VAST compliant video ad-players with IAB VAST template implementations, allowing for the capture of a number of events. The goal is to deliver data to the UK market that will be used as a currency by the advertising market.

Assumptions

  • The broadcasters' Ad Server(s) are capable to render all of the required informations in the tracking pixels.
  • Ad Server macros corresponding to the required informations (metadata or otherwise), are known and well understood by the broadcaster. In other words, the broadcaster knows and understands what is required in the tracking pixel and knows how to deliver it.

Requirements

#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.
2VAST>StreamingConvert VAST-requests into streaming requests.2
3Output 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.
4Census 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.
5VM 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.

User interaction and design

Data flows diagram to follow here. (video player > ad-call > ad-server > video player > measurement)

Questions

Below is a list of questions to be addressed as a result of this requirements document:

QuestionOutcome

Not Doing

  • 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.
  • No labels