DataSag guides · Updated 27 October 2026
Install DataSag on Gatsby
Add DataSag to Gatsby through an onRenderBody head component in the root gatsby-ssr.js file. Create a project first, then replace the example public key with the key from your dashboard.
Where to put the tracking script
Use the Gatsby SSR onRenderBody API to add one deferred external script through setHeadComponents. Merge the addition into an existing hook rather than overwriting it, and keep the React import required by your file format. Build and publish the generated site; inspect its HTML because this hook concerns generated documents.
const React = require("react");
// Merge into your existing onRenderBody hook if one exists.
exports.onRenderBody = ({ setHeadComponents }) => {
setHeadComponents([
<script key="datasag" defer
src="https://www.datasag.com/tracker.js"
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
- Publish the change to the domain visitors actually use. Open a nested page as well as the homepage.
- In browser developer tools, find one tracker.js script with the correct data-datasag-key value.
- Filter Network requests for /api/track. Confirm that a pageview payload names the path you opened and receives a successful response.
- Open the same DataSag project and choose a date range containing your test. Confirm the page appears before measuring campaigns or conversions.
Avoid this Gatsby setup mistake
A browser onRouteUpdate hook, a plugin and gatsby-ssr can all add analytics behavior. Do not add a second pageview sender without testing the current tracker. gatsby develop is not a substitute for checking generated production documents.
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
Call the browser API from a React action handler after success. Gatsby build-time Node execution and SSR do not have the visitor window. Keep the global loader separate from individual page components.
<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 Gatsby
Check the rendered script, public project key, browser requests and first pageview before relying on your analytics.
- Fix DataSag analytics not working on Gatsby
Trace missing website visits through script placement, project keys, exclusions, consent, network delivery and report filters.
- Fix duplicate analytics pageviews on Gatsby
Separate legitimate engagement events from duplicate tracker installations and repeated pageview dispatches.
- Track custom events on Gatsby
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 Gatsby
Choose a non-blocking script placement and verify actual loading behavior instead of relying on a fixed speed claim.
Platform reference
Official Gatsby 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.