Trackers on pxta.com

Google Tag Manager Sends Almost Nothing Itself, but It Decides What Everything Else Sends

Sun, 25 Oct 2026 00:00:00 +0000

Google Tag Manager is a loader. The site puts one snippet on every page, the snippet fetches a container from www.googletagmanager.com/gtm.js?id=GTM-..., and the container loads every other tag the marketing team has set up in Tag Manager’s web interface. The request PXTA sees from Tag Manager itself carries little more than the container ID.

So why list it at all? Because when a report shows a Meta Pixel or a TikTok tag firing at the wrong moment, the fix very often lives inside a Tag Manager container.

What Google Analytics 4 Sends From a Website, and Where Personal Data Slips In

Sun, 25 Oct 2026 00:00:00 +0000

Google Analytics 4 sends its data to an address ending in /g/collect, on google-analytics.com, analytics.google.com or a regional variant of them. One request can hold several events, one per line of the request body, with page details in the query string.

Google’s own rules say not to send personally identifiable information to Analytics. That’s a rule for the site owner, though, and the tag sends whatever the page gives it. PXTA checks what actually goes out.

What the Google Ads Conversion Tag Sends, Including Enhanced Conversions

Sun, 25 Oct 2026 00:00:00 +0000

The Google Ads conversion tag tells Google that an ad click turned into a sale, a sign-up or a lead. It’s separate from Google Analytics, even when both are loaded by the same gtag.js script, and its requests go to different places: googleadservices.com/pagead/conversion/, googleads.g.doubleclick.net/pagead/viewthroughconversion/, and a few paths on www.google.com such as /pagead/1p-conversion/ and /ccm/collect.

PXTA knows all of those as one tracker, so a report lists “Google Ads conversion tag” once, whichever endpoint the site’s setup happens to use.

What the LinkedIn Insight Tag Sends, and Why Its Page Addresses Matter Most

Sun, 25 Oct 2026 00:00:00 +0000

The LinkedIn Insight Tag is a B2B favourite. It lets a company see which job titles and industries visit its site, retarget them on LinkedIn, and count conversions from LinkedIn ads. Requests go to px.ads.linkedin.com, mostly to /collect and /wa/.

Compared with the Meta and TikTok pixels it sends little. A partner ID, the page address, a timestamp. That’s exactly why the page address deserves attention: it’s nearly everything the tag says about the visit.

What the Meta Pixel Sends From a Website, Field by Field

Sun, 25 Oct 2026 00:00:00 +0000

The Meta Pixel is the most common ad tracker on small business websites. A shop installs it to see which Facebook and Instagram ads lead to sales, and to build audiences of people who visited. Each time it fires, the browser makes a request to facebook.com/tr, usually as a tiny image.

That request is short and easy to read once it’s decoded. PXTA’s catalog entry for the pixel knows what each field means, and the report shows them in a table under every finding.

What the Microsoft Advertising UET Tag Sends, Page Titles Included

Sun, 25 Oct 2026 00:00:00 +0000

Microsoft’s Universal Event Tracking tag, UET for short, is the conversion and remarketing tag for Microsoft Advertising, the ad network behind Bing search ads. It loads bat.js from bat.bing.com and sends its events to bat.bing.com/action/.

It gets less attention than the Meta Pixel, and it often sends more than people expect: its page load events usually carry the page address and the page title.

What the Pinterest Tag Sends, With Enhanced Match Hidden in a JSON Field

Sun, 25 Oct 2026 00:00:00 +0000

The Pinterest Tag sends its events to ct.pinterest.com/v3/ and /user/. Shops use it to count checkouts from Pinterest ads and to build audiences from site visitors, so it tends to sit on product, cart and confirmation pages.

Its requests pack data in an awkward way. Some fields are JSON objects squeezed into a single URL parameter: the page details in ad, customer details in pd. Read raw, they’re a wall of percent signs. PXTA unpacks the JSON and shows each part as its own row.

What the Snap Pixel Sends From a Website, Hashed Email Field Included

Sun, 25 Oct 2026 00:00:00 +0000

Snapchat’s pixel loads scevent.min.js from sc-static.net and posts its events to tr.snapchat.com, mostly /p. It’s common on shops that advertise to younger buyers, and like the other ad pixels it counts conversions and feeds audiences.

The request is a short form post. Four or five fields cover the event, the page, and, when it’s set up, the visitor’s hashed email.

What the TikTok Pixel Sends From a Website, Decoded From Its JSON Events

Sun, 25 Oct 2026 00:00:00 +0000

The TikTok Pixel doesn’t send a short query string like the older pixels. It posts a JSON document to analytics.tiktok.com/api/v2/pixel, with the event, the page and the visitor nested inside it. Reading one by hand means picking through braces. PXTA flattens the JSON into dotted field names, so context.page.url reads as one row in the report.

TikTok ads sell well for shops and service businesses alike, so the pixel turns up on sites that never had a social ad tag before, often pasted in by whoever ran the campaign.

What the X Pixel, Formerly the Twitter Pixel, Sends From Page Addresses to Search Terms

Sun, 25 Oct 2026 00:00:00 +0000

X’s website tag, still loaded from static.ads-twitter.com as uwt.js, sends its events to analytics.twitter.com/i/adsct and t.co/i/adsct. Many sites have one left over from a Twitter campaign years ago, and it keeps firing on every page.

Its request is a plain query string. The interesting field has a long name: tw_document_href, the address of the page.