How do I set up the Meta pixel to track newsletter signups?
Short answer
Put the pixel on your subscribe page, then in Events Manager create a custom conversion: open the event setup tool, load the page, and click the subscribe button so Meta records that click as the conversion. Expect 3 to 24 hours before it registers, with no notice. Optimize campaigns for that event, not page views.
"Pixel is a big deal. It's a pain in the butt, but it just is what it is. It sucks, but we've got to do it because it works."
In the publisher cohorts I've worked with, getting the pixel on the subscribe page has been the main blocker. Nothing else works without it, so do it first.
What does the pixel actually do?
It's a Facebook thing that lets you track when somebody does something on a website. In this case, hitting the subscribe button. You put a square around the subscribe button and tell Meta: this is what I want people to do. Then Meta can find more people like the ones who did it.
I treat the pixel as tracking, not targeting. I don't track much else on the site, because the only thing I care about is subscribers. Two years in, it still confuses me sometimes.
How do I set up the subscribe conversion?
- Make sure the pixel is installed on the subscribe page. The event setup tool needs it already live on the target page.
- In Ads Manager, open Events Manager.
- Create a custom conversion and choose to set up an event.
- When Meta loads your subscribe page, hover until the subscribe button is outlined, and click it. Meta records that click as your conversion.
- Repeat for every separate site. Each site needs its own setup.
- Wait. Don't redo it.
Why does it look like setup failed?
Custom conversions can take 3 to 24 hours to register, and Meta tells you nothing in the meantime. That silent delay is the most common reason people think they broke it and start over. Wait a day.
If you use a page builder, target the specific landing page. Don't assume the pixel automatically propagates to new pages.
Can I track free and paid signups separately?
Yes. Multiple pixels are allowed, but if you have full access to one, one is fine. Define different events on different pages: "subscribe" for free signups on the ad landing page, and "sign up" for paid or organic pages. The event is technically the same; you define it on one page versus another.
On client engagements, my team usually creates a fresh, clean pixel. When a news org has no pixel at all, we make one and email them the code to paste into their CMS.
Is Conversion API worth setting up?
For properties you'll run long term, yes. It runs through Tag Manager and needs access to the site. For short, quarterly client engagements, the setup effort isn't worth it; basic pixel events are enough.
What else trips people up?
- Optimizing for landing page views instead of subscribes. Someone looking at your page isn't subscribing.
- Trusting a default event that fires too early. We had to fix inflated reporting with an event that fires only after a successful signup.
- Connecting Meta to the form to the CMS. It's the most annoying part, so I do the basics and creative first and the connections last.
Study a working setup to get 90% of the way there. YouTube covers the last 10%.
Answered by TJ Larkin. From pixel setup walkthroughs and publisher onboarding calls in 2026. Last updated .