Install
Install AnalyticFast with Google Tag Manager
The site-specific GTM template loads a public helper that attaches the Site ID to the tracker. The template needs no API key and is imported locally into your Web container.
Install on Google Tag Manager
Start by adding the website in AnalyticFast and selecting its domain, timezone and currency. These examples use https://t.analyticfast.com; the origin and Site ID shown in your site’s Settings take precedence.
- In the AnalyticFast install panel choose Google Tag Manager and download the site-specific
analyticfast.tpl. - In a GTM Web container open Templates → Tag Templates → New → menu → Import. Select the downloaded template.
- Review its
inject_scriptpermission: it should allow the exact site-specific loader URL, not every origin. - Create one tag using the template, fire on All Pages with once-per-page firing, and configure consent to match your site’s policy. Do not add a History Change pageview tag.
- Use GTM Preview to inspect firing, publish the container, and verify ingestion from the public website.
// Expected public loader URL in a hosted site-specific template:
https://t.analyticfast.com/api/onboarding/loader.js?site_id=YOUR_SITE_ID
// The loader adds:
<script defer data-website-id="YOUR_SITE_ID" src="https://t.analyticfast.com/js/script.js"></script>This is an importable local template, not a claim of approval in Google’s Community Template Gallery. The template uses injectScript; the loader adds data-website-id because the sandbox API does not accept arbitrary script attributes. A tag reporting success means its script loaded, not that the collector accepted a pageview. Remove any direct script, plugin or SDK copy before publishing this method. The current generated loader does not add a pending-consent attribute; use the chosen GTM consent controls or a separately managed snippet when that state is required.
Verify the published website
- Replace
YOUR_SITE_IDwith the ID for this website, then open its public domain in a normal browser. A builder preview, localhost, webdriver or a visit with?ml_ignore=truemay be ignored. - In browser Network tools, check
https://t.analyticfast.com/js/script.jsand the request to/api/event. A downloaded script or a successful HTTP response alone does not prove that an event was accepted. - Use Verify installation in AnalyticFast and check the last received event. If none arrives, check the Site ID, allowed hostname, consent configuration, duplicate installations and any blocker. Domain ownership verification is a separate step.
If your site has a Content Security Policy, allow https://t.analyticfast.com in both script-src and connect-src. Do not put tokens, customer email addresses or private keys in the snippet, URLs or goal properties.
Consent setup
Use the consent integration described above for this method. The consent guide explains pending, granted and declined states; a tag that never loads cannot record visits. Test the actual behavior of your chosen consent manager.
Official platform references
Instructions reviewed against the repository and official platform documentation on October 31, 2026. Screenshots are reserved placeholders; no live platform installation is claimed here.
Add your website to get its Site ID and installation checklist. Once visits arrive, connect your payment provider.
Questions, answered.
Does a successful GTM tag prove that events were accepted?
No. It shows that the loader completed. Confirm the tracker request, the Site ID and allowed hostname, then use AnalyticFast’s Verify installation and last-event status.
Does installing the script also record purchase revenue?
No. It records visits and goals. Connect a supported payment webhook and pass visitor/session IDs into checkout metadata to connect verified payments with traffic. A Buy click or thank-you pageview is not payment confirmation.
Why does the script load but no visit appears?
Check the real Site ID, accepted hostname, published code, consent settings and blockers. Localhost, automation and ignored visits may be excluded. Use the last received event in AnalyticFast as evidence; the script download alone is insufficient.