NewUTM links show country, device and more

Guide for solopreneurs running Meta ads

Meta Pixel lead tracking: make Meta count the leads you really got

Meta Pixel lead tracking means sending Meta a Lead event each time someone really submits your landing page form. Fire it only after the form saves, once per person, from the browser and the Conversions API with the same event ID so Meta counts it once. Then send Purchase when they pay, so Meta finds buyers, not form-fillers.

Works for ads that send people to your own landing page, not Facebook instant forms.Why instant forms are different →

Start 7-day free trial

7 days of Team, free. No card needed.

Example One week of a consultant's ads: what was sent to Meta, and what really happened
What happened on the pageBadly set up pixelSet up as in this guide
Someone clicks Submit but the phone number is invalid, so the form doesn't saveLeadNothing (no lead was saved)
Someone fills the form twice in a day2 Leads1 Lead
Someone on Safari with an ad blocker fills the formNothing (pixel blocked)1 Lead, from the server
A lead books a call and you mark them Call booked in your sheetNothingSchedule
A lead pays on Razorpay and never reaches the thank-you pageNothingPurchase, with the ad click they came from

What does the Meta Pixel Lead event actually do?

The Meta Pixel is a small piece of code from your Events Manager that runs on your page. Each event it sends tells Meta something happened: PageView when the page loads, Lead when someone becomes a lead, Purchase when they pay.

Meta uses those events for two jobs:

  • Reporting. The Results and Cost per result columns in Ads Manager come from them.
  • Optimisation. A campaign set to get leads shows your ads to people who look like the ones who sent a Lead before. Send a Lead for the wrong people and Meta goes and finds more of the wrong people.

So the events are not just a counter. They are the brief Meta's ads work from. If you send it junk, you pay for more junk.

Why doesn't Meta's lead count match the leads you got?

Almost every solopreneur running ads to a landing page sees it: Ads Manager says 40 leads, the sheet has 31. The usual reasons:

ReasonWhat happens
Lead fires on the button clickThe pixel sends Lead when Submit is pressed, even when the form fails or the person leaves before it saves.
RepeatsThe same person submits twice, or refreshes the thank-you page, and Meta gets two Leads.
Blocked browsersAd blockers, Safari and some in-app browsers stop the pixel, so real leads never reach Meta.
Different daysMeta counts a lead on the day of the ad click or view (up to 7 days before); your sheet has the day the form was filled.
Meta estimates someFor people who turned off tracking (many iPhones), Meta adds modelled leads it can't see, so it can show more than came in.
Instant formsLeads from Meta's own lead forms never reach your page, so they're in Ads Manager, not in your sheet.
Came back another waySomeone clicks an ad and returns later from Google or WhatsApp. Meta still credits the ad.

Some of these you can't remove: Meta's attribution window and modelled results are how Meta reports. The first three you can fix, and they are the ones that teach Meta the wrong thing.

How do you set up Meta Pixel lead tracking that matches your real leads?

Four rules, whichever tool you use:

  1. Fire Lead only after the form really saves. Not on the button click, and not on the thank-you page load (people refresh it and share it).
  2. One Lead per person. If the same email or phone submits again, don't send another Lead.
  3. Send it twice, count it once. Send the Lead from the browser pixel and from your server through the Conversions API, so blocked browsers still reach Meta. Give both copies the same event name and the same event ID: Meta's documentation says that is how it recognises the two as one event, and it generally keeps whichever arrives first.
  4. Tell Meta what happened next. A Lead is a form fill. Send Purchase when they pay, and an event when a lead turns good, so the campaign can learn who buys.

Doing this by hand means editing your form's code, running a server that calls the Conversions API, storing who you've already sent, and connecting your payment gateway. That's the part ownyourclick does for you.

How does ownyourclick send leads and purchases to Meta?

