SupremeTracking

Documentation

Practical guides for taking a fresh Node from installation to reliable event forwarding.

Getting Started

Node installed, what's next?

Your seven-step path from a fresh Node to your first forwarded conversion.

Getting Started

Install the Loader

Add the first-party Loader with your Property id and verify the installation on the real page.

Getting Started

What a Node is (control vs data plane)

Understand where events run, where product access lives, and how the planes stay separate.

Getting Started

Log into the Console

Connect the browser-based Console to your Node and find the main operational views.

Loading events

Connect Google Tag Manager

Install the current GTM template, map an event, and publish the right trigger.

Loading events

The canonical event payload

See how browser and webhook inputs become one event shape before processing.

Loading events

Verify your first event

Confirm ingestion in the Console and troubleshoot an empty event feed.

Loading events

Install the Web Events skill in Claude or ChatGPT

Add the Supreme Events Skill to your own AI agent so it writes correct Supreme tracking.

Loading events

Install a Node guided by the Web Events skill

Let your AI agent walk you from zero to a working Node with a verified first event.

Loading events

Track a specific page from its HTML or URL

Hand your agent a page and get a paste-ready snippet for its conversions.

Integrations

Integrations overview

Learn how the catalog, Node modules, credentials, and forwarding fit together.

Integrations

Connect Reddit Ads

Connect a Property to the Reddit Pixel and Conversions API v3, then verify both delivery paths.

Integrations

Connect Meta Ads to your Node

Pull your ad account's spend into your own Node and read ROAS against the revenue the Node itself measured.

Integrations

Connect an MCP client to your Node

Point your AI agent at the Node's MCP endpoint with the MCP_KEY and let it answer questions about events, purchases, diagnostics and ads.

Concepts

The Node's maintenance cron

The Node closes finished sessions, reclaims stuck ones and reconsolidates counts on its own clock. Learn what a one-minute crontab changes — and why a Node with no crontab at all still maintains its sessions on its own.

Loading events

Capture Leads and use the Leads API

Capture Leads from the browser or from your own server, keep them up to date, and prove every capture landed on your Node.

Integrations

Export Leads to spreadsheets

Publish a Property's Leads as a CSV file on your Node, behind its own username and password, and let your Excel or Google Sheets spreadsheet refresh itself.

Integrations

Connect Hubla

Receive Hubla sales on your Node by webhook and tie each sale to the visit that brought it, with the checkout link decorated by the Loader.

Integrations

Connect Lastlink

Receive Lastlink sales on your Node, with one webhook per product pointing to the same address, and tie each sale to the visit that brought it.

Integrations

Sale without the visitor identifier

What the purchase_without_stuid diagnostic means, what a Hubla or Lastlink sale loses when it arrives without the visitor identifier, and how to find the cause.