Forty properties. One place to answer for them.

Every market, every domain, every language, with roles that decide who sees which. Measurement that sets no cookies, an audit trail on every run, and the fix shipped into your own codebase rather than a ticket.

ChatGPT
Perplexity
Google
Claude
Grok
Codex

The hard part was never the SEO. It is getting anything shipped.

Cookies set on your visitors. Nothing to put in a banner.

Nothing here needs a six-week review.

One tag, no cookies, and an audit trail on every run. The parts that usually stall in legal or in the dev queue are the parts that were designed to go through them.

Tracking snippetCopied

Paste this into the <head> of your site. Any framework.

<!-- Keupera Analytics -->

<script>window.KEUPERA_API_KEY = "kp_live_••••4c1a";</script>

<script src=".../tracker.js" async defer></script>

Receiving events · first pageview 2 minutes ago

One tag, and no consent conversation

A single script tag, or a server-side package if you would rather never ship a script. No cookies are set and nothing is stored on the visitor's device beyond a session id that dies with the tab, so there is nothing to add to a banner and nothing to ask consent for.

One workspace. The whole estate.

Six tools, every property, one organisation. Roles decide who opens which, and the API hands the lot to your warehouse.

Answers the questions procurement asks.

Talk to sales

Four roles per organisation, and a client-role invite is refused outright unless it names the sites that person may open. Analytics sets no cookie and stores a one-way hash rather than an address. Every run is kept with its status and its results, so an audit has something to read.

Four roles per organisation
Access scoped to sites
Every run kept and dated
Cookieless, no banner
Visitors hashed, never raw
GDPR ready, data is yours
One tag, any framework
REST API and MCP server

Start with one property, not a programme.

Prove it on one property

Put the tag on a single site, or a package server-side. No cookie, no banner change, nothing for legal to open a ticket about.

  • One script tag or a package
  • No consent banner change
  • Live in an afternoon
  • No credit card

<!-- Keupera Analytics -->

<script>window.KEUPERA_API_KEY = "kp_live_••••4c1a";</script>

<script src=".../tracker.js"></script>

Copied
First pageview2 min ago

/ · Chrome · Desktop · Germany

Unique Visitors1

For the security review

What is stored, what never is, and exactly which people can open which properties. One page, before anybody signs anything.

  • Stored and never-stored, listed
  • Four roles per organisation
  • Client access scoped to sites
  • Every run kept and dated
What Keupera storesone page

Stored

A one-way hash of the visitor
The path and the referrer
UTM parameters on arrival

Never stored

No cookies, no device storage
No raw IP addresses
No cross-site identity

Who can open what

Super adminEverything, and the only role that can change roles
AdminInvites people and sets website access
MemberWorks in the properties they are given
ClientNamed websites only, enforced on the invite

Into your own stack

Take the markup and ship it through your own review, and pull every table from the API into the warehouse you already run.

  • Schema you review before shipping
  • REST API over every table
  • One key per organisation
  • MCP server for assistants
application/ld+json

{

"@type": "Organization",

"name": "Acme Inc.",

"sameAs": [ … ]

}

WWordPress
SShopify
WWebflow
CCustom / Next.js

The questions your reviewers ask

No. Analytics Studio sets no cookie and stores nothing on the visitor's device beyond a session id that dies with the tab. A visitor is a one-way hash of an address, a browser string and your site id. Be clear on the trade: people behind one office address collapse into one visitor, and someone who changes network counts twice.

There are four roles in an organisation. A super admin owns it and is the only role that can change anyone's role. An admin invites people and sets website access. A member works in the properties they are given. A client-role invite is refused outright unless it names the websites that person may open.

Those are a conversation rather than a checkbox on this page, and we would rather say so than imply something is shipped that is not. Bring your requirements to the call and you will get a straight answer on what exists today, what is on the roadmap, and what is not happening.

Yes. Every table behind the dashboard is on the REST API on one key per organisation, using the same date parameters the dashboard uses, and there is an MCP server if you would rather point your own assistant at it. Retention depends on your plan, and a date outside that window is deleted rather than archived, so pull anything you need to keep.

Less than you expect. Analytics is one script tag, or a server-side package if you would rather not ship a script at all. Brand Identity hands you the schema as markup to review rather than a recommendation to translate. The only thing that genuinely needs a deploy is the code you have already read.

Sites are grouped under one organisation with their own limits, and roles scope who opens which. The honest constraint is seats and site allowances on your plan rather than the software, which is exactly the sort of thing to settle on the call rather than discover in month three.

Your time to shine

Take your SEO and GEO to the next level.