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 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.
  • 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 - Install the Loader tag

Add the Loader to the <head> of every page that should emit browser events. Replace the placeholder with your Node domain:

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

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 2 - 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 3 - Verify the installation

From the Console, open Loader Configuration. In Verify Installation, enter the Node/Uplink host that serves the Loader, with no page path, and select Check Installation.

A green Installation verified successfully! result 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 and does not inspect response status or body, it does not prove valid Loader JavaScript, snippet placement, or ingestion. Open the website separately and confirm its supreme.js response in browser developer tools.

Learn more: Verify your first event.

Step 4 - 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 5 - 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 6 - 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.