Documentation

Setup guides and implementation notes for tracking, conversions, and revenue attribution.

Get Started

Analytise uses one lightweight tracker script. After install, pageviews, visitors, AI/LLM traffic, and standard traffic sources are tracked automatically.

  1. Add your website in the dashboard.
  2. Install the tracker snippet with your `data-site-id`.
  3. Verify data in dashboard cards (`Visitors`, `Pageviews`, `AI/LLM Traffic`, `Online`).

Revenue Attribution (GTM Required)

Revenue attribution in Analytise currently depends on conversion events pushed through Google Tag Manager dataLayer (or `window.analytise.trackConversion(...)` in custom code).

Important

If GTM/dataLayer conversion events are not sent, Revenue and Conversion Rate will stay at zero.

Required event fields

  • `event` (for example: `purchase`)
  • `value` (numeric revenue amount)
  • `currency` (3-letter code, e.g. `USD`)
  • `transaction_id` (recommended for dedupe)

GTM dataLayer example

window.dataLayer = window.dataLayer || [];
window.dataLayer.push({
  event: "purchase",
  transaction_id: "ORD-12345",
  value: 149.99,
  currency: "USD"
});

Custom Code Conversion Tracking

If you do not use GTM triggers directly, you can still report conversions with `window.analytise.trackConversion(...)`.

window.analytise.trackConversion({
  event: "purchase",
  transaction_id: "ORD-12345",
  value: 149.99,
  currency: "USD"
});

Analytise classifies attribution from available UTM/referrer/ad-click IDs and stores the conversion in `conversion_events`.

Troubleshooting

Revenue still shows 0

  • Confirm purchase event is pushed to dataLayer after checkout.
  • Confirm event payload includes `value` and valid `currency`.
  • Check `transaction_id` uniqueness to avoid dedupe conflicts.
  • Verify tracker script is loaded only once per page.

Duplicate conversions

Ensure your purchase event is fired once. Analytise dedupes by `(website_id, transaction_id)` when `transaction_id` exists.