Documentation Getting Started

Log into the Console

The SupremeTracking Console is the browser-based operator interface for your Node. It connects from your browser to the Node you specify, so event data does not need to pass through the Supreme System.

Sign in

Open app.supremetracking.io/console. If you do not have an active session, the app opens the login screen.

Enter:

  • Uplink domain: the Node hostname created during setup, for example tracking.example.com.
  • Master Key: the secure key created by that Node.

Select Initiate connection.

Do not paste the Master Key into your website, GTM, analytics tools, support messages, or screenshots. GTM event tags use the Ingest Token, not the Master Key.

Know the main views

  • Home gives you the operational overview, Loader controls, analytics summary, and Live Feed.
  • Health shows whether the connected Node and its services are responding.
  • Integrations is where you install, configure, enable, and inspect destination or source modules.
  • Properties organizes event ownership inside the Node.
  • Events shows realtime and historical event records read directly from the Node.
  • Logs helps diagnose Node and forwarding behavior.

The exact actions available can depend on the access granted by your License and Plan. The Node itself does not make that access decision.

Configure and verify the Loader

From Home, open Loader Configuration. The modal shows the Node-specific tracking script and the automatic browser-event controls.

Under Verify Installation:

  1. Enter the Node/Uplink host that serves the Loader, with no page path.
  2. Select Check Installation.
  3. Confirm the green Installation verified successfully! result.

The green 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. Confirm the snippet and its real network response on the rendered website separately. If the script is missing there, follow Install the Loader. If the script is present but the event feed stays empty, use Verify your first event.

Confirm the correct Node

After login, verify that the hostname, health information, and expected Properties belong to the Node you intended to manage. Then open Events and trigger a test action on the connected website.

The Console reading an event proves local Node observability. To prove destination delivery, also check the receiving platform after you configure an integration.

Learn more: Integrations overview.

If login fails

Check these without sharing the Master Key:

  • The Uplink domain is the Node hostname, not the website, Console, or System domain.
  • The Node domain resolves over HTTPS and is reachable from your browser.
  • The Master Key came from this Node's setup and was copied completely.
  • You are connecting to the intended Node rather than an older or staging installation.
  • A proxy, firewall, or certificate problem is not blocking the Node API.

Once the connection works, return to Node installed, what's next?.