What Does the Meta Pixel Track on Substack?

The problem

"I've added my Facebook pixel ID to my Substack site, but after a few days of running, and testing each day, I've not been able to see any test details, conversion data, landing page data, or custom conversion information come through on my Meta Events Manager." — r/Substack, October 2026

"Substack shares very little information with its facebook pixel." — r/Substack, July 2026

If you buy Facebook or Instagram ads for your newsletter, you need to know whether they produce subscribers. Substack lets you add a pixel ID, but it doesn't show you what it sends, and Meta's tools don't always make it obvious. In our review of public Reddit, X, Hacker News and GitHub posts (October 2026), 8 forum threads touched on the Meta pixel or Conversions API with Substack, from a 2021 question on pixel conversion tracking to a 2024 thread on where the base code goes and the October 2026 "how do I confirm it" thread quoted above.

This page explains what Substack supports, which events fire, how to check them, and where the limits are.

What tracking does Substack support?

Substack's Analytics settings accept IDs for these tools, and nothing else:

Field	What it does	Notes
Google Analytics Measurement ID	Page views, sign-ups and paid subscriptions in GA4	ID starts with G-
Google Tag Manager ID	Loads your GTM container	Google tags only by default (see below)
Facebook (Meta) pixel ID	Reports ad-driven actions such as subscribing	Paste the numeric ID only
Twitter (X) pixel ID	Page views by default; optional sign-up and paid event IDs	Create the events in X Ads first
Parse.ly pixel ID	Content analytics
Facebook site verification	Domain verification for Meta	A meta tag, not tracking

Substack does "not currently support custom CSS or HTML in the post editor" (Substack help), so you can't paste Meta's base code or add your own fbq() calls. The ID field is the only way in.

Which Meta events does Substack send?

Substack's own advertising analytics post says you will see "a free signup, paid signup, or pageview" on the Facebook side. The October 2026 help article describes the pixel as reporting "when someone who clicked one of your Facebook or Instagram ads takes an action on your publication—for example, subscribing" (Substack help).

Neither page names the Meta event types. We read Substack's public page code in October 2026 and observed:

Reader action	Meta event (observed)	Parameters (observed)
Visits a page	Page view	Named in Substack's 2023 post
Free sign-up	CompleteRegistration	Event ID
Paid subscription	Purchase, plus Subscribe for subscriptions	value, currency, event ID

We also observed that Substack itself attaches a hashed email (the ud[em] advanced-matching field) to its pixel requests. Meta's advanced matching docs describe em as an email that is either lowercase or SHA-256 hashed. This is our reading of code on one day, not a documented Substack feature, and it can change.

How do I check that my pixel is working?

1. Use the ID, not the code. In Meta Events Manager, copy the pixel's numeric ID. In Substack, open Settings → Analytics, paste it into the Facebook pixel ID field and save.
2. Install Meta's browser checker. Meta's Pixel Helper is now called Meta Ads Data Advisor, a free extension for Chrome and Edge. Its badge shows "the number of Pixel events fired" on a page, and its panel lists each event with its parameters (Meta docs).
3. Load your publication. Open your Substack homepage and a post. You should see your pixel ID and a page-view event.
4. Test a free sign-up. Subscribe with a fresh email address you control. Look for CompleteRegistration in the extension.
5. Test a paid sign-up if you sell subscriptions. Use a card you own, then cancel and refund from Substack's Subscribers page, not Stripe (Substack help). Look for Purchase and Subscribe with a value.
6. Check Events Manager. The events should appear on the pixel's overview. Substack notes that most outside tools "take 24 to 48 hours to show meaningful numbers" (Substack help), so don't give up after an hour.

If nothing fires, re-check the ID, check that the pixel is active in Meta, and try again without an ad blocker.

Why don't my custom conversions or Tag Manager tags fire?

Two common causes:

• URL-based custom conversions. An advertiser in r/Substack said they could track ad conversions only "using the direct conversion information from substack", because Substack "has stopped sending website information to Facebook". They also "had to create a second Facebook pixel dedicated just to sub stack" so their website and Substack conversions didn't mix. That is one user's report, but it fits what we observed: use the standard events, and give Substack its own pixel.
• Meta tags inside Google Tag Manager. In Substack's page code (observed October 2026), Tag Manager is told to allow Google-built tags only, and custom HTML or non-Google pixels are blocked unless Substack has exempted the publication. Put the Meta pixel in the native field. GA4 through Tag Manager does work and sees sign-ups and paid subscriptions (Substack help).

What are the limits?

• No Conversions API of your own. You can't send server events for Substack sign-ups, because Substack doesn't tell your server when they happen. Meta deduplicates pixel and server events only when the event ID and name match (Meta docs). That only matters if you also capture sign-ups on a form you host.
• No identity for you. The pixel tells Meta that a sign-up happened. It doesn't tell you who signed up. For that you need your subscriber export.
• Only your publication's pages. Substack loads the tool "on your publication's pages" (Substack help). We expect sign-ups that happen elsewhere, for example inside the Substack app, not to reach your pixel. Treat ad-reported sign-ups as a lower bound.
• Value optimisation. One advertiser said Meta "won’t let me optimise for value because it's not connected to conversion API" (r/Substack). Results vary by account; test before you scale spend.

What not to do

• Don't try to inject pixel code through embeds or workarounds. Substack doesn't support custom HTML.
• Don't upload your subscriber list to Meta as a custom audience unless your privacy notice and your readers' consent cover it.
• Don't share one pixel between your website and Substack if you need clean Substack numbers.
• Don't trust a single day of Events Manager data.

Where newsletterapi fits

newsletterapi offers subscriber analytics from your export, which joins your Substack export with sign-up dates and sources so you can compare ad spend with real subscribers. It is independent of Substack. If your ads collect leads in a Meta form instead of sending people to Substack, read Facebook lead ads to Substack. For the rest of Substack's built-in numbers, see Substack analytics explained, and for events you can automate on, see Substack webhooks.