Usercentrics on your landing pages
Running Google Ads into the EEA, the UK or Switzerland now means sending Google a consent signal with each visitor. Usercentrics does that from one script tag with your Settings ID, and on LanderLab the tag goes in the domain's custom code, so every page published on the domain shows the banner and applies your configuration.
You define the services once in the Usercentrics Admin Interface: Google Ads, GA4, the Meta Pixel, your native network. Every landing page on the domain follows that setup, and new pages are covered the day they go live.
One Usercentrics script tag for the whole domain
The banner comes from Usercentrics' loader with your Settings ID. In the domain's custom code in LanderLab, it loads on every page published on that domain once live pages are republished, so the EEA campaign you launch next month starts with consent already in place.
Google Consent Mode v2 for EEA campaigns
Usercentrics sends Google the default consent state on load and the update once the visitor chooses, covering ad_storage, analytics_storage, ad_user_data and ad_personalization. Your Google Ads and GA4 tags on the landing page then work with the signals Google asks for on European traffic, and the conversions Google can count keep reaching your account.
Auto-blocking for the pixels on your pages
With auto-blocking, Usercentrics holds back the services its scanner found until the visitor agrees to them. Loaded from the domain's custom code, it runs ahead of the pixels your landing pages add.
Auto-blocking depends on your package, and the Admin Interface only offers it when your account has it. Without it, you mark each script with the service's exact name from the Admin Interface, and it waits for that service's consent.
Basic or Advanced Consent Mode, your call
Usercentrics supports both ways Google describes Consent Mode. In Basic, no Google tag loads until the visitor makes a choice. In Advanced, the tags load first with consent denied and adjust when the visitor answers. Which one fits depends on your legal advice and how much modeled conversion data you want Google to work with, and the banner on your landing pages supports either.
A clear list of what your landing pages load
Usercentrics' scanner logs the third-party calls it finds as data processing services. For a media buyer who adds a pixel per network and a widget per test, that list is a useful audit on its own: it shows what your pages actually load, which is what the banner has to account for.
