LandexHub ConsentValidation site W14
Other setups

Overview

Validation site W14

How LandexHub Consent behaves on a site like this

This is an ordinary WordPress site with the setup below. We install the plugin, visit the site as a new visitor and check, with three independent tools, what loads before and after a choice in the cookie banner.

GeneratePressCloudflare edge cachegtag.jsPixelYourSiteYouTube as a linkAdvanced Consent Mode

How it works

1Set up

LandexHub Consent with this theme, cache and tracking. gtag.js and PixelYourSite behind Cloudflare. Pages are cached at Cloudflare's edge (Cloudflare Free, Cache Rule "Eligible for cache" for HTML).

2Visit

First visit, reject, accept, analytics only, withdraw, returning visitor.

3Compare

Consent Monitor, Website Evidence Collector and a manual check against what the documentation promises.

What should happen here

Before any choiceCookieless only

No analytics or marketing cookies. Google sends only cookieless pings (gcs=G100). The PixelYourSite script waits.

Reject allNothing tracks

Same as before any choice; every Consent Mode signal is denied.

Analytics onlyMeasures

GA4 measures (gcs=G101); no marketing requests or cookies.

Accept allMeasures

GA4 measures with full consent (gcs=G111). The Meta Pixel starts.

Withdraw consentNothing tracks

No new tracking starts; after a reload the site behaves as after Reject all.

Page from Cloudflare’s cacheNothing tracks

A page served by Cloudflare behaves the same; one visitor’s choice never reaches another, because the choice lives in the visitor’s browser.

YouTube videoNothing tracks

Replaced by a link, as the documentation recommends. Nothing loads until the visitor clicks.

Try it yourself in a private window with your browser’s network tab open. Change your choice any time: Cookie settings

LandexHub Consent validation site W14All validation sitesDocumentationPrivacy and cookiesCookie settings