ownyourclick receives the lead itself (it's the form fill that lands in your Google Sheet), so the events it sends Meta are leads that really reached your Leads tab.

  1. In ownyourclick, go to Pages → Add page, paste your landing page's address and add the tag it gives you to the page's <head>. Your form's leads now arrive in your sheet with their source and hot %.
  2. Open the page, then its Meta ads tab. Add your Pixel ID and choose the events to send: Page view, Lead, Purchase. The tag loads the pixel for you; if the page already runs the same pixel, the tag uses it and doesn't start a second copy.
  3. Add a Conversions API access token (from Events Manager) so the events go from the server as well. The browser and server copies carry the same event ID, so Meta counts each lead once.
  4. Check it. In Events Manager open Test events, copy the code, save it on the Meta ads tab and press Send test event. Remove the code when you've seen it arrive.

What it does for each lead:

  • Lead is sent only after the lead is saved, never on a click that didn't become a lead.
  • The same person (same email or phone) submitting again within 30 days isn't sent as another Lead.
  • Purchase comes from the payment: from your thank-you page, or straight from Dodo Payments, Razorpay or Stripe on the Payments tab. It carries the ad click from when that person first landed, so Meta can credit the sale to the ad even though the payment was confirmed later by the gateway. How the gateway connection works, and why it catches buyers who never reach your thank-you page: payment tracking.

How do you tell Meta which leads were good?

On the Meta ads tab, under When a lead's status changes, tell Meta, pick which of your statuses send an event:

When a lead reaches… (your status)Meta gets
InterestedQualified lead
Call bookedSchedule
ContactedContact
PaidPurchase

You change the status in ownyourclick or straight in your Google Sheet (a connected sheet syncs back within about 30 seconds), and the event goes to Meta. Over time you can point a campaign at the event that matters, such as Purchase, instead of every form fill. Think of the funnel as 100 people see the ad, 50 click, 20 fill the form, 5 buy: the 5 are who you want Meta to find more of.

The statuses above are an Example: use your own names.

Where can you see Meta Pixel data, and check it's working?

  • In Meta: Events Manager shows each event your pixel and Conversions API received, and Test events shows them live while you test. Ads Manager's Results column shows what each ad got.
  • In ownyourclick: the Meta ads tab. Pick what your campaign is optimised for (Leads, Purchases or Landing page views) and a period (Today, 28 days or Custom). It compares what ownyourclick recorded from your Meta ads, what it sent to Meta and what Meta accepted, says why any are missing, lists every event sent, and explains the usual reasons Meta's count differs from yours.

Use the two together: when Ads Manager and your sheet disagree, the tab tells you whether a lead was never sent, was a repeat, or was refused by Meta.

What doesn't this fix?

  • Instant forms. Lead ads that keep people inside Facebook never reach your page, so ownyourclick doesn't capture them or send their events. Switch the ad to your landing page to track them.
  • Your own Lead code. If your page or form plugin already sends Lead or Purchase to the same pixel, turn those off on the Meta ads tab (or remove your code), or they count twice.
  • Meta's reporting rules. Attribution windows and modelled results still apply, so the two numbers can differ by a few even when everything is right.
  • Spend. ownyourclick doesn't import ad spend. For cost per paying customer, divide the ad's spend in Ads Manager by its paying leads in your sheet.

Questions

What do people ask?

What's the difference between the Meta Pixel and the Conversions API?+

The pixel sends events from the visitor's browser; the Conversions API sends them from a server. Browsers with ad blockers, Safari and some in-app browsers can stop the pixel, so sending both, with the same event ID, gets more of your real leads to Meta without counting any twice.

Should the Lead event fire on the button click or the thank-you page?+

Neither, ideally. A button click fires even when the form fails, and a thank-you page fires again on every refresh. Fire Lead when the form submission is actually saved. ownyourclick sends it only after the lead reaches your Leads tab.

How do I stop Meta counting leads twice?+

Send each lead once per person, and give the browser and server copies the same event name and event ID so Meta deduplicates them. If your own code also sends Lead to the same pixel, turn one of them off.

Can Meta optimise for purchases instead of leads?+

Yes, if it receives Purchase events. With ownyourclick, a payment from your thank-you page or from Dodo Payments, Razorpay or Stripe is sent to Meta as Purchase with the ad click the buyer first came from, and you can also send Purchase when you mark a lead Paid.

Does this work with Facebook instant forms?+

No. Instant forms keep people inside Facebook, so there's no landing page visit to track. Send the ad to your own landing page with the ownyourclick tag instead.

Do I need to be a developer to set this up?+

No. You add one tag to your page's <head>, then paste your Pixel ID and Conversions API access token on the page's Meta ads tab and press Send test event to check it.

How do I test my Meta Pixel?+

In Events Manager, open Test events and copy the test code. In ownyourclick, save it on the Meta ads tab and press Send test event; the event appears in Test events. Remove the code afterwards, because events sent with a test code don't count in your ads.

Was this page helpful?

Send Meta the leads you really got

7 days of the Team plan, free. No card needed. Then from ₹699 a month.

Start 7-day free trial