CookieScript on your landing pages
Paid traffic rarely respects borders, and privacy rules now differ by US state as well as by country. CookieScript is one of LanderLab's built-in integrations: set it up once, it's saved to your LanderLab account, and every page you switch it on for shows the banner the visitor's location calls for.
It's a good fit for US lead gen that crosses state lines and for buyers who run a domain per offer. One CookieScript account manages the banners for all your domains, and each one follows the scan of its own site.
CookieScript saved once, switched on per page
With CookieScript built into LanderLab, there's no snippet to copy into each page or to keep in sync when you change the banner. The setup is saved to your LanderLab account and switched on for the pages that need it, including the ones you haven't built yet.
The right banner for each market
Paid traffic rarely stays in one country. CookieScript's geo-targeting picks the banner by the visitor's location, down to US states, so a visitor from Germany and a visitor from Texas can see different banners, and you decide which regions see one at all.
CookieScript asks for geo-targeted code to load on the page itself rather than through Google Tag Manager, and a built-in integration is exactly that. One setup, the right banner per region, no per-geo copies of your pages.
Many offer domains, one CookieScript account
If you run a domain per offer or per vertical, CookieScript manages the banners for all of them from one dashboard. Each banner follows the scan of its own site, so a new solar domain doesn't inherit the cookie list of your insurance domain, and in LanderLab each one is a saved setup you pick on the pages it belongs to.
Targeting pixels that wait for targeting consent
CookieScript sorts scripts into categories: strict, performance, targeting, functionality and unclassified. Ad pixels belong under targeting and stay blocked until the visitor accepts it, so the Meta or native pixel on a landing page fires for the visitors who said yes and not for the ones who didn't.
Consent records when a partner asks
CookieScript records each visitor's consent. Depending on the plan, a record can hold the consent ID, the status, the date and time, the country and a proof of consent. When a network, a buyer or a brand asks how consent was handled on the page that sent them traffic, the answer is a record, not a screenshot of the banner.
