CookieYes integration

Your landing pages change every week, and the cookie list should keep up. CookieYes is built into LanderLab: switch on the banner, let it rescan on a schedule and keep a log of each visitor's choice.

  • Built-in integration
  • Landing pages, Quiz funnels

Why connect it

Why CookieYes and LanderLab

  • Built in, no code to paste

    CookieYes is an integration in LanderLab, saved to your LanderLab account and switched on for the pages that need it.

  • Scans that follow your tests

    A monthly scheduled scan finds the cookies new pages and pixels set, so the banner's list doesn't fall behind your launches.

  • A consent log for audits

    Each consent is recorded with an ID, the country, the status, the date and time in UTC and a proof of consent.

  • Consent Mode v2 for Google campaigns

    CookieYes is a Google-certified CMP with Consent Mode v2 and IAB TCF support, so Google's tags get the visitor's choice.

  • The right banner for each geo

    Geo-targeting shows a GDPR banner where it applies and the banner you choose elsewhere, from one setup.

CookieYes on your landing pages

CookieYes is one of LanderLab's built-in integrations. Set it up once, it's saved to your LanderLab account, and you switch it on for the landing pages, advertorials and quizzes that need a banner. There's no installation code to copy between pages.

It fits media buyers and small brands who run many pages and change them often: ecom advertorials, lead gen landing pages for several geos, a quiz for a new angle every week. The scheduled scan catches the pixels you add for each test, and the consent log answers the question when a partner asks how consent was handled.

The same CookieYes banner on every landing page

With CookieYes built into LanderLab, a banner is something you switch on, not something you install. The setup lives in your account, so the fifteenth landing page gets the same banner as the first, and nobody has to remember where the snippet went.

CookieYes's automatic script blocking holds third-party cookies until the visitor opts in, which is what lets you keep ad pixels on a page that takes EU traffic.

Monthly scans that catch new pixels

Landing pages change more often than most sites: a new pixel for a new traffic source, a tracker swapped for another, a widget added for one test. CookieYes can scan the site on a monthly schedule and sort the cookies it finds, so what you added for this week's test doesn't sit on the page unlisted in the banner.

One offer, traffic from several regions

A landing page that takes clicks from the US and the EU doesn't need two versions. CookieYes's geo-target banner shows each visitor the banner set for their region, so EU visitors get a GDPR banner with a reject option and the rest see what you've chosen for them, or nothing.

Use cases

Ways to use CookieYes on paid traffic

  • 01

    Supplement advertorials in Ireland and the EU

    An Outbrain campaign runs readers through an advertorial to the store. CookieYes holds the Outbrain and Meta pixels until consent, and the consent log shows each reader's choice if the network asks.

  • 02

    One offer, several geos

    A landing page taking US and EU traffic uses the geo-target banner, so EU visitors get a GDPR banner with a reject button and US visitors get the one you set for them.

  • 03

    Weekly creative tests

    Each new test brings a widget or a pixel. The monthly scheduled scan finds what the new pages set and lists it in the banner without a manual audit.

FAQ

CookieYes integration FAQ

Anything not here, ask us.

CookieYes and LanderLab

Does LanderLab integrate with CookieYes?

Yes. CookieYes is built into LanderLab: set it up once and switch it on for the pages that need a cookie banner.

Is CookieYes a good fit for landing pages?

It suits teams that publish and change pages often: scheduled scans follow new pixels, and the consent log answers partners' questions.

Does CookieYes block pixels before consent?

Yes. Its automatic script blocking holds third-party scripts that set cookies until the visitor consents to their category.

Does CookieYes support Google Consent Mode v2?

Yes. CookieYes is a Google-certified CMP and supports Consent Mode v2 and IAB TCF.

Can CookieYes keep a record of consent?

Yes. The consent log records the consent ID, country, status, date and time and proof of consent.

Do I need a plugin or Zapier to use CookieYes with LanderLab?

No. CookieYes is built in, with nothing in between.

Other integrations

Plug in the rest of your stack.

Connect CookieYes and launch your next page.

Build the page, switch CookieYes on and send your ads to it. Free to start, no card.

From one prompt to qualified leads

Watch one prompt become a live solar quote funnel, every lead routed to your buyer, and the leaks flagged before they eat your budget.

0:00
0:59