iubenda on your landing pages
Agencies and advertisers in Italy and across the EU often manage their clients' privacy and cookie policies in iubenda already. With LanderLab, the landing pages you build for Meta and Google campaigns get the same banner: iubenda's embed script goes in the domain's custom code, and every page published on the domain shows it.
The banner is configured remotely in iubenda, so a change to its text, layout or buttons reaches the landing pages without anyone touching the pages.
iubenda's banner on every landing page of a domain
iubenda's current snippet is a single script, with the banner configured remotely in your iubenda dashboard. In the domain's custom code in LanderLab, it loads on every page published on the domain.
For an agency, that means a new landing page for a client is covered the moment it's published, with the banner the client's legal adviser already approved.
Auto-blocking by purpose
iubenda's scanner finds the services on your site, and auto-blocking holds their requests until the visitor consents. Services are grouped into five purposes: necessary (1), functionality (2), experience (3), measurement (4) and marketing (5). A Meta Pixel under marketing stays blocked until marketing is accepted, and you can move a service to another purpose if the default doesn't fit.
Consent signals for Google campaigns
iubenda is a certified CMP with Google Consent Mode v2 support, so your Google Ads and GA4 tags on the landing page get the visitor's choice. That's what Google asks advertisers to send for EEA traffic, and it keeps conversion measurement working for the visitors who accept.
Pixels you add by hand follow the same purposes
Not every script comes from the scan. When you add a pixel for a new network through a page's custom code, iubenda's manual method ties it to a purpose number, so it waits for the same consent as the services auto-blocking already handles. One rule for every tracker on the landing page, however it got there.
One consent setup per client, not per page
Agencies lose time when every landing page needs its own consent decisions. With iubenda in the domain's custom code, the decision is made once per client domain, in the client's own iubenda account, and every page you publish there inherits it. Your team builds and tests; the client's compliance stays where the client keeps it.
