GATE Documentation

Get a site tracked, then ask your bot how it's doing — real visit and pageview counts, no third-party analytics service, no cookie banner.

Who this is for

You have a site — a landing page your bot deployed, or any other site you run — and you want to know whether anyone's visiting it, and what they're looking at. You'd rather not hand that data to a third-party analytics company, or bolt a cookie-consent banner onto a page that didn't need one.

Before you start

Lens turned on for your org. If your bot says it can't track a site, ask your org's admin to check tool access for Lens.
A site to track — a GATE-hosted project, or any other domain you can add a line of code to (or hand off to whoever maintains it).
A little patience after tracking starts. Lens only counts visits from the moment it's live on the page — there's no history to import, and a quiet site will honestly say so before the numbers catch up.

Steps

Start tracking the site. Tell your bot: "Start tracking acme.com with Lens." It creates the site and comes back with a snippet — a single line of code that has to live on every page you want counted.
Get the snippet onto the page. How, depends on where the site lives:
- A GATE-hosted project: ask your bot to add it — "Add the Lens snippet to our site and deploy it." Your bot edits the page and pushes the change itself.
- Any other site: your bot hands you the snippet to pass along to whoever maintains that site's code — it goes in the page <head>, once, on every page you want tracked.
Give it a little traffic, then check in. Visit the site yourself a couple of times, then ask: "How's traffic on acme.com?" Your bot reports real visits and pageviews for the last 7, 30, or 90 days — or tells you honestly that there isn't enough traffic yet if the count is still at zero. That's not a bug: Lens never guesses a number it doesn't have.
Ask for the detail that matters to you. "What are the top pages on acme.com this month?" "Where's our traffic coming from?" "What countries and devices are people using?" Your bot pulls top pages, referrers, countries, and device breakdowns straight from the same report.
Check in on recent visitors. "Show me recent visits to acme.com." You'll get a list of anonymous sessions — country, device, the page they landed on, and how long they stuck around. No names, no emails, nothing that identifies a person.
Go deeper in the dashboard, if you want it. Session replay (a masked recording of how someone scrolled and clicked) and click/scroll heatmaps live on Lens's dashboard page, not in chat — your bot can point you there when you want more than the numbers.

What you'll see

In chat: the tracking snippet at setup, and traffic reports — visits, pageviews, top pages, referrers, countries, devices, and recent sessions — whenever you ask.
In the dashboard: the full Lens view for the org, including sites, session replay, and heatmaps, at the Lens page.
On the tracked site: nothing visible at all — no cookie banner, no widget, just the page working as it always did.

Why this is different from the usual analytics setup

Lens doesn't use a cookie, so there's no consent banner to bolt onto your page for it. It doesn't send anything to a third-party analytics company — every row lands in your GATE server's own database (wherever your server is hosted — for EU-hosted servers, the data never leaves the EU) and stays there under that site's retention setting (30–90 days; 90 by default). Session replay is masked before it ever leaves the browser: typed text and page content are blanked out, so a replay shows how someone moved and clicked, never what they typed or read. If you've ever hesitated to add analytics because of the privacy trade-off, this is the version built to not make you choose.

Troubleshooting

"Not enough traffic yet" and you know people have visited. Confirm the snippet actually made it onto the live page — ask your bot to check, since a change that wasn't deployed (or a snippet that was pasted somewhere other than the page <head>) never reaches Lens at all. On an external site, this is the most common gap: the handoff step didn't happen yet.
Numbers stopped updating. Ask your bot whether tracking got paused for that site — it's reversible, and resuming picks collection back up with nothing lost in between.
You rebuilt the site and traffic disappeared. If the rebuild dropped the snippet (a new template, a redesign, a framework swap), it has to go back in — ask your bot to check that it's still there after any redesign.
You want to stop tracking a site for good. Say so — this permanently deletes everything collected for that site and can't be undone, so make sure that's really what you want first.

Going deeper

Built-in tools — the concept page
Launch a landing page — get a site live first