Install
Install AnalyticFast on Framer with custom code
Framer can install the tracker through a site-wide custom-code entry. Use one initial load; AnalyticFast already observes navigation between routes.
Install on Framer
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 your site’s project settings and find Custom Code. Add a new script entry with a recognizable name such as AnalyticFast.
- Choose the head position and apply it across all pages. Paste the complete snippet below.
- For execution frequency, choose Once instead of Run on every page visit.
- Publish, open the public domain and navigate between two pages. Confirm that a second custom-code entry is not loading another tracker.
<script defer data-website-id="YOUR_SITE_ID" src="https://t.analyticfast.com/js/script.js"></script>Do not place a site tracker inside a visual embed that isolates it from the page. A route-specific entry can leave the rest of your site unmeasured. Check both your CMS detail pages and landing page after publishing. If a consent tool controls analytics scripts, use one installation path and connect its state changes to the tracker rather than adding another loader on every route.
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.
Should the Framer custom-code entry run on every page visit?
Use Once for the loader. AnalyticFast tracks SPA history navigation itself, so rerunning the loader on every route is unnecessary. Check real navigation after publishing.
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.