Install

Install AnalyticFast in Ghost Code Injection

Ghost’s Site Header injection places the tracker on the site without editing a theme. Use the site-wide setting so posts and index pages share the same installation.

Install on Ghost

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. Open Ghost Admin → Settings → Code Injection; some admin versions group it under Advanced.
  2. Paste the full deferred snippet below into Site Header and save.
  3. Open your public homepage and a published post outside Ghost Admin.
  4. Remove an older theme copy, GTM installation or per-post snippet that loads the same tracker.
<script defer data-website-id="YOUR_SITE_ID" src="https://t.analyticfast.com/js/script.js"></script>

The injection available in a post’s editor sidebar applies only to that post. Installing there will not cover the rest of a publication. The tracker does not automatically identify Ghost members or read their email from page content. Connect the payment provider used by your membership flow and pass explicit checkout context for revenue attribution. A member visiting an article is not evidence of a new subscription payment.

Screenshot placeholder: Ghost Code Injection panel with the script in Site Header rather than a per-post field.

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.

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 withdraw

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

Does the tracker automatically identify paid Ghost members?

No. Page tracking does not identify a member or record their subscription payment. Use customer-supplied identity deliberately and connect supported provider webhooks with checkout attribution metadata.

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.