Strong use of a CMP at the top of the page with reject all ability, which has a fairly custom implementation with Google Consent Mode.

Google Tag Manager (GTM) is the core tag manager of choice for the all of the tracking implementation with a server side backbone.

Bespoke server side approach to both Google Analytics and Adobe Analytics to measure on-site actions across the different verticals.

Bespoke cookie setting after consent alongside a well structured data layer, which is also powering the retail media offering.

A wider selection including Meta, Google Ads & Google Floodlights. Though quite a lot of different overlapping Google base tags in place.

Publisher tags are in place, but more to extend the retail media offering to make use of the on-site capabilities that Tesco operates.

Use of OneTrust as the core CMP but interestingly worded reject all button with the CTA “continue without accepting” alongside consent mode.

Tealium is the core tag manager of choice for the all of the tracking implementation with a server side backbone.

Core setup is based around Google Analytics with key events / data layer captured through the journey.

Some unique 1st party data settings in place behind a Tealium IQ backbone, but fairly standard structure overall.

A wider selection including Meta, X, Pinterest, TikTok, TTD, Snapchat, Microsoft, Google Ads & Google Floodlights. But some evidence of duplicate firing after consent.

Publisher tags are in place, but more to extend the retail media offering on more the Nectar side of the business.

Use of OneTrust as the core CMP and quite strict setup with “Reject All” CTA and consent mode.

A mix of Google Tag Manager but also Adobe Launch, to align with some of the Adobe heavy setup on-site alongside some server side tracking.

Core setup is based around Google Analytics with key events / data layer captured through the journey. Big switch to groceries domain however.

Adobe is the critical tool here, for both personalisation and audience capture on-site traffic with some custom tracking in local storage.

A wider selection including Meta, Google Ads, Microsoft Ads & Criteo. Though also evidence of CSP issues impacting certain tags.

Publisher tags are in place, which is primarily through the Criteo element of the retail media tracking.

Use of OneTrust as the core CMP and quite strict setup with “Reject All” CTA and consent mode.

Adobe Launch is the tag manager of choice, for both analytics and marketing tags.

A big Adobe Analytics user with plenty of eVars setup across the web journey and funnel.

Heavy users of the Adobe stack, including Target & Audience Manager to go alongside Launch / Analytics.

Focus towards Google Ads, Meta, X and Microsoft Ads tags on the site. Though no server side approach.

Doesn’t seem to be any evidence of any publisher tracking, with no complete retail media offering yet.

Use of OneTrust as the core CMP and quite strict setup with “Reject All” CTA and consent mode. But initial accept does not work.

Google Tag Manager (GTM) is the core tag manager of choice for the all of the tracking implementation with a server side backbone.

Core setup is based around Google Analytics with key events / data layer captured through the journey.

Some AWS backend in place to collect different signals but limited overall with emphasis on Google.

The likes of Meta, X, Snapchat, TikTok, CM360 with unique Blis / Tradedoubler. Microsoft doesn’t work.

Tracking is in place to make use of their MMG retail media network across the core ecommerce pages.

Use of OneTrust as the core CMP and quite strict setup with “Reject” CTA and consent mode.

A very custom implementation of Google Tag Manager (GTM) hosted on the Lidl first party domain.

A dual approach of Google Analytics and Microsoft Clarity, which are the core tags on site.

As strong as it can be, with a “LidlID” and custom cookies like utm_source captured in the data layer.

Pretty much no marketing tags here, with the focus purely on Analytics tracking.

Website is limited here, likely from the lack of ability to buy online in the UK through the site.

Use of OneTrust as the core CMP and quite strict setup with “Reject Cookies” CTA and consent mode.

A mix of Google Tag Manager but also Adobe Launch, to align with some of the Adobe heavy setup on-site alongside some server side tracking.

Core setup is based around Google Analytics with key events / data layer captured through the journey.

Adobe is the critical tool here, for both personalisation and audience capture on-site traffic with some custom tracking in local storage.

Primarily focused towards Google Ads, CM360 & Meta on shop page though some duplicate firing. Microsoft has issues.

Tracking in place to fuel their retail media network, primarily with some LiveRamp enrichment.

Strong use of a CMP at the top of the page with reject all ability, which has a fairly custom implementation with Google Consent Mode.

Google Tag Manager (GTM) is the core tag manager of choice for the all of the tracking implementation with a server side backbone.

Core setup is based around Google Analytics with key events / data layer captured through the journey. Heap Analytics / Microsoft Clarity also exists.

Google backbone but plenty of 1st party server tracking. A fairly strong data layer also exists to empower data management.

A wider selection including Meta, X, Pinterest, TikTok, Microsoft, Google Ads & Google Floodlights. Dotomi also exists with multiple cookie syncs.

Publisher tags are in place, in a specific role for Epsilon to take 1st party data for use in a retail media network for JLP.