Documentation Getting Started

Node installed, what's next?

Your Node is online, but it only becomes useful when it receives an event. The shortest path from a fresh installation to a working setup is to create your first Property, load the browser library, see an event in the Console, and then forward a conversion to a destination such as Meta or GA4.

The finish line has two parts:

  1. The event is visible in your Console.
  2. The same conversion reaches an enabled destination integration.

Before you start

Have these ready:

  • Your Node domain, such as tracking.example.com.
  • The Uplink domain and Master Key created during Node setup.
  • The Ingest Token saved during Node setup if GTM is part of your path.
  • The list of website domains that will send events, for the Property you create in Step 2.
  • Access to your website's <head>, a Google Tag Manager web container, or the supported WooCommerce or Shopify installation surface you use.

Your marketing events and customer data are processed by your Node and do not pass through the Supreme System. The Console reads operational data directly from your Node in your browser. When you enable a destination module, that module forwards its mapped fields from the Node to the destination you chose.

Learn more: What a Node is (control vs data plane).

Step 1 - Open the Console and log in

Open app.supremetracking.io/console. Enter your Uplink domain and Master Key, then initiate the connection.

The Console runs in your browser and talks directly to the Node. Keep the Master Key private: do not place it in page code, GTM variables, tickets, or screenshots.

Learn more: Log into the Console.

Step 2 - Create your first Property

A fresh Node has no Property, and a Node without an active Property does not accept events. In the Console, create the first Property and register in its domains list every domain that will send events — including the exact www. or subdomain variants your pages use. Note the Property's numeric id; the Loader URL in the next step needs it.

Events arriving from a domain that is not registered in the Property are refused by the Node.

Step 3 - Install the Loader tag

Add the Loader to the <head> of every page that should emit browser events. Replace the placeholders with your Node domain and the Property id from Step 2:

<script src="https://<your-node-domain>/lib/supreme.js?pid=<property-id>"></script>

The ?pid= parameter is required — without a valid, active Property id the Node serves a stub that discards every event. The Loader exposes window.supremeSend, adds first-party context, and delivers browser events to your Node. A WooCommerce plugin or a supported Shopify/GTM setup can load the same library for you, but the page must have the Loader before an event tag tries to call it.

Learn more: Install the Loader.

Step 4 - Verify the installation

Open the published page and confirm two things in browser developer tools: the request to /lib/supreme.js?pid=<property-id> completes with HTTP 200, and window.SupremeTracking.propertyId returns the Property id from Step 2 (null means the page received the rejecting stub).

The Console also offers Verify Installation under Loader Configuration. A green Installation verified successfully! result there means the browser completed the modal's network probe to the constructed https://<entered-host>/lib/supreme.js URL. Because the probe uses a no-cors HEAD request, does not inspect response status or body, and carries no ?pid=, it does not prove valid Loader JavaScript, a working Property id, snippet placement, or ingestion — the developer-tools check above is the evidence that counts.

Learn more: Verify your first event.

Step 5 - Connect GTM and configure triggers

In the Console's Integrations view, open DEPLOY NEW MODULE and select Google Tag Manager. Save the correct web container ID, then install the Supreme Tracking Event Core template in that GTM web container.

Create a tag for the event you want to test, supply the Node's Ingest Token, and attach a deliberate trigger. Use GTM Preview before publishing. The current template sends through window.supremeSend; it does not replace the Loader.

Learn more: Connect Google Tag Manager.

Step 6 - Confirm your first event

Trigger the page view, lead, purchase, or other event on the test page. Return to the Console and check the Live Feed or Events view for the event name and timestamp.

Seeing the event here confirms that it crossed ingestion and reached local observability on your Node. It does not yet prove that a destination platform accepted it.

Learn more: Verify your first event.

Step 7 - Connect your first integration

Open Integrations, choose DEPLOY NEW MODULE, and select a destination such as Meta or GA4. Install the module when required, enter that platform's credentials, enable it, and save.

Trigger a fresh test conversion. First confirm it in the Console, then use the destination platform's own test or diagnostics view to confirm arrival. A visible Console event and a platform receipt together complete the end-to-end check.

Learn more: Integrations overview.

What's next

Once the first path works, add only the events and destinations you can verify. Map server-side or webhook sources into the same canonical model, expand integrations one at a time, and review the plan attached to your License before relying on plan-specific features.

The common event shape is the contract that keeps those sources and destinations consistent. Learn more: The canonical event payload.