Get started

Quick start (5 min)

Get from "I have a domain" to "I see live events in my dashboard" in five minutes. No build step, no cookie banner, no third-party scripts.

1. Create a property

Log in to the portal → Properties → New property. Pick the type (web, ios, android) and add at least one domain (for web) or bundle identifier (for native).

You will get a public ingest key that looks like:

pk_a3f09c2e71bd…

This key is safe to put in client-side code. It only authorises sending events to that one property; it cannot read anything back.

2. Drop the tracker on your site

Add this once, anywhere in your HTML (the <head> is fine, but it works in the body too):

<script defer
  src="https://tracera.eu/t.js"
  data-pk="pk_a3f09c2e71bd">
</script>

That's it. The tracker is small, async, and uses navigator.sendBeacon so it never blocks page navigation. No cookie is set. No localStorage entry is created. Nothing is fingerprinted.

Self-host the tracker? For maximum ad-blocker resistance you can serve t.js from your own (sub)domain and proxy the ingest endpoint. See Web tracker SDK → Self-hosting.

3. See it in the dashboard

Open your property in the portal and switch to the Realtime view. Visit the page you just instrumented in another tab. You should see the event appear within a second or two.

If nothing shows up, jump to Web tracker → Troubleshooting.

4. Send a custom event

Any meaningful user action can become a named event with optional key–value properties:

tracera('event', 'signup_completed', { plan: 'pro', value: 49 });

Use this for conversions (signups, purchases) and product analytics (feature usage). The dashboard will group events by name and let you filter by property values.

What you didn't have to do

Add a cookie consent banner for analytics. There are no analytics cookies.
Configure GDPR-related opt-outs. The visitor identity is not personal data.
Sign anything to use a US sub-processor. There isn't one.
Wait for a build pipeline. The snippet is the integration.