Website pixels: install and check tracking tags
An ad platform can only measure sales and sign-ups from your ads when its pixel is on your website. Hermoso puts the pixel there through the site connection your brand already has, then reads the live page to check it is there. Installing, listing and removing pixels costs no credits.
The pixels
Meta Pixel, TikTok Pixel, Google tag (G-, AW- or GT- ids), LinkedIn Insight Tag, Reddit Pixel, Pinterest Tag, X Pixel and Snap Pixel.
- The pixel id is never made up. Leave
pixelIdout and Hermoso uses the brand's only pixel on its connected ad account. If there are several, it lists them and asks which. An id you give is checked against the brand's connected ad account, and refused if it is not one of the brand's. - The code is the platform's own. For Meta and Pinterest, Hermoso uses the code from your connected account or the platform's published base code. For the Google tag it uses Google's published snippet. For TikTok, LinkedIn, Reddit, X and Snap, pass
snippet: the base code copied from the platform's events manager. It must contain the pixel id.
Where it goes
| Your site | What Hermoso does |
|---|---|
| Google Tag Manager | Adds a Custom HTML tag with the pixel's code that fires on every page, in a draft. It reaches visitors when the container is published: pass publish: true, and for a container that is already live, its GTM-XXXXXXX id as confirmPublicId. Works for every pixel above. |
| Wix | Adds a Wix marketing tag: Meta Pixel, TikTok Pixel, Google Ads (AW-) or Google Analytics (G-). It is live on the published site straight away. Wix keeps one pixel of each kind per site, so replacing a different one needs its id typed back as replaceExisting. The Wix API key needs the Manage Marketing Tags permission. |
| Webflow | Webflow only lets its own apps add code, not a site token, so Hermoso gives you the code: paste it in Webflow under Site settings, Custom code, Head code, then publish the site. |
| WordPress | WordPress has no setting for this, so Hermoso gives you the code to add to the head of every page with a header and footer code plugin or your theme's header. |
| Shopify | Shopify no longer lets an app add another company's pixel to a store, so connect the pixel with the platform's own Shopify app from the Shopify App Store. |
If the brand has both Google Tag Manager and Wix connected, say which one with site.
Tools
| Tool | What it does |
|---|---|
install_tracking_tag | Installs a pixel. Without confirm: true nothing is written and the reply says exactly what would change. With it, the change is made and, once it is on the site, the live page is read: verify.found is true, false, or null when the page could not be read. |
list_tracking_tags | Reads the live page the way a browser loads it and lists every pixel and Tag Manager container on it, plus the tags Hermoso installed in Tag Manager and the site's Wix marketing tags. A page behind a password or a login (a Shopify store that is not public yet, for example) is reported as not checked, never as a page with no pixels. |
remove_tracking_tag | Removes a pixel Hermoso installed. Without confirm: true nothing changes. In Tag Manager the removal is a draft until the container is published. A pixel someone else added is never touched. |
In the app, open Connectors and choose Website pixels on the Google Tag Manager, Wix, Webflow or WordPress card. The API routes are POST /api/tracking-tags/install, GET /api/tracking-tags and POST /api/tracking-tags/remove.
Example
install_tracking_tag {"platform": "meta"}
→ "This adds a Custom HTML tag ... Nothing was changed."
install_tracking_tag {"platform": "meta", "confirm": true, "publish": true, "confirmPublicId": "GTM-ABC1234"}
→ "Added ... Verified: 1234567890 is on https://yourshop.com (found in the page as a browser loads it)."
A Tag Manager publish can take a few minutes to reach every visitor. If the first check says the pixel is not there yet, run list_tracking_tags again shortly.