crowne counts page views and custom events without cookies and without a consent banner. Add a site in the app, then pick a way to send events.
Choose a setup
A browser setup has two parts: where the script comes from, and where its events go. Each part can be crowne's or yours.
| Script from | Events to crowne | Events to your endpoint |
|---|---|---|
| crowne's CDN | Script tag | Script tag with data-endpoint |
| The npm package | npm package | npm package with endpoint |
| Your domain | Custom domain with data-endpoint |
Custom domain |
"Your endpoint" is a custom domain that points to crowne, or a path on your own site that your server forwards with the first-party proxy.
You can also send events from your server, without a script. See Server events.
Which setup to pick
- Quickest: the script tag. Paste one line, and you are done.
- For apps with a bundler: the npm package. The code ships in your bundle, so no extra script loads.
- Fewer blocked visits, no code: a custom domain. Add one DNS record.
- Fewest blocked visits: the first-party proxy. Script and events use a path on your own site.
Some ad blockers block analytics. Ad blockers tells how they find it, and what each setup does against them.
Privacy
crowne sets no cookies and uses no local storage. A visitor id is a hash of a daily salt, the site, the address, and the browser. crowne deletes the salt after 48 hours, so nobody can trace an id back to a person. crowne never stores addresses or full browser strings. Read the privacy page.