Measured by your site.
Kept in your account.
First-party, cookie-free analytics where consent is the mechanism: every tracker blocked until its category is approved, and up to 90 days of history joining the record when a visitor becomes someone you know.
Three parts. One approach to your visitors' data.
Measurement
Pageviews, funnels, goals and custom events, collected by one small script on your own site.
Consent
A banner you design over four literal categories, with a scanner that keeps every script blocked until its category is approved.
The handoff
When a visitor becomes a contact, up to 90 days of their anonymous history attaches to the record automatically.
Consent is the mechanism. Not a banner over the top.
Visitors see a consent banner you design, with four categories. Behind it, a cookie scanner catalogues every script on your site and keeps each one blocked until its category is approved.
- Four categories: necessary, analytics, marketing, personalization
- A cookie scanner that catalogues every script
- Tracker blocking until consent
Measurement. Cookie-free by default.
One small script tracks pageviews, funnels, goals and custom events, first-party. There is nothing to gate, because nothing leaves your site.
- One small script, cookie-free by default
- Funnels, goals and custom events
- A live visitor count for launch day
When someone consents. Their history joins the record.
A stranger reads your site for weeks before they fill anything in. When they finally do, up to 90 days of that anonymous history attaches to the new record automatically, encrypted at rest.
- Up to 90 days of history attaches on consent
- Automatic, and encrypted at rest
- The new contact lands in Audience, not in a report
Against your tracking tag. And the banner bolted over it.
The norm is handing your visitors to someone else, then adding a consent banner that changes nothing underneath. Here the banner is wired to the blocking.
| A third-party analytics tag | Mercleo Analytics | |
|---|---|---|
| Where the data goes | To the vendor, then back as reports | Collected by your site, kept in your account |
| The consent banner | Bolted on over the top | The switch that actually blocks the trackers |
| A visitor you finally meet | A number in a report | A contact with 90 days of history attached |
| Cookies | The reason for the banner | None by default |
- Also in Analytics
- Pageviews and referrers
- Realtime view
- Funnels
- Custom events
- Goals
- Form analytics
- Site performance
- Paid channel reporting
- Error tracking
- Consent categories
- Cookie scanner
- Tracker blocking
One record. And your Analytics built on it.
Questions we get asked.
No. Your website is measured the same way, and unlike Google Analytics, what it learns lands on your actual contact records.
No. The banner, the scanner and the blocking are part of the analytics area, not a second subscription.
In your account. It is collected by your own website and stays there: no advertising networks in the loop.
Up to 90 days of their anonymous history attaches to the new record automatically, encrypted at rest.