GTM & custom events

No gateway key needed: report conversions directly from the browser. The tracker watches Google Tag Manager's dataLayer and exposes its own conversion API for custom code.

DataLayer pushes (GTM)

The tracker observes window.dataLayer.push(...) and recognizes common purchase events: purchase, order_completed, lead, signup, subscribe and more. Add the standard fields:

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

event — the event name (purchase works for money).
value — the revenue amount, number.
currency — 3-letter code (USD, EUR …).
transaction_id — optional but recommended; enables dedupe.

Enhanced-ecommerce payloads are understood too — both ecommerce.purchase and flat GTM pushes are normalized before they're stored.

trackConversion() API

If you don't drive GTM triggers, call the global API anywhere after the tracker has loaded:

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

Automatic attribution

Both paths classify the source the same way the rest of Analytise does — UTM parameters first, then referrer and ad-click IDs, then "Direct" — so gateway payments and client conversions sit in the same conversion_events stream on the Conversions page.

Revenue stays at zero?

Client-reported revenue requires the event to actually fire after checkout. See Troubleshooting.

Troubleshooting