
CMA Online Platforms Review: Arete Research’s View
2
Directing the Flow of Traffic
Google is also the main conduit through which the “long tail” of publishers get paid (i.e. those smaller sites which cannot
afford their own digital ad salesforce or can adequately track their “audience” and present it to advertisers). We refer to
the $27bn Google spent in 2018 traffic acquisition costs - $14.2bn paid to Google “Network members” or third party sites,
and another $12.6bn paid to Distribution partners, including Apple - paid annually as “code of silence” money for
publishers, who need their “representation.” Google aggregates advertiser spend and has the option to direct that spending
to its own properties or to third parties. One solution would be to oblige Google to separate the third-party ad network is
runs – by far the world’s largest – from selling ads on its own properties. This may be beyond the scope of the UK to insist
upon, but it could be proposed that in the UK, Google cannot “represent” third-party sites while also selling its own ad
inventory. This would open the market to others selling ads on third party sites and restrict Google’s access to data on users
beyond its own Sites.
Similarly, Google regularly directs search queries to its own properties, either where it promotes its own apps (in its
PlayStore) over rival alternatives, whether it favours its own travel or shopping advertisers over “organic” results, or
whether, via its partnership with Twitter (whose Chairman is Google’s former Chief Business Officer) which displays its
tweets in search results, an option not available to other social networks. The complaints of failing businesses like Yelp are
well known, but more able rivals have also suffered from lack of exposure in Google search results, especially when Google
owned Zagat, a leading restaurant review site. Google also aggregates results from crawling publisher sites, and may
present these as its own, with limited reference to, or path for monetisation for the publishers who have “done the work.”
In many instances, Google sits “on top of” multiple other content creators, directing whether they get paid (or not),
something Facebook has not matched by establishing its own third-party network.
Limiting IDs to its Own Networks
Another issue is that Google (and Facebook) restricts the passing along of log-level IDs, so that advertisers have no way
to independently confirm that they reached an audience. In this way, Google services are “opaque by design” – they
stubbornly resist outside 3P measurement. This also prevents cyber-security researchers from testing the level of bot
activity or other ad fraud schemes on Google platforms. There have been numerous instances where Android apps were
found to be allowing extensive over-permissioning in terms of data collection. This is done by a range of utility apps, such
as battery monitors, keyboards, which have been found to run click injection schemes or collect keystroke data to sell apps
install ads. This is equally a clearly well-documented problem with Facebook, which has now, staggeringly, been
indemnified by the US FTC for any mis-steps in applying its privacy policy prior to its recent settlement. Facebook has on
multiple occasions quietly “updated” its policies on data collection, while reserving the right to “grade its own homework”
when advertisers demand audits of its data via third-parties, releasing only limited data on the audience segments it
presented.
Distribution of APIs via Chrome and Android
Many of these business arrangements which Google exploits to sustain its $150bn sales business are built on the
distribution of its Chrome Browser and Android smartphone OS and many of its specific features, embedding Google
properties as default APIs (applications programming interfaces); for example, most Android compatible applications will
call up Maps, YouTube or Google Search as a default option within the functions of the apps themselves. Any business with
an application will be obliged to show its location using Google Maps, or embed video content which resolves to YouTube.
Google dictates terms to developers and encourages them to use their systems at set-piece events like its Google I/O
developers conference. These “front-ends” for consumer experiences allow Google to “nudge” consumers towards its own
services and create barriers to building other services alongside Google’s. Facebook has a similar library of APIs, holds its
onw developer conference (F8) and tightly controls its own Partner Network of authorised advertising resellers.