The analytics we deliberately don't collect
While other tools pivot to harvesting cross-platform data for AI, encer measures what a creator needs with consent-first analytics and no durable visitor identifiers.
Published · Updated
Creator tools are racing to collect more: connected social accounts, cross-platform behavior, and profiles that feed an AI assistant. encer is deliberately going the other way.
You still get the numbers that matter — visits, clicks, sources, and trends — without building a durable dossier on the people who visit your page.
Consent-first by default
Analytics load only after a visitor grants consent. Before that there is no tracking tag on the page at all, which is why a pre-consent scan simply finds nothing to connect to.
No durable visitor identifier
Visitor hashing uses a salt that rotates every day, so the same person is not trivially linkable across days. The goal is useful aggregate trends, not a permanent identity.
What that means for you
You measure what helps you decide — where visits come from and what people click — and you can tell your audience honestly that you are not quietly profiling them.
Real use example: choosing the next tour stop
A musician shares the same tour page from Instagram, a newsletter, and a partner community. After visitors consent, the creator compares aggregate visits by source and clicks on each city link. They can see that the partner community sends fewer visits but more venue clicks, without trying to recognize one visitor again on another day.
That is enough evidence to decide where to announce the next date. It is intentionally not enough to build a persistent profile of individual fans.