Install
Install AnalyticFast in Webflow site-wide custom code
Use Webflow’s site-wide Head code field so your published pages share the same tracker. Your Webflow plan must provide custom-code access.
Install on Webflow
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.
- Open the site’s settings, then Custom code → Head code.
- Paste the complete script below once. Include its opening and closing script tags; do not wrap it in html, head or body tags.
- Save changes and publish to the public domain registered in AnalyticFast. Saving the settings alone does not publish them.
- Open a published CMS page and a static page. Remove page-level embeds or GTM tags that already load AnalyticFast.
<script defer data-website-id="YOUR_SITE_ID" src="https://t.analyticfast.com/js/script.js"></script>A single page’s custom-code field covers only that page. The site-wide field avoids gaps as you add landing pages or CMS entries. Keep defer on the tracker. If you later move the snippet to a consent manager, remove this copy first. External checkout tracking still requires the provider’s webhook and metadata handoff; a Webflow button click is only a goal or outbound click.
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.
Connect your consent choice
If your site uses an analytics consent banner, use the pending-consent snippet and connect its Accept and Decline/withdraw actions. Pending mode sets no analytics cookies; it still records visits using the collector’s cookie-free identity mode. A consent manager that blocks the tag entirely prevents those requests. Choose the collection behavior appropriate for your site; pending mode is not a promise of legal compliance.
<script defer data-website-id="YOUR_SITE_ID" data-consent="pending" src="https://t.analyticfast.com/js/script.js"></script>// In your existing banner handlers:
window.analyticfast?.('consent', true); // Accept
window.analyticfast?.('consent', false); // Decline or withdrawRestore a stored choice on later visits. See the consent implementation guide for the full state and identity behavior.
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.
Why did saving Head code not change my live website?
Publish the site after saving the custom code. Verify the public domain, not just Designer or a preview. Also check whether your plan provides custom-code access and whether a page-level copy is duplicating the tracker.
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.