Documentation Loading events

Install a Node guided by the Web Events skill

If you have never used Supreme Tracking, the Web Events skill can act as your installation guide. Your AI agent explains each step in plain language, tells you exactly what to prepare, diagnoses errors by their exact messages, and verifies each milestone before moving on. The finish line is a Node — your own tracking engine, on your own hosting — showing its first event in the Console.

The division of labor is fixed: the agent guides, you click. Creating the subdomain and database happens in your hosting panel, and the installation itself happens in the Console wizard, which verifies your account with a code sent by email — only you can complete it. The agent never needs your Master Key, and nothing it does runs on Supreme's infrastructure.

For what a Node is and why it runs on your infrastructure, read What a Node is (control vs data plane).

Before you start

The agent will walk you through this list, but you save time by preparing it up front:

  • Web hosting that runs PHP 8.1 or newer, with the zip and curl extensions and write permission. Ordinary shared hosting is enough.
  • A MySQL database you can create in your hosting panel, with its host, name, user, and password at hand.
  • An empty, dedicated subdomain served over HTTPS, such as tracking.your-domain.com — never the root folder of a live website.
  • A way to upload one file to that subdomain: the hosting file manager or FTP access.
  • Access to the email inbox you will register with.

Start the guided install

Open your agent and paste:

I have never used Supreme Tracking. Using the supreme-web-events skill, guide me through installing my own Node from zero, one step at a time, and verify each step before we move on. My hosting provider is <provider> and my site is <your-domain.com>.

The agent takes it from there. Expect it to cover, in order:

  1. The prerequisites checklist above, adapted to your hosting panel.
  2. The Console wizard at app.supremetracking.io/console — Deploy new node: email verification, profile, Node domain, downloading and uploading the one-file installer, the environment handshake, the automatic installation, and the database step.
  3. Saving your keys. The final wizard screen shows the Master Key (your Console login for this Node — store it in a password manager, never in page code or chat messages) and the Ingest Token (used later for GTM or WooCommerce).
  4. The first Property: creating it in the Console and registering every domain that will send events. A fresh Node has no Property, and without one it accepts nothing.
  5. The Loader tag with your Property id, and the end-to-end check: a test event visible in the Console's event feed.

Only that last observation — an event with your test's name and timestamp in the Console — counts as done. The agent knows this and should not declare success earlier.

If a step fails

Give the agent the exact error text you see; the skill carries a triage table for the wizard's error messages and for post-install failures. Two habits make the diagnosis fast: paste error messages verbatim instead of describing them, and tell the agent what you observe in the browser's developer tools when it asks.

What's next

With the first event visible, continue exactly as any Node operator would: