Your first website, connected.

From registering a domain to reading your first report.

Guides · 2 min read

1. Register the domain

Add the site in Settings → Tracked Sites with its domain and timezone. The workspace hands back the snippet with your domain already filled in. Domains are unique across workspaces, so a domain’s events land in exactly one workspace. Like any client-side analytics, ingest cannot authenticate the sender.

2. Paste one script tag

Put it before the closing head tag, in the layout your pages share rather than on individual pages. That is the difference between measuring your site and measuring the three pages somebody remembered to edit.

<script defer
  data-domain="example.com"
  src="https://backend.funnelsights.com/js/script.js?d=example.com"></script>

That is the whole install. Pageviews, SPA navigations, scroll depth, engaged time, outbound clicks, file downloads and form submissions all start immediately — everything is on by default and each is turned off with an attribute set to "false". Tracking several domains from one snippet: comma-separate them in data-domain.

On Shopify

Put the tag in theme.liquid, before the closing head tag: Online Store → Themes → Edit code. That counts the storefront. Shopify never renders theme.liquid on checkout, thank-you or order status pages, so the tag cannot see a purchase. For those, copy the custom pixel from Settings → How to set up in the app and paste it into Shopify admin under Settings → Customer events → Add custom pixel. It counts those pages and records Add to Cart, Checkout Started and Purchase, with the order total as revenue.

3. Check it arrived

Load a page on your site and look for the pageview. One arriving confirms three things at once: the script loads, it reaches ingest, and the domain matches the site you are looking at. The full reports follow within 15 minutes, when the rollup next runs, so the day you install you will see today filling in rather than a complete history.

Useful attributes

• data-api — send events to your own domain instead, by proxying ingest.
• data-include / data-exclude — wildcard path rules, e.g. /blog/**,/docs/*.
• data-hash — for SPAs that route on the fragment.
• data-local — also record on localhost while you are developing.
• event-<key>="value" — attach a property to every event from this page.

Already running Google Tag Manager? Do nothing else — the next guide explains why your existing tags arrive on their own.