Seean
Sign inStart free for 15 daysTry free

Install with Google Tag Manager

Use a web container that is already installed on your site. You need permission to edit tags and publish the container. Copy your website token from Seean → Settings → Installation. A server-side or mobile container is not the browser installation described here.

Create the tag

Open your container’s workspace, choose Tags → New, then Tag Configuration → Custom HTML. Paste this tag, replacing YOUR_SITE_TOKEN:

<script defer src="https://app.seean.io/k.js"
  data-site="YOUR_SITE_TOKEN"
  data-api="https://app.seean.io"></script>

Name it Seean tracker. Custom HTML accepts third-party script tags. Do not replace this with a sandboxed custom-template injectScript call that loses the data-site and data-api attributes; Seean reads them from its executing script element. Google’s Custom HTML instructions.

Choose when it fires

For a site where your policy permits loading analytics at page load, use the All Pages pageview trigger. In Advanced Settings → Tag firing options, choose Once per page.

If your site requires analytics consent first, make the tag fire only after that consent is granted through your existing consent-management flow, including visitors who grant it after page load. Do not use Consent Initialization as permission to track, and do not assume Custom HTML automatically inherits Google Analytics’ consent behavior. Seean’s DNT/GPC/browser opt-out checks still apply. GTM consent settings.

Do not use a History Change trigger to reload this script on every SPA route. Once loaded, Seean already observes supported pathname navigation. Also remove any second Seean installation from your layout or another tag.

Preview, publish and verify

  1. Save the tag and open Preview. Connect Tag Assistant to your site and check whether the Seean tag fires at the intended time. If it does not, inspect its trigger and consent conditions.
  2. Follow installation verification: find the script and POST request, then match the pathname in Seean Events. A “tag fired” message alone is not proof that Seean stored an event.
  3. Navigate to another pathname and use Back/Forward. The tracker should remain installed once; automatic pageviews should reflect those path changes.
  4. Submit and publish the container version. Open the published site outside Preview and repeat the check. Workspace changes are not live until published.

Google’s preview workflow.

Missing data or duplicates

Check that the correct GTM container is installed on the published site. If the tag fires but no request appears, inspect consent, browser privacy settings, blockers, token attributes and CSP. A site security policy can block injected scripts even when Preview shows a fired tag.

For double counts, search both GTM and your application for k.js. Keep one load, no route-change reloads and no extra pageview call alongside automatic tracking. Queries and hash fragments alone are not distinct page paths.

Remove or rotate

Pause or remove the tag and publish the container to stop future collection from it. When rotating a Seean tracking token, update this tag and publish the new value. Existing analytics data is retained.

Something unclear? Contact support.