Platforms

Pixel Tracking supports 13 platforms. Each one has a row on the Dashboard and its own platform card, opened with Open platform card. The card has the same panels for every platform: Connection, Server side (where the platform has one), Consent and Events on this platform.

The ID field checks the format when you save. A row shows Active when the platform is on and the ID is valid, Not set up when it is on but the ID is missing or wrong, and Off otherwise. Saved IDs are shown partly masked.

Overview

The Dashboard groups the platforms in three blocks: Tag management, Analytics and Ad platforms.

Platform	Field	Format	Server side
Google Tag Manager	Container ID	GTM-XXXXXXX or GT-XXXXXXX	No
GA4	Measurement ID	G-XXXXXXXXXX	Measurement Protocol (Pro)
Umami	Website ID, Umami address	a UUID, and your Umami URL	No
Microsoft Clarity	Project ID	8 to 15 letters and digits	No
Google Ads	Conversion ID, Purchase label	AW-123456789	Enhanced conversions
Meta	Pixel ID	digits only	Conversions API (free)
TikTok	Pixel ID	letters and digits, such as CXXXXXXXXXXXXXXXXXXX	Events API (Pro)
Pinterest	Tag ID	13 digits	Conversions API (Pro)
Snapchat	Pixel ID	a UUID	Conversions API (Pro)
Reddit	Pixel ID	starts with t2_ or a2_	Conversions API (Pro)
Microsoft Ads	UET tag ID	5 to 9 digits	No
LinkedIn	Partner ID, Purchase conversion ID	digits	No
OpenAI Ads	Pixel ID	letters, digits, _ and -	Conversions API (free)

Paste the ID only, never the whole JavaScript snippet.

Google Tag Manager

• Container ID: either a Tag Manager container (GTM-...), loaded with gtm.js, or a Google tag (GT-...), loaded with gtag.js. The field picks the right loader from the prefix.
• Tag Manager loads the container and pushes every event to the data layer as brl_trk_<event> (for example brl_trk_purchase), with an ecommerce object and a brl_trk_event_id.
• Default consent category: Marketing. Change it only after checking which tags the container holds.

Caution

Use Tag Manager or the native integration for a given event, not both. If the container also fires a Meta, TikTok, GA4 or Google Ads tag that is switched on here, the event is sent twice. The Dashboard shows a warning when Tag Manager and native tags are both on.

GA4

• Measurement ID: the measurement ID of your GA4 web stream, in the G-... format. You find it in GA4 Admin, on the web stream. A GT-... Google tag goes in the Tag Manager field instead.
• Sends ecommerce events in the GA4 schema through the Google tag: page_view, view_item, add_to_cart, begin_checkout, purchase.
• Default consent category: Analytics.
• With Pro: Measurement Protocol, an API secret and Purchase transport (Browser gtag or Server, Measurement Protocol). GA4 cannot deduplicate, so the purchase takes one road only. See Server events.

Umami

• Website ID: the UUID of the website in your Umami.
• Umami address: where your Umami runs, for example https://stats.example.com. The script is loaded from there.
• Umami sets no cookies and keeps no IP address, so it loads without waiting for consent. To put it behind the banner as well, turn on Wait for consent anyway in the Privacy panel of its card.
• Umami counts the page view itself. The plugin adds view-item, add-to-cart, checkout and purchase, the purchase with its revenue and currency so it shows in Umami’s revenue report.
• Exclude administrators applies to Umami too.

Microsoft Clarity

• Project ID: 8 to 15 letters and digits.
• Default consent category: Analytics.
• Each event is sent to Clarity as a Clarity event under its internal name, such as purchase.
• Clarity gets its own consent call when the visitor’s choice changes, separate from Google Consent Mode.

Google Ads

• Conversion ID: the AW-... ID shown on your purchase conversion action in Google Ads.
• Purchase label: the label of that conversion action. The conversion ID alone fires nothing; the label names the exact action.
• Sends the purchase conversion.
• Enhanced conversions: when on, hashed customer data goes with the conversion. The email and phone are hashed on the server, so the browser never sees them in plain text.
• Default consent category: Marketing.

Meta

• Pixel ID: digits only, as shown in Meta Events Manager. The Conversions API uses the same ID to pair browser and server events.
• Conversions API: turn it on and paste the Access token generated for this Pixel ID. The token stays on the server and never appears in the page or the log.
• Test event code: set it only while you watch the Test events tab in Events Manager. Clear it before going live.
• Graph version (Advanced panel): the Meta API version. Keep the one the plugin ships with.
• Default consent category: Marketing.

TikTok

• Pixel ID: the code of the TikTok web source, copied from TikTok Events Manager.
• Sends PageView, the WooCommerce funnel and Purchase.
• With Pro: Events API with an Access token generated in TikTok Events Manager for the same Pixel ID, and a Test event code.

Pinterest

• Tag ID: 13 digits.
• Event names sent: pagevisit, addtocart, checkout for the purchase, plus search, signup and lead.
• With Pro: Conversions API, which also needs the Access token and the ad account ID. Pinterest takes server conversions on the ad account, not on the tag. You read the ad account in the Pinterest business hub.

Snapchat

• Pixel ID: a UUID, such as 00000000-0000-0000-0000-000000000000.
• Event names sent: PAGE_VIEW, VIEW_CONTENT, ADD_CART, START_CHECKOUT, PURCHASE, SEARCH, SIGN_UP.
• With Pro: Conversions API with an Access token.

Reddit

• Pixel ID: starts with t2_ or a2_.
• Event names sent: PageVisit, ViewContent, AddToCart, Purchase, Search, SignUp, Lead.
• With Pro: Conversions API with an Access token.

Microsoft Ads

• UET tag ID: 5 to 9 digits.
• Sends pageLoad, add_to_cart, begin_checkout, purchase with revenue and currency, and product IDs where there are any.
• Microsoft accepts offline conversions only through an OAuth API, so there is no server side for it.

LinkedIn

• Partner ID: the Insight tag partner ID.
• Purchase conversion ID: the number LinkedIn gives the purchase conversion, separate from the partner ID. Read it in LinkedIn Campaign Manager, on the action tied to your purchase. Without it, the tag loads but no conversion is recorded.

OpenAI Ads

• Pixel ID: your OpenAI Ads pixel ID.
• Event names sent: page_viewed, contents_viewed, items_added, checkout_started, order_created, registration_completed, lead_created.
• On the card, under Events on this platform, switch each event on or off: Contents viewed, Items added, Checkout started, Order created, Subscriptions and trials.
• Conversions API with an API key. Two switches go with it:
  • Validate only: OpenAI checks the payload and stores nothing. Turn it off before going live.
  • Send the purchase on order status: the order leaves from the server when it reaches a paid status, and the browser skips it. On by default.
• Advanced panel: Advanced matching (a hashed email, a hashed pseudonymous ID, country, city and postcode), Debug (logs each event to the browser console) and Content ID.
• OpenAI follows its own rules: money in minor units, a closed list of event names, and no phone or name fields.

Consent category per platform

Every platform needs a consent category before its tag loads and before a server event is sent. The defaults are Analytics for GA4, Clarity and Umami, and Marketing for everything else. You change it on the platform card, and the Consent tab lists them all. See Consent.