Client sites, each in its own style.
Look after every client’s cookie banner from one workspace. Each site keeps its own banner, tools and records, and a site that needs no banner shows none.
Where it gets hard
A different setup for every client
Each client has its own brand and its own tools: Google Analytics and a chat widget on one site, a booking embed and the Meta pixel on the next. Fitting the banner and the cookie page to each one is work you repeat per site.
Proof when a client asks
A visitor complains, or a client wants to know how their site collects consent. Finding out what the banner said at the time, and what that visitor chose, is hard when nothing was kept.
A bill that grows per domain
Many consent tools charge per domain or per pageview. Every new client site adds to the bill, and so does a client’s busy month.
How it goes with Gatelamp
Every client site in one dashboard
Each site gets a status lamp: off when no banner is needed, on when it asks, and a warning when something’s wrong. Switch between sites at the top. Each one keeps its own banner, inventory and records.
All your sites →A banner in each client’s style
Set a client’s colours, font, corner radius, border and shadow once, and the banner and settings follow. Preview it on the real site at desktop and phone width before you publish. The rules built into the banner stay the same on every site.
Your site’s style →Know what each site loads
A real browser visits every client site each week, and after a deploy if you like. Findings are matched against an open cookie database and your own library, and each one names the script that caused it.
Site scanner →Proof when a client asks
Every choice is kept with a random consent ID and the banner version the visitor saw, without IP addresses. Search a consent ID, or export a site’s records for a period as CSV.
Proof of consent →
Say your studio looks after twelve client sites. The dashboard shows five with a banner, each in its client’s colours and font, and seven with the lamp off. Someone adds a chat widget to a bakery’s site on Friday, and on Saturday morning you get an email naming the page and the script. When a hotel client asks what a guest chose, you search the guest’s consent ID and send over the record.
Gatelamp for agencies: common questions
- Can my clients log in to see their own site?
- Client access to a single site is planned, without a date yet. At launch you can invite people to your workspace with a role, and export a site’s consent records as CSV to send to the client.
- How is Gatelamp priced for an agency?
- Monthly and per workspace, never per pageview, so a client’s busy month doesn’t change what you pay. The Studio plan is for portfolios and agencies: many sites, scans after every deploy and team members with roles. Prices follow before Gatelamp opens, and everyone on the waitlist gets the early price.
- Does Gatelamp make my clients’ sites compliant?
- No tool can promise that. Gatelamp builds in the published rules for banners, shows what each site really does and keeps proof of every choice. Whether a setup is lawful still depends on what the client does 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.
Also for
Switch on early.
Join the waitlist for Gatelamp. We invite people in small groups, and waitlist members get the early price.
The form didn’t load. You can also join on our waitlist page.