Integration catalog
Connect your sources and your destinations.
Supreme runs on your server and talks to the platforms you already use: it receives the sale from whoever sells, and sends the conversion to whoever advertises. Each integration is a module you install from the Console, in one click.
- 13
- available now
- 1
- in closed beta
- 3
- coming
States read from the System catalog on 2026-10-08. The Console shows each module's installed version and its compatibility with your Node.
Destinations: where the conversion goes
The event lands on your Node, is translated into Supreme's canonical format and leaves for the ad platform. The call is made by your server, with credentials stored on your Node.
Conversions API from your server and the pixel in the browser, carrying the same event_id on both sides so Meta never counts one sale twice. Multiple pixels per property.
Conversions fired in the browser, by conversion label on your AW- account. The module also reads campaign spend and performance for the Console. There is no server-side send in this integration.
Measurement Protocol from your server and gtag in the browser, sharing one session. Measurement ID, API Secret and DebugView configured per property.
Events API from the server and the pixel in the browser, deduplicated across both sides.
Conversions API v3 and the Reddit Pixel, deduplicated across browser and server. Granted on request while it is in closed beta.
Pixel and Conversions API for ads placed on ChatGPT. The module is written and registered in the catalog, but has no published release to install yet.
Pinterest Conversions API. Registered in the catalog and not built yet — we are not promising a date.
Sales sources: where the sale comes from
The payment platform notifies your Node over a webhook. You paste one URL and the secret Supreme generates for you — no API keys, no tag on the checkout. And when a checkout link leaves a page carrying the Loader, it goes out decorated with the visitor's identifier: the sale comes back attached to the visit that produced it.
Sales, refunds and subscription events. Checkout links leave your page decorated, and Initiate Checkout can be switched on per property.
Purchases, refunds and abandoned carts, with checkout-link decoration from your own page.
Purchases, refunds, subscriptions and abandoned checkouts, plus generated Pix and boleto charges. An abandoned checkout is recorded as a lead.
Sales, renewals, refunds, abandoned checkouts and Pix and boleto charges.
Sales, renewals, refunds, abandoned carts and Pix and boleto charges.
Purchases, refunds and abandoned carts from your Yampi store.
Purchase and refund from your WooCommerce store, over WooCommerce's own webhook with a shared secret.
Web events: how the event gets in
The normal path is the Loader on your page. These two exist for when the page is not yours to edit — a container somebody else administers, or a checkout hosted by the platform.
Supreme's own template in the Google Tag Manager gallery: whoever owns the container installs it and fires Supreme events without touching the site's code.
Custom Pixel on the Shopify storefront and checkout, served from our CDN. It captures the browsing and the checkout the Loader cannot reach on Shopify's domain.
CRM
The first CRM integration is registered in the catalog and has not been built yet. It is on this page so you know what is coming, not to be sold as ready.
Lead and deal events in Kommo. Registered in the catalog, with no published release.
Your platform is not on the list?
Any platform · no code
The Webhook Builder solves the case no catalog solves. If the platform can send a webhook, you build the integration yourself, from the Console, without waiting for us and without writing a line of code.
- 1 Paste a sample payload the platform sends.
- 2 Point at the value, the currency, the e-mail, the order identifier.
- 3 Pick the Supreme canonical event and switch it on.
The Builder previews the event before you activate it, and the Console keeps the received payload so you can check it field by field.
Frequently asked questions
Do I have to install an integration for every platform?
You install only what you use. Meta, Google Ads, GA4 and Google Tag Manager ship inside the Node package and update along with it. The others are catalog modules: you pick one in the Console, install it in a click, and each is then updated on its own cadence.
What if my sales platform is not on the list?
Use the Webhook Builder. Any platform that can send a webhook can be wired to Supreme with no code: paste a sample payload, map the fields onto the canonical event format and switch it on. It is the same path a native module takes once it has translated the payload.
Do I need an API key from the sales platform?
Not for the webhook integrations. In the platform's own dashboard you paste a URL on your own Node and the secret Supreme generates for you. Credentials are needed by the ad destinations, because there it is Supreme calling the platform's API.
Where do the integration credentials live?
On your Node, in the database you already administer. The call to Meta, Google or TikTok goes from your server straight to the platform: there is no server of ours in the middle of that path, which is why your event ceiling is your hosting, not an invoice.
Can I use the same integration on more than one site?
Yes. The Node organises tracking by Property, and an integration is connected per property — each site with its own pixel, its own ad account and its own webhook secret, on the same Node.
How do I know the conversion arrived?
From the Console. Every event shows the destinations it went to, the status of each delivery, the payload that left and the response the platform returned. That is the difference between "the pixel is installed" and "this sale reached Meta".
What do "closed beta" and "coming" mean on this page?
Closed beta is a published, installable module, granted on request while it matures. Coming is a module registered in the catalog with no published release: there is nothing to install yet. Both labels come from the System catalog, not from a roadmap promise.
Install the Node and connect what you already use.
Supreme goes onto the hosting you already pay for. The integrations come after, one at a time, as you need them.
Check the e-mail: it needs the format you@yourcompany.com.
Free, no credit cardThe e-mail is only to start the installation.