SEO

Meta Pixel and Conversions API: a practical guide for businesses in Mexico

Meta optimizes toward what you report. Which events to measure, how the Pixel and the Conversions API work together, how to avoid counting every sale twice and what to check in Events Manager before spending the first peso.

Equipo GrowFlow8 min read

In Meta Ads the algorithm learns from what you report. If your account only tells it someone clicked, it will find you more clicks; if it tells it someone messaged you on WhatsApp or left their details, it will look for more people like that. That's why measurement isn't a technical detail to leave for later: it's the instruction you give Meta about who to find. This guide explains the two pieces that make it possible, the Pixel and the Conversions API, and how to set them up so they complement each other instead of getting in each other's way.

What the Pixel does and what the Conversions API does

The Meta Pixel is a snippet of code that lives on your site and sends events from the visitor's browser: they viewed a page, submitted a form, completed a purchase. It's easy to install, but it depends on the browser, and many browsers now block third-party cookies or scripts, especially on iPhone and with privacy extensions.

The Conversions API sends those same events from your server straight to Meta. Since it doesn't go through the browser, blockers don't stop it, and it can also report things that happen off your site, like a sale you closed by phone or at the counter. Meta recommends using both together: the Pixel provides the browser signal and the Conversions API covers what the browser loses.

Meta PixelConversions API
Sends fromThe visitor's browserYour server
Affected by blockersYesNo
SetupCode on the site or a tagServer integration or a Meta partner
Off-site eventsNoYes: in-store, phone or message sales
Deduplication neededYes, if you also send the event through the APIYes, if you also send the event through the Pixel

Which events to measure (and which not to)

Meta has a list of standard events with fixed names, and it's worth using them instead of inventing your own, because they're the ones the system recognizes for optimization. For most service businesses in Mexico, these are the ones that matter:

  • Lead: when someone submits a form with their details.
  • Contact: when someone reaches out by phone, email or chat, for example by tapping the WhatsApp button on your site.
  • Schedule: when someone books an appointment to visit you.
  • Purchase: when a purchase is completed, with its value and currency (MXN).
  • ViewContent and InitiateCheckout: useful in online stores to build audiences, not as the campaign goal.

The most common mistake is optimizing toward an event that's too easy, like PageView or a click, because "more of them come in." Meta will bring you exactly that: visits that never write. Choose as your goal the event closest to the sale that happens often enough for the algorithm to learn. According to Meta's help page on the learning phase, an ad set needs about 50 optimization events in the 7 days after its last significant edit to exit that phase. If your final event is very rare, optimize toward the step before it while you gather data.

Deduplication: make every sale count once

If you send the same event through the Pixel and the Conversions API without telling Meta it's the same one, it counts it twice: your report shows double the forms and the algorithm learns from inflated data. The fix is event deduplication. Meta recommends the event ID and event name method:

  1. Generate a unique identifier for each event at the moment it happens, for example when the form is submitted.
  2. Send it in the Pixel as eventID, passed as the fourth parameter of the fbq('track') call.
  3. Send the same value in the Conversions API as event_id.
  4. Use exactly the same event name on both sides: Lead in the browser and Lead on the server.

Meta deduplicates events that share an ID and name if they arrive within 48 hours, and generally keeps the one it received first. If the ID changes between browser and server, or the name has different capitalization, deduplication fails and you won't see an error: just inflated numbers.

If you sell on WhatsApp: messaging events

Many businesses in Mexico don't close on the site but in the chat. That's what the Conversions API for Business Messaging is for: it reports what happens inside the WhatsApp, Messenger or Instagram Direct conversation with action_source set to business_messaging. That way you can tell Meta which chats became a qualified lead (LeadSubmitted) or a sale (Purchase), not just how many conversations were opened. The documentation states that purchase optimization is available for ads to Messenger and WhatsApp. We cover it in detail in Facebook and Instagram ads that lead to WhatsApp.

Domain, portfolio and data ownership

Before installing anything, verify your domain in your Meta business portfolio. Verification proves the site is yours, and it's done with a meta tag on your page, an HTML file at the root or a TXT record in your DNS. And make sure the Pixel's dataset is created inside your business's portfolio, not an agency's or a freelancer's: the event history and the audiences built from it are an asset, and if the Pixel isn't yours, you lose it the day you change providers.

How to check that everything works

  • In Events Manager, use the Test Events tool and complete a conversion yourself: you should see the browser event and the server event, with one marked as deduplicated.
  • Check the event match quality of each server event; if it's low, customer data is missing.
  • Compare the forms or sales Meta reports in a week against the ones you actually received. A large gap upward is usually broken deduplication; downward, events that aren't being sent.
  • Confirm in the ad set settings that the campaign optimizes toward the right event, not link clicks.
Do I need the Conversions API if I already have the Pixel?
It's what Meta recommends. The Pixel loses events when the browser blocks cookies or scripts, and the Conversions API sends them from your server. Together, with deduplication, they give Meta a more complete signal.
Why does Meta report more sales than I had?
Most often the same event arrives through the Pixel and the API without the same event_id, and Meta counts it twice. Check that both send the same ID and the same event name.
Which event should I choose as my campaign goal?
The one closest to the sale that happens often enough for the algorithm to learn. For service businesses it's usually Lead, Contact or Schedule; for stores, Purchase.

Measurement is the first thing we set up on any account as a Meta Ads agency, before the first ad. If you're choosing between platforms, read Meta Ads or Google Ads, and if you want to understand how management is priced, see how much a Meta Ads agency charges in Mexico.