2.1 Data-targeting
Data-targeting offers a variety of possibilities.
Essentially, data is represented by cookies and
device-IDs which share a common feature. Data
enables one to reflect certain interests, affinities,
purchase intentions, or general demographic features
of users (Busch, 2016). There are 1st party, 2nd party,
and 3rd party data types. 1st party data represents
user-related data directly retrieved from the user. For
instance, CRM-data or login-data gathered from the
client’s website are considered 1st party data, which
can be used for retargeting. 2nd party data is provided
by the direct partner. 3rd party data is data generated
and provided by third-party companies (Stevens et al.,
2016).
In the TCF context, it is not a question of the data
type at first. However, identifying the user within the
data requires user consent. If there is no consent, there
is no data access.
Thinking about this condition, the question is:
how many users will be willing to provide their
consent and how many will not? It is a delicate
situation as you can imagine when asked for consent.
Do you want to be asked before consent “Do you want
to be tracked on the internet?” or “Do you want to
provide us your data?”; the majority of the users
certainly would not consent because they would
assume that they would be tracked as a “person”.
Interestingly, cookie data do not possess any personal
data. In the moment of a visit, a text file (the cookie)
is stored on the hard drive, containing several
information types, e.g. file creation date, which
subpages have been visited or which volume level
was set on the web-radio. Therefore, all information
is website-related and not user-related.
3rd party data providers also usually utilise the
domain address the user visited. Cookie technology
allows addressing all devices with a specific cookie.
This represents an effective technology enabling
addressing interest-related ads without relying on
personal information.
However, the European Court of Justice (ECJ) has
decided that storing cookies requires user consent
although they do not provide direct user-related data
(ECJ, 2019). The argument is that it contains
pseudonymous data and therefore should be consent
as well. The interesting aspect here though is the fact
that the ECJ made clear that cookies do not contain
personalised data. However, in practice, users may
not realise this and still hesitate in providing their
consent upon visiting a webpage.
It needs to be emphasised that missing consents
would lead to fewer potentials out of data-targeting.
It is likely that TCF in version 2.0 will strengthen
certain 2nd party data providers and weaken many
3rd party ones. Vendors such as Google, Amazon,
and Facebook possess their own login “realms”. If a
user is registered among these vendors, he/she will be
more likely to provide consent for data usage as
compared to a sporadic visit of a random webpage.
Moreover, users would be more interested in
benefiting from various functionalities the platforms
of the vendors offer.
Google, Amazon, and Facebook also possess their
own Demand Side Platforms (DSP). Each vendor
provides its own data within their DSPs (access to the
data is therefore only possible through the use of the
DSP). It is not possible to “push” data from one DSP
to another – this is why these kinds of DSPs are
labelled as “Walled Gardens”. It is possible to feed in
external 3rd party data though; however, the opposite
is not possible. 3rd party data is useful in specific
cases as some providers made more accurate targeting
data available compared to Google, Amazon or
Facebook. Unfortunately, the amount of data 3rd
party vendors can provide would eventually drop.
There are also DSPs that fully rely on 3rd party data
only – the developments would have an effect on their
market performances as well. Currently, there are
various DSPs in the market with different solutions,
addressing different niches. However, the threatening
disappearance of DSPs would eventually strengthen
the Walled Garden DSPs. Looking at Facebook,
Amazon and Google, it can be said that Facebook is
unique as it positions within the social media domain.
Google and Amazon thus represent currently the
biggest PA players in the industry, raising questions
in regard to their influence in the whole market.
2.2 Frequency Capping
One of the advantages in PA is the ability to set a
Frequency Cap (FC). A FC is the maximum
frequency of the ad to be displayed per user (e.g.
Buchbinder et al., 2014).
Before PA was introduced, agencies booked ad
placements per publisher manually. For instance, ad
placements on 20 different publishers resulted in
different FC on each publisher set by the marketers.
This represents a problem as ads would be displayed
too frequently to users and lose potentially their
optimal impact. With the introduction of PA, it was
possible to set a FC on all marketers. With that, it is
feasible to set a common FC of, for instance, 2 per
week for over 3,000 different webpages. If the FC is
set too low, the advertising impact would not be
effective enough. However, this is important to