Collection
The SDK buffers events and flushes in batches, falling back to sendBeacon on page unload with a CORS-safelisted content type so exit events are never dropped.
How it works
From one script tag to trustworthy numbers
A real ingestion pipeline with deduplication, deterministic sampling and verified installs — so the counts you see are the events that happened.
The setup
Four steps, usually under five minutes.
- 01
Register the website
Give the site a name, domain, timezone and currency. EvronAnalytics issues a unique tracking ID (aw_…) and a versioned SDK configuration bound to it.
- 02
Install one snippet
Paste the script tag into your <head>. It loads asynchronously from /tracker.js, reads its data-site-id attribute and pulls its feature configuration remotely — so you can change what is tracked later without touching your code.
- 03
Verify the installation
Verify Installation checks that the script is reachable on your domain and that a ping event actually arrives. No guesswork about whether the tag is really live.
- 04
Watch, then report
The debugger streams events as they land. Once data is flowing, build saved reports with the metrics, dimensions, funnels and chart types you need.
The snippet
This is the whole installation for most websites.
<script async src="https://analytics.evronstudio.com/tracker.js" data-site-id="aw_yoursite" ></script>
Custom events are optional: window.evron.track("signup", { plan: "pro" })
What happens behind the scenes
Identity
A first-party visitor ID persists across visits; sessions rotate after 30 minutes of true inactivity and emit a fresh session_start.
Ingestion
The public events API validates the tracking ID and domain, filters bots, applies deterministic per-visitor sampling, anonymises IPs and de-duplicates by event ID.
Storage & reporting
Events land in your workspace database with indexes tuned for time-series and dimension queries, then feed the overview, debugger and custom report engine.