Install

Use the AnalyticFast browser SDK from your project

The repository contains a small browser package at packages/analyticfast. Its manifest is currently private; this guide does not claim a public npm release. The plain script is the available installation path when you do not have a reviewed local package build.

Install on npm browser SDK

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.

1. For the source-package workflow, build the browser SDK in your AnalyticFast checkout with npm --prefix packages/analyticfast run build after installing its build dependencies.
2. In your website project, install that built local package using its actual absolute path, as illustrated below. Do not substitute an unrelated registry package with the same name.
3. Initialize once in a browser lifecycle hook. Supply both your Site ID and host; omitting host defaults to the website’s own origin and is only suitable for an intentional same-origin deployment.
4. Call goals from actual completion handlers and read optional attribution IDs immediately before checkout. Remove any existing plain-script installation.

npm install /absolute/path/to/AnalyticFast/packages/analyticfast

import { init, track, identify, attribution, consent } from 'analyticfast';

// In your root browser lifecycle hook:
init({ siteId: 'YOUR_SITE_ID', host: 'https://t.analyticfast.com', consent: 'pending' });

// In the corresponding existing handlers, not during initialization:
// consent(true); // Your banner's Accept action.
// consent(false); // Decline or withdrawal.
// track('signup_completed', { plan: 'starter' });
// identify({ user_id: customerProvidedId });
// const ids = attribution(); // Forward present IDs to your checkout server.

Place initialization in the browser

• React / Next.js: call init in a root component’s useEffect; mark an App Router component 'use client'. Render it once from the root layout.
• Vue: call init in the root component’s onMounted hook, not at module evaluation during SSR.
• SvelteKit: call init in onMount in the shared layout. Do not put it in a server load function.

The SDK uses the existing tracker queue and does not require manual pageviews for real SPA navigation. identify accepts customer-supplied identity; it should not scrape a page or manufacture personal data. attribution() can return an empty object: omit missing metadata instead of inventing IDs. This is the browser SDK, separate from scoped-token server APIs.

Verify the published website

1. Replace YOUR_SITE_ID with 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=true may be ignored.
2. In browser Network tools, check https://t.analyticfast.com/js/script.js and the request to /api/event. A downloaded script or a successful HTTP response alone does not prove that an event was accepted.
3. 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

• React useEffect reference
• Vue onMounted reference
• Svelte onMount reference

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.