The use of OneTrust as a CMP, which has a reject all option, but notably lets Google fire on initial page load, though with denied consent mode.

Google Tag Manager (GTM) is the core tag manager of choice for the all of the tracking implementation though no real server side approach.

A big use of Google Analytics is in place here, alongside some more independent tracking from Dot Digital.

Seems to be less focus on the use of first party data management directly on platform, with heavy focus on client side marketing tags to do this lift.

A wider selection including Meta, TikTok, Google Ads, LinkedIn & more uniquely Reddit. Though some are set via plugin vs GTM, limiting setup.

Some evidence of publisher tags are in place, primarily the Google Ad Manager backend, which is used to support ads direct on site.

The use of OneTrust as a CMP, but no reject all option. Notably Google in both GTM & Google Analytics fires, though with denied consent mode.

Google Tag Manager (GTM) is the core tag manager of choice for the all of the tracking implementation though no server side approach.

Google Analytics is the core tool used here but 3 different properties exist vs a more single setup.

Pretty limited here, with focus on the Google tags. But also some legacy cookie syncs through Zeta Global, who fire a whole load of unwanted tracking.

Interestingly Google focus with GA but also unique with Floodlights from CM360. More bespoke programmatic exists via Quantcast / Zeta / Microsoft.

Some evidence of publisher tags are in place, primarily the Google Ad Manager backend, which is used to support ads direct on site.

A robust CMP is in place, alongside a reject all option for users. Some unique custom server side elements also in the inner-workings of this setup.

Google Tag Manager (GTM) is the core tag manager of choice, which looks to be beefed up with sGTM server side clients for Meta / TikTok.

A big use of Google Analytics is in place here, both on the site usage side but also “ad impression” events when in-house ads show up.

A lot of internal backend infrastructure working to collate data, alongside the marketing pixels. Google Analytics in particular is heavily capturing signals.

A wider selection including Meta, TikTok, Snapchat, LinkedIn, Spotify & X. Some strange event tracking though, including ViewContent on Homepage.

Some evidence of publisher tags are in place, primarily the Google Ad Manager backend, which is used to support ads direct on site.

A robust CMP is in place, alongside a reject all option for users. No tags fire without consent.

The choice of Adobe Launch is a more unique setup to tag management but aligns to the Adobe backbone. No real server side structure in place.

The key focus is centered around a few Adobe Analytics properties, with no usage of Google Analytics.

A couple of core technologies are in place including Lytics, Salesforce & a bit of Adobe, but marketing fed by the Lytics integration in particular.

A wider selection including Meta, TikTok, Google Ads, X & Pinterest. Microsoft & LinkedIn both have issues on initial user consent trigger.

Some evidence of publisher tags are in place, primarily the Google Ad Manager backend, which is used to support ads direct on site.