Documentation Getting Started

Install the Loader

The Supreme Loader is served by your own Node. It creates the browser-side window.supremeSend bridge, gathers first-party page context, and delivers events to the Node's ingestion path.

Copy the snippet

Use the exact Node domain that was deployed for tracking:

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

Do not use the Console domain or the Supreme System domain in this URL. The script belongs to your Node.

Place it in the page head

Add the snippet inside <head> on every page that should send events. Load it before GTM event tags, WooCommerce listeners, Shopify bridges, or custom code that calls window.supremeSend.

For a direct website installation:

  1. Add the snippet to the shared site head or layout.
  2. Publish the website change.
  3. Open a public page in a private browser window.
  4. In developer tools, confirm that the request to /lib/supreme.js returns JavaScript successfully.
  5. In the browser console, confirm that typeof window.supremeSend returns "function".

Other installation surfaces

  • Google Tag Manager: if GTM is your only script-injection surface, use a Custom HTML tag for the Loader and fire it on an Initialization trigger. Event tags must run after it. The official event template still depends on window.supremeSend.
  • WooCommerce: the Supreme WooCommerce plugin can enqueue its configured Loader URL before its event listener. Confirm the Node URL and Ingest Token in the plugin settings.
  • Shopify: install the Loader in the storefront's top-frame theme surface when your selected Shopify event transport requires the browser bridge. A sandboxed Custom Pixel cannot assume direct access to the top-frame window.supremeSend.

Choose one intentional Loader installation per page. Multiple copies add noise and make ordering problems harder to diagnose.

Verify from the Console

Log into the Console and open Loader Configuration. Under Verify Installation:

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

The green result only 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 rendered website and its real script response separately, then send an event and verify your first event to prove ingestion.

If verification fails

Check these in order:

  • The Node hostname is correct and uses HTTPS.
  • https://<your-node-domain>/lib/supreme.js opens without a 404 or certificate error.
  • The snippet is present in the rendered page, not only in an unpublished theme or GTM workspace.
  • A consent rule, content-security policy, ad blocker, or tag sequencing rule is not preventing the script from loading.
  • The value entered in Verify Installation is the Node host, not a website page URL or a URL with a path.

Once the Loader is present, continue with Connect Google Tag Manager or another supported event source.