The Atriqo tracker

What Atriqo tracks

• Pageviews
• Sessions
• Referrers
• Pages
• Countries
• Devices
• Browsers
• Operating systems
• UTM parameters
• Custom events
• Outbound links
• File downloads
• 404 pages (opt-in)

What Atriqo avoids

No cookies, no fingerprinting, no cross-site tracking, no raw IP storage. Full details in How Atriqo works — What the tracker avoids.

Custom events

Custom events are available for actions like signups, button clicks, downloads, or other product events.

Generic examples:

• signup
• pricing_view
• docs_install_viewed

// Track a custom event
window.atriqo.track('signup', { plan: 'starter' });

Call window.atriqo.track(name, properties) once the tracker has loaded. Because the snippet loads async, window.atriqo is undefined until track.js runs — so guard early calls with optional chaining, e.g. window.atriqo?.track('signup', { plan: 'starter' }). Once loaded, the tracker installs window.atriqo.track at the very start of its script, so the call is safe even when a privacy guard (opt-out, DNT, localhost) is active — it simply does nothing.

Event names

A name must be 1–64 characters long and use only ASCII letters (a–z, A–Z, without accents), digits, underscore or hyphen. Any other name is silently ignored: no event is sent and no error is thrown, so check names that never show up in your report.

• signup and pricing-view are valid.
• Sign up (space), signup.done (dot) and registro_éxito (accent) are ignored.

Properties

Properties are optional. An event keeps at most 10 of them and drops the rest. Keys and values are converted to strings and truncated to 64 characters.

Before storage, the parts of a property value that look like personal data (email addresses, phone numbers, card numbers, IBANs and long digit sequences) are replaced with the marker [REDACTED]; the rest of the value is kept. Keys get the same treatment for email addresses. If that replacement makes a key or value longer than 64 characters, it is replaced entirely with [REDACTED]. This is a safety net, not a licence: don't send personal data in properties.

Where they appear

There is no per-plan cap on custom event names. Custom events are recorded, listed with their counts in the events report of your dashboard on every plan, and included in CSV export; on Growth and Business you can also break a custom event down by its properties in the dashboard and track it as a goal.

For a step-by-step walkthrough, see the guide Custom events and goals.

404 pages

404 page tracking is opt-in and off by default. Enable it per site in Settings → Tracking. Atriqo counts a 404 when the error page your server serves includes this tag:

<meta name="atriqo:status" content="404">

Put the tag in the <head> of that page, before the tracker script. The tracker looks for it once, when it loads, and the snippet is async, so a tag placed after the script may be missed. 404s that a single-page app resolves client-side, without a page load, are not detected.

The report is the "404 pages" tab of the events panel in your dashboard. While it is enabled, each 404 counts as a billable event toward your monthly quota, on top of its pageview (2 in total).

Next

Want a quick summary of the privacy commitments — hosting, IP handling, cross-site rules? See the Privacy at a glance page, or dive into the full methodology at How Atriqo works.