Mercleo
Join the beta
Getting started

Sites

A site is a domain you register in Analytics to get a unique tracking snippet, install it, and see whether events are actually arriving.

A site is a domain you register so Analytics can track it. Registering a site generates a unique snippet token: you paste the tracking snippet into your page's <head> and Analytics starts collecting page views, sessions, custom events, and form submissions. You manage every site from the Sites page in Settings.

Registering a site

Open Sites from Settings and click New site. The form has two fields:

  • Domain: required. Enter the hostname only, with no protocol and no path, for example example.com or app.example.com. The value is lowercased before it is saved.
  • Display name: optional, up to 255 characters. A human-friendly label shown in the sites list. If left blank, the list shows a dash in the Name column.

Click Create site. On success, Analytics generates the snippet token and opens the new site's detail page so you can copy the install snippet.

An invalid hostname returns an error asking for a plain domain like example.com; a domain you have already registered on this account returns an error pointing you to the existing site record.

Installing the snippet

The site detail page has an Install snippet section with three parts.

Tracking script (required) captures page views, sessions, custom events, and form submissions. Paste it into the <head> of every page you want tracked:

html
<script async src="https://pulse.mercleo.com/pulse/pulse.js" data-token="YOUR_TOKEN"></script>

Cookie consent script (optional, recommended) renders the consent banner and gates tracking until consent is granted. Load it before the tracking script:

html
<script async src="https://pulse.mercleo.com/pulse/pulse-cmp.js" data-token="YOUR_TOKEN"></script>

Copy the exact tags from the site detail page rather than typing them. Each one carries this site's own token, with a copy button beside it.

Identity stitching happens automatically. Once window.pulse.identify(email) is called from your site, Analytics links the anonymous visitor to a contact in your account and retroactively stamps all of that visitor's prior page views and events with the contact reference. This unlocks the cross-product timeline in Reach.

Two attributes on the tracking script tag give you control over what Analytics tracks, without opening the dashboard. Add data-exclude-paths to skip any page whose path starts with one of the listed prefixes, for example data-exclude-paths="/admin,/preview". Analytics never sends events for a matching page:

html
<script async src="https://pulse.mercleo.com/pulse/pulse.js" data-token="YOUR_TOKEN" data-exclude-paths="/admin,/preview"></script>

To keep your own visits out of the data, load the site once in your browser with ?_p_optout=1 appended to the URL, for example https://yoursite.com/?_p_optout=1. Analytics stores the opt-out in that browser's local storage and stops tracking the device from then on. Visit again with ?_p_optout=0, or call window.pulse.optIn() from the browser console, to resume; window.pulse.optOut() does the same as the query parameter. The opt-out applies to that one device only, not to your whole account.

The sites list

The list shows every site on the account, newest first, with a count above it. The columns are Domain (click to open the site), Name, Status, Data, and Created.

The Status badge shows Active or Inactive; a paused site reads Inactive. This is separate from the Data column, which tells you whether events are actually arriving. See Troubleshooting: is tracking working? below for what each state means.

Each row has an actions menu with Edit, Pause tracking or Resume tracking (depending on current status), and Delete.

Editing, pausing, and deleting a site

From the detail page or the row menu, Edit lets you change the Display name, the Unresolved visitor TTL (days) (how long anonymous visitor data is retained before it is pruned, between 1 and 365 days), and the Active checkbox (accept new tracking events).

Pause tracking turns the site Inactive and stops it accepting new events without deleting anything. Resume tracking turns it back on; pausing does not delete data, it only affects whether new events are accepted.

The Danger zone on the detail page holds two actions. Regenerate snippet token generates a new data-token value and asks you to confirm before applying. After regenerating, every existing installation stops tracking until you replace the snippet with the new token.

Delete site asks you to confirm, then soft-deletes the site: it disappears from the list and stops tracking, but events already collected are retained. Deletion cannot be undone. To stop tracking temporarily, use Pause tracking instead.

The Consent banner card on the detail page has a Configure button that opens the site's consent settings, split into three tabs: Banner, Scripts, and Cookies. Banner controls the cookie consent banner your visitors see. Scripts is where you register third-party scripts and their consent category. Cookies shows what Analytics detected running on your site.

Troubleshooting: is tracking working?

The Data column on the sites list, and the matching field in the site's Statistics card, show the same ingest-health indicator, derived from the most recent event Analytics received for that site:

  • Receiving: an event arrived in the last 24 hours.
  • No recent data: the site has received events before, but nothing in the last 24 hours.
  • Awaiting data: no event has ever arrived. The most common cause is that the tracking snippet is not installed yet.

If a site still reads Awaiting data after you install the snippet, check that: the script tag sits before the closing </head> tag; the /pulse path segment in the script's src was not dropped or edited; the page is not caught by a data-exclude-paths prefix that is broader than intended; and you have not opted your own browser out with ?_p_optout=1 while testing.

Updated