FR
← Blog
Advertising

Meta pixel conversion events an SME should send

September 2026 · Advertising · Quebec City

Most SME ad accounts send Meta a single signal: the page load. That counts visits, and it says nothing about what you want to get. Conversion events are the actions you declare as results. Without them your ads manager shows clicks, the system optimises toward traffic, and nobody can tie a dollar of spend to a quote request. This page gives you what it takes to judge what is wired up in your own account, and what to demand from whoever wires it.

This is the pattern I run into most often when I open a Quebec manufacturer's ad account for the first time. The pixel is in place, the install was invoiced, and not one event corresponds to real purchase intent. The full method sits on the Facebook and Meta advertising page.

PageView is not a standard event

Here is the distinction half the articles on this subject get wrong. Meta documents the pixel base code as a snippet you add between the opening and closing head tags on every page where you will be tracking visitor actions. That code carries your pixel ID in two places, and it automatically tracks a single PageView conversion each time it loads.

So PageView does not appear in Meta's standard events table. It is not an event you add, it is the one the base code fires on its own. The consequence is direct: an account that has only PageView has no conversion events at all. It has an installation, not a measurement. When a supplier offers PageView as proof that tracking works, that answer should end the conversation.

The 17 standard events, and the seven that concern you

Meta documents exactly seventeen standard events, described as predefined visitor actions that correspond to common conversion-related activities. The names are spelled the way Meta spells them, with no spaces. Here is the complete list, with Meta's own description.

A Beauce fabricator selling custom systems has no use for AddToCart, InitiateCheckout or Purchase. Seven of the seventeen describe its reality: Lead, Contact, CompleteRegistration, Schedule, SubmitApplication, ViewContent and Search. Picking the right ones out of the seventeen is a business decision, not a technical task. It belongs to whoever knows what a good customer looks like in your shop, and it gets made before anyone touches the website.

Meta also documents eleven properties an event can carry, among them a value, a currency, a content name and a content category. That is the difference between an account that counts requests and an account that knows which ones are worth something.

Custom conversions: useful, and capped

Alongside standard events, Meta documents custom conversions: visitor actions tracked automatically by parsing your website's referrer URLs, without adding new events to the pixel. Meta's own example is a conversion that tracks visitors who viewed any page with a thank-you segment in its URL.

Two things to hold on to before you accept that approach. First, it leans on PageView events plus URL patterns, so it is worth exactly what your site structure is worth. Second, there is a ceiling written into Meta's documentation: the maximum number of custom conversions per ad account is 100. That is not a constraint for a healthy SME account. It is one for an account nobody has ever cleaned out.

What the Conversions API changes, and the double-counting trap

The pixel speaks from the browser. The Conversions API sends the same events from a server, a website platform or a customer relationship system. Meta states that these server events are processed like pixel events, and may be used for measurement, reporting and optimisation in a similar way.

Running both at once is what Meta calls a redundant setup, and it requires deduplication. The rule is documented: the pixel's event ID must match the ID sent through the API, and the event name must match as well. When Meta finds the same combination sent to the same pixel within 48 hours, the later events are discarded.

This is why the subject concerns you even if you will never touch a line of code. A redundant setup done badly doubles your results, inflates your numbers and drives your apparent cost per result down. You celebrate a performance that does not exist, then raise the budget on the strength of it. The question to ask is short: are both sources sending, and do the identifiers match. A supplier who does not understand the question should not be installing the Conversions API.

The attribution window decides what you are reading

Two people can look at the same campaign and read two different numbers. The gap often comes from the attribution window. Meta documents a default setting of 7 days after a click plus 1 day after a view, and documents 1-day, 7-day and 28-day windows for both clicks and views.

One exception is worth knowing before you compare two reports: inline link clicks use a fixed 1-day-click attribution window. These are Meta's documented definitions from its developer reference, not the tooltips in the interface. When a monthly report quietly changes window from one month to the next, the improvement on the page is not an improvement, it is a change of rule.

When none of this applies

An SME whose sales close over the phone, after a plant visit and three meetings, cannot make a purchase event mean anything. There is no online transaction to track, and forcing a Purchase event onto a form does not create a sale, it creates a false number.

For that company the only useful events are the few that mark genuine intent: a quote request, a booked meeting, a visit to the one page only a serious buyer reads to the end. The rest of the measurement does not happen in the ads manager, it happens in the sales log. What the pixel can do is tell you which campaigns come before the good conversations. It will never tell you which one signed. A supplier promising otherwise is selling a certainty the platform does not provide.

Sources

If you want to know what your account actually sends Meta before adding a dollar of budget, we can look at it together.

Book my call
Home · Portfolio

B2B Marketing · Industrial Marketing · Uncompressed · ClientGallery

© 2026 MarketingSTRAT