How to add VisitTrack with Google Tag Manager

The loader is the one VisitTrack's install screen generates for GTM — it creates the script element with data-site set explicitly — plus the one-line queue stub, so tags that fire before the script has loaded can still send events. If you can edit your site's HTML, a direct install is slightly more robust — content blockers that block GTM also block everything GTM loads.

How to install VisitTrack on Google Tag Manager

1. 1

   Step 1: Copy your site id

   Add your site in VisitTrack; the install step's Google Tag Manager tab shows the loader with your id filled in (the version below adds the queue stub on top). Replace SITE_ID below.

2. 2

   Step 2: Create a Custom HTML tag

   In your GTM workspace: Tags → New → Tag Configuration → Custom HTML, and paste the loader.

   GTM → Custom HTML tagCopy

   <script>
     window.visitrack = window.visitrack || function () {
       (window.visitrack.q = window.visitrack.q || []).push(arguments);
     };
     (function () {
       var s = document.createElement("script");
       s.defer = true;
       s.src = "https://visitrack.app/tracker.js";
       s.setAttribute("data-site", "SITE_ID");
       document.head.appendChild(s);
     })();
   </script>

3. 3

   Step 3: Fire it on All Pages, once per page

   Under Triggering, choose All Pages. In Advanced Settings → Tag firing options, choose Once per page. Name the tag "VisitTrack" and save.

4. 4

   Step 4: Optional: require consent in standard mode

   If you run a consent banner with Consent Mode and keep VisitTrack's standard mode (which stores a first-party id), open Advanced Settings → Consent Settings and require analytics_storage. In cookieless mode nothing is stored on the device, so you may not need a consent requirement — that's your legal call.

5. 5

   Step 5: Preview, then submit and publish

   Use Preview to confirm the tag fires on the first page, then Submit → Publish. Nothing reaches your live site until the container version is published.

How to check VisitTrack is working on Google Tag Manager

1. In GTM Preview, the VisitTrack tag fires once on the first page and not again on client-side route changes.
2. Open the live site after publishing; VisitTrack's live view shows you within seconds.
3. DevTools → Network: tracker.js loads from visitrack.app, then a POST to /api/collect per page.

Does VisitTrack track Google Tag Manager page navigation?

The tracker patches the History API, so route changes in single-page apps are pageviews automatically. Firing this tag again on a History Change trigger would insert a second copy of the script and double-count — keep it on All Pages, once per page.

On classic multi-page sites, every page load fires All Pages and the tag runs once, as expected.

How to track custom events and goals in Google Tag Manager

To forward a dataLayer event — say your app pushes { event: "sign_up" } — create a trigger of type Custom Event with that event name, and a second Custom HTML tag that calls VisitTrack. Because the loader defines the queue stub, this works even if the event fires before the script has finished loading.

<script>
  window.visitrack("signup", { method: "email" });
</script>

Event names are the identifier in VisitTrack — pick one (signup) and keep it. An event named signup fills the Signups tab; any event can become a goal in Settings → Goals. Click goals don't need GTM at all: data-vt-goal="name" on the element works once the script is loaded.

Script options you might need on Google Tag Manager

All optional — add them to the same tag. Full reference: script configuration.

Google Tag Manager troubleshooting

Not on Google Tag Manager? See all 29 integration guides.