Install

Install AnalyticFast on WordPress with the site plugin

Use the repository’s WordPress plugin to enqueue one deferred tracker. It has a settings page for the public Site ID and tracking origin; it does not need a payment API key.

Install on WordPress

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.

Use WordPress 6.3+ and PHP 7.4+. In your AnalyticFast installation panel choose WordPress and download the plugin ZIP.
In WordPress open Plugins → Add New Plugin → Upload Plugin. Upload analyticfast.zip, install and activate it. This is a direct upload, not a claim of a WordPress.org directory listing.
Open Settings → AnalyticFast. Enter YOUR_SITE_ID and the HTTPS tracking origin https://t.analyticfast.com, replacing the ID with your own.
Save, clear page/CDN caches and visit a public page while signed out. Remove any earlier theme or GTM copy.

Site ID: YOUR_SITE_ID
Analytics origin: https://t.analyticfast.com

Prefer the plugin over editing a parent theme that an update could replace. On multisite, settings are per WordPress site. The plugin does not automatically identify logged-in members. Its analyticfast_should_track filter can suppress server-side enqueueing; avoid caching one visitor’s consent-specific HTML for everyone. For a browser-only consent manager, disable the plugin enqueue and use the managed snippet once instead. See the plugin installation guide.

Screenshot placeholder: WordPress Settings → AnalyticFast with the public Site ID and HTTPS origin, after saving.

Verify the published website

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.
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.
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.

Will a theme update remove the installation?

The plugin enqueues the tracker independently of theme files. Keep the plugin activated and its settings saved. If you switch installation methods, remove the old copy before adding another.

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.