Documentation Loading events

Verify your first event

A successful Loader probe is not the same as a successful event. Verify the complete browser-to-Node path by triggering a known action and finding the resulting event in your Console.

Run a controlled test

  1. In Loader Configuration, enter the Node/Uplink host with no page path and run Verify Installation.
  2. Open the actual test page and use browser developer tools to confirm that its /lib/supreme.js?pid=<property-id> request completes with HTTP 200. A 400 or 404 means the Property id is missing, unknown, or inactive.
  3. Confirm that window.SupremeTracking.propertyId returns your Property id. A null means the page received the rejecting stub, which still defines window.supremeSend — a typeof check alone proves nothing.
  4. Trigger one deliberate event. A configured automatic page_view is enough for an ingestion check; use a test lead or purchase when you need to verify conversion mapping.
  5. Open the Console's Live Feed or Events view and look for the event name and current timestamp.

The green result in step 1 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, 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. Steps 2 through 5 provide that evidence.

What success proves

An event visible in Events proves that:

  • The page emitted an event.
  • The Node accepted and persisted the canonical event.
  • The browser-based Console can read it from that Node.

It does not prove that Meta, GA4, or another destination accepted the forwarded payload. Verify that separately in the destination's test or diagnostics view.

If no event appears

Work through the path in order.

1. Loader

  • Confirm the script URL uses the Node domain, not the Console or System domain, and carries ?pid=<property-id>.
  • Open https://<your-node-domain>/lib/supreme.js?pid=<property-id> directly and inspect the real response and status code. A 400 or 404 means the Property id is missing, unknown, or inactive.
  • Confirm window.SupremeTracking.propertyId on the page returns the expected Property id.
  • Check the rendered website source or Elements panel for the snippet.
  • Check the Network panel for certificate, CSP, consent, blocking, or 404 errors.

If needed, revisit Install the Loader.

2. GTM or event source

  • In GTM Preview, confirm the intended trigger fires exactly once.
  • Confirm the tag type is the approved Supreme Tracking Event Core.
  • Confirm the tag uses the Node's Ingest Token, never the Master Key.
  • Confirm the Loader runs before the tag calls window.supremeSend.
  • For leads and purchases, confirm the success signal occurs before the tag fires.

See Connect Google Tag Manager.

3. Transport and Node

  • In the browser Network panel, find the request initiated by supremeSend and inspect whether it reached the Node.
  • A 403 on the Node's ingest request means the page's domain is not registered in the Property's domains list — register the exact domain, including its www. or subdomain variant, in the Console.
  • A 422 with invalid_property or property_not_ready means the Property id is invalid or the Property is inactive — fix the Property in the Console.
  • An HTTP 2xx or accepted response only proves initial transport acceptance; the Node responds before canonical processing finishes. The event appearing in the Console is the persistence checkpoint.
  • Confirm the Node hostname and HTTPS certificate are valid.
  • Confirm the Node is reachable and its database connection is healthy.
  • Use Health and Logs in the Console for the connected Node.
  • Do not paste the Master Key, Ingest Token, event PII, or a full payload into a public support message.

4. Console view

  • Confirm you logged into the same Node that the Loader targets.
  • Clear event filters and select the expected Property.
  • Use a time range that includes the new test.
  • Refresh after triggering a fresh event instead of relying on an old browser action.

Event visible, destination missing

If the event appears in the Console, ingestion and local persistence worked. Next check whether the destination module is installed, active, compatible, and configured with valid platform credentials.

Continue with Integrations overview and compare the canonical fields described in The canonical event payload with the destination requirements.