Service Usage Analysis - labadserver/Adplayer GitHub Wiki

A new requirement has been formulated regarding the allocation of a EDAA AdChoice icon usage report. This page is meant to collect and discuss requirements.

Status: Draft.

Scope: National.

Required performance figures:

• Number of icons displayed.
• Number of icons clicked.

Required reporting (out of scope, but to be discussed for collector entity requirements):

• Overall report structure and recipients.
• Website-specific report structure and recipients.

Proposals:

• Defined callbacks on event interfaces.

Constraints:

• The AdChoice icon is not hosted in one place/location.
• The AdPlayer is not hosted in one place/location.
• Avoid multiple requests.
• Collection and storage of performance figures need to comply with regulations on data protection and user privacy.

Assumptions:

• A centralized service can gather the performance figures.

Usage data of opt-out pages, whether youronlinechoices.com/meine-cookies.org or service related can track through website analysis tools.

Open Discussion:

• Central tracking entity.
• Open interface to register for the events impression and click, decentralized tracking and reporting.
• Activation through entity that delivers the adplayer and initializes it, activates tracking url of central entity for a agreed upon timeframe. Activation through defined interface.
• Decentralized collection of data and reporting on request through BVDW

Next steps:

• Review of requirements
• Discuss centralized approach with INFOnline