Install DataSag on Docusaurus

Where to put the tracking script

Add an object to the existing Docusaurus scripts array with src, defer and data-datasag-key attributes. Preserve the rest of your configuration. Build and serve the generated production site, then test a documentation route directly and through client navigation. The config runs in Node.js, so browser event calls do not belong there.

// Merge this entry into the existing scripts array.
export default {
  scripts: [{
    src: "https://www.datasag.com/tracker.js",
    defer: true,
    "data-datasag-key": "YOUR_PUBLIC_KEY"
  }]
};

The project tracking key is public and belongs in this snippet. Account credentials, provider API keys and database secrets do not. Keep your existing consent choices and only load analytics when your site's policy permits it.

Verify the published installation

1. Publish the change to the domain visitors actually use. Open a nested page as well as the homepage.
2. In browser developer tools, find one tracker.js script with the correct data-datasag-key value.
3. Filter Network requests for /api/track. Confirm that a pageview payload names the path you opened and receives a successful response.
4. Open the same DataSag project and choose a date range containing your test. Confirm the page appears before measuring campaigns or conversions.

Avoid this Docusaurus setup mistake

Docusaurus accepts string script entries, but an object is needed here to preserve the public tracking-key attribute and explicit non-blocking loading. Do not also insert the tracker through a client module, swizzled theme component or individual MDX page.

Keep pageviews separate from scroll, click and engagement events. A page can generate several tracking requests while still representing one visit to that path.

Events and conversions

Use a React browser handler in an interactive component or a goal attribute on rendered markup. For a completed action, wait for its actual success callback; a documentation link click only establishes intent.

<a href="/signup" data-datasag-goal="signup_click">Create account</a>

This attribute measures a click. To record a completed signup, call window.datasag.track in the application's confirmed success handler. Current plan details determine which event and campaign reports are available.

Setup and troubleshooting recipes

• Verify DataSag analytics on Docusaurus

  Check the rendered script, public project key, browser requests and first pageview before relying on your analytics.

• Fix DataSag analytics not working on Docusaurus

  Trace missing website visits through script placement, project keys, exclusions, consent, network delivery and report filters.

• Fix duplicate analytics pageviews on Docusaurus

  Separate legitimate engagement events from duplicate tracker installations and repeated pageview dispatches.

• Track custom events on Docusaurus

  Add click goals or completed-action events with DataSag's data attribute and browser JavaScript API.

• Track UTM campaigns on your website

  Create consistent tagged links and verify that campaign parameters reach your website and DataSag.

• Measure AI referral traffic on your website

  Check visits with observable AI referrers and understand the difference between traffic, citations and LLM visibility.

• Configure CSP for DataSag analytics on your website

  Diagnose blocked scripts, beacon requests and image fallbacks without disabling your site's Content Security Policy.

• Exclude your own analytics visits on your website

  Use DataSag's browser exclusion switch to keep your testing activity out of future tracked visits.

• Load analytics without blocking rendering on Docusaurus

  Choose a non-blocking script placement and verify actual loading behavior instead of relying on a fixed speed claim.

Platform reference

Official Docusaurus documentation explains the platform integration point. DataSag-specific behavior here follows the current tracker and project setup.

Need a different stack? Browse every installation guide.