Install DataSag on Remix v2

Where to put the tracking script

For a Remix v2 application, add one deferred external script to the existing document head in app/root.tsx. Preserve Meta, Links, Outlet, ScrollRestoration and Scripts in their established locations. Keep the tracker outside nested route components. This guide targets Remix v2 conventions; inspect different framework versions before copying their root shape.

<script defer src="https://www.datasag.com/tracker.js" data-datasag-key="YOUR_PUBLIC_KEY"></script>

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 Remix v2 setup mistake

An action or loader runs on the server and cannot use the browser window. Root error handling can render a different document. Test direct entries, client navigation and your relevant error route without adding another script to every nested route.

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 client handler after a successful action result. A fetcher changing state or a Form submission beginning does not itself prove completion. Keep event definitions aligned with actual action data.

<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 Remix v2

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

• Fix DataSag analytics not working on Remix v2

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

• Fix duplicate analytics pageviews on Remix v2

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

• Track custom events on Remix v2

  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 Remix v2

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

Platform reference

Official Remix v2 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.