Documentation

1. Install tracking

• Create an account and verify your email address.
• Add your website. Enter the domain (you can paste a full address); it is saved without https:// and without www.
• Open the website's Install tracking page and copy the snippet.
• Paste the snippet just before the closing head tag on every page you want to measure.
• Load one of those pages, then press Check again in the Installation Center. Only an event that actually arrives proves the install works.

Domain matching

Events are accepted only from pages whose domain is the saved domain or one of its subdomains. If you saved example.com, pages on example.com, www.example.com, and shop.example.com are accepted; other domains are refused and counted as refused requests.

2. Custom events

Record an action by calling metrivue with a name, for example metrivue('signup'). Names may use letters, numbers, spaces, and the characters _ . : - and can be up to 80 characters.

If your code may run before the snippet has loaded, define this line first and the snippet will send the queued events: window.metrivue = window.metrivue || function(){ (window.metrivue.q = window.metrivue.q || []).push(arguments) }

3. Single-page apps and campaigns

• Navigation that changes the address through the browser history is recorded as a pageview automatically.
• The utm_source, utm_medium, and utm_campaign values in the page address are recorded with the pageview.

What is recorded

• Recorded: the page path without its query string or fragment, the hostname of an external referrer, the three UTM values, a shortened user-agent string, and an anonymous visitor identifier.
• The visitor identifier is a one-way hash that changes every day, so a visitor cannot be followed from one day to the next.
• Not recorded: IP addresses, cookies or local storage values, full page addresses with their query strings, or form contents.
• Visits that send Do Not Track or Global Privacy Control signals are not recorded at all.

How metrics are defined

• Pageviews: each page load or in-app navigation the snippet reported.
• Visitors: distinct anonymous visitors per UTC day, added up across the selected range. The same person on two days counts twice.
• Traffic channels: an estimate from the referrer and UTM values. Visits from apps that hide referrers appear as Direct.
• Sessions: a visitor's events with no gap longer than 30 minutes. Measured only from the date shown on the Analytics page, and a visit crossing UTC midnight counts as two sessions because visitor identifiers reset daily.
• Goals: conversions count matching events; converting sessions are distinct sessions with a matching event; the conversion rate is converting sessions divided by all sessions with any event, so it is available only from the date sessions started being measured. Funnels are not available.
• Dates and days use UTC.

Availability checks

Metrivue requests your home page over HTTPS about every 15 minutes, following up to 5 redirects. A check is OK when the final status is below 400. Availability is the share of checks that succeeded; it is not time-weighted uptime. A site served only over HTTP is reported as failing.

Troubleshooting: no events arrive

• View the page source of a live page and confirm the snippet is present exactly once.
• Check that the saved domain matches the page you load. The Installation Center lists refused requests with reasons.
• Make sure the website is Active, not paused.
• Browsers and extensions that block trackers, and Do Not Track or Global Privacy Control signals, prevent events from being stored.
• Caching plugins or CDNs may serve old pages without the snippet. Clear them after adding it.
• If your site sends a Content-Security-Policy, it must allow the script and the connection to your Metrivue address.
• Each visitor address can send up to 120 events per minute per website; more are refused.