Install DataSag on PHP templates

Where to put the tracking script

Add the deferred external script once to the local PHP include that emits your public HTML head. Preserve the existing document structure and include that file through a known local path in the pages you intend to measure. The tracking snippet itself is HTML; it does not need a PHP analytics library.

<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 PHP templates setup mistake

An independent PHP endpoint may return JSON, redirect before rendering, or use another header include. Keep the tracker in rendered HTML and avoid inserting output before code that needs to send response headers. Do not derive an include path from visitor input.

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 an HTML goal attribute for clicks, or invoke the API from browser code after a confirmed response. A server-side PHP success branch cannot directly call the browser API unless it renders an appropriate page or response for browser code to handle.

<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 PHP templates

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

• Fix DataSag analytics not working on PHP templates

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

• Fix duplicate analytics pageviews on PHP templates

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

• Track custom events on PHP templates

  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 PHP templates

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

Platform reference

Official PHP templates 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.