Gatelamp for web shops

Marketing tags that wait for a yes.

GA4, Google Ads and the Meta pixel stay quiet until a customer accepts. Consent Mode v2 follows the choice, in every language your shop sells in.

Where it gets hard

Tags that fire on page load

Analytics, ad and pixel tags usually run as soon as the page opens. A banner on top doesn’t stop them, so data goes out before anyone has chosen.

Consent Mode set up by hand

GA4 and Google Ads read Consent Mode signals. Set up by hand, the signals can start at “granted”, or miss the update when a customer changes their mind.

Customers in several countries

A shop that sells in several countries needs the banner, the settings and the cookie page in each language. Keeping every version in step by hand means one is always behind.

How it goes with Gatelamp

  1. Hold the tags back

    Mark each tag with its category and it runs only after a customer accepts that category. Consent Mode v2 starts with all four signals denied and updates the moment someone chooses. The Meta pixel and Microsoft UET get their own consent calls.

    Script blocking →
  2. Check what really fires

    A real browser visits the shop before a choice, after “Reject all” and after “Accept all”. Anything that needs consent in the first two rounds is marked as a problem, with the script that caused it.

    Site scanner →
  3. A banner in every shop language

    Banner, settings and cookie page per language, picked from the page, so a German page gets a German banner. Starter text in English, Dutch, German, French, Danish and Swedish to check and edit before it goes live.

    Every language →
  4. Proof of every choice

    Each choice is kept with a random consent ID, the choice per category and the banner version the customer saw, without IP addresses. Search a consent ID, or export a period as CSV.

    Proof of consent →
For example

Say you sell tea from the Netherlands to customers in Germany and Belgium. GA4, Google Ads and the Meta pixel sit in the page as text until someone accepts. A visitor on the German pages gets the banner in German and clicks “Reject all”: Consent Mode stays at denied, and the pixel gets the same answer. In the weekly scan, nothing runs after “Reject all”.

Gatelamp for web shops: common questions

Does Gatelamp work with Google Consent Mode v2?
Yes, from day one. All four signals start as denied and update the moment a customer chooses, and it works with GA4 and Google Ads. IAB TCF isn’t supported at launch; it matters for sites that sell personalised ads through Google AdSense or Ad Manager.
Is there a Shopify app?
A Shopify app with Shopify’s Customer Privacy API is planned, without a date yet, and so is a WordPress plugin. Until then, the plain script tag works on Shopify, as on any other site.
Does Gatelamp make my shop compliant?
No tool can promise that. Gatelamp builds in the published rules for banners, shows what your shop really loads and keeps proof of every choice. Whether your setup is lawful still depends on what you do with the data. It isn’t legal advice.

Gatelamp is in development, so plans, features and prices can still change. It helps you follow the published rules on cookies and consent; it isn’t legal advice.

Early access

Switch on early.

Join the waitlist for Gatelamp. We invite people in small groups, and waitlist members get the early price.