Documentation Loading events

Connect Google Tag Manager

Use the official Supreme Tracking Event Core custom tag template in a Google Tag Manager web container to map GTM triggers into Supreme events.

The current template does one job: it builds an event payload and calls the existing window.supremeSend function. The Loader must be installed first.

Before you start

You need:

  • Access to the correct GTM Web container.
  • Its container ID, such as GTM-XXXXXXX.
  • The Ingest Token produced during Node setup.
  • The Loader running on the pages where the tag will fire.

Never put the Node's Master Key in GTM. The template does not ask for it.

Register the GTM integration

In the Console:

  1. Open Integrations.
  2. Select DEPLOY NEW MODULE.
  3. Choose Google Tag Manager.
  4. If Install Module is offered, install it and then open its configuration.
  5. Enter the correct GTM- container ID.
  6. Enable the integration and save.

This keeps the Node and Console configuration associated with the intended container.

Import the current template

Obtain the current approved template.tpl for Supreme Tracking Event Core from your SupremeTracking delivery channel. Confirm that name when you open the file in GTM; do not substitute an older template with different fields or browser-pixel behavior.

In GTM:

  1. Open Templates.
  2. Under Tag Templates, select New.
  3. Open the template editor menu and choose Import.
  4. Select the approved template.tpl.
  5. Review and save the template.

After saving, Supreme Tracking Event Core appears as a tag type in that web container.

Create an event tag

Create a new tag with Supreme Tracking Event Core, then configure:

  • Ingest Token: the token created by your Node.
  • Select Event: a canonical event such as page_view, lead, add_to_cart, or purchase. Choose the custom option only when you intentionally need another event name.
  • Event ID: optional. Leave it blank for automatic generation unless another tag must supply the same ID for deduplication.
  • User Data: map only variables you are allowed to collect and send.
  • Custom Parameters: map event-specific values.
  • Currency, Value, and Items: populate these for applicable commerce events.

You do not configure a Node URL in this template. It sends through the Loader already running on the page.

The event becomes canonical inside the Node. See The canonical event payload.

Attach deliberate triggers

Use one tag configuration for each event/trigger contract you can test:

  • Fire a lead tag only after a confirmed form success, not on the initial form view.
  • Fire a purchase tag only on a confirmed purchase signal, with a stable transaction value and currency.
  • Use Custom Event triggers when your site pushes a trustworthy data-layer event.
  • Avoid publishing broad click triggers until Preview shows that they fire only on the intended action.

The Loader can emit configured automatic browser events. Check Loader Configuration before adding an overlapping GTM trigger so that you understand which source owns the event.

Preview, verify, and publish

  1. Open GTM Preview and connect the test site.
  2. Confirm the Loader request succeeds before the event tag runs.
  3. Confirm the intended trigger fires exactly once.
  4. If the tag reports that supremeSend is unavailable, fix Loader presence or tag ordering.
  5. Verify the event in the Console.
  6. Publish the GTM container only after the previewed event is correct.

The template does not fire fbq or gtag directly and does not collect browser identity cookies or GA identifiers itself. Destination delivery belongs to the Node's self-contained modules. Continue with Integrations overview.