What the Pixel is for in a B2B store
The Meta Pixel is a piece of code that runs in the visitor’s browser and tells Meta what that person did in the store. Conversion reporting for Facebook and Instagram campaigns relies on this data, and so does audience building, for example people who viewed a product or sent a quote request.
In wholesale and distribution, Meta is rarely the main acquisition channel, but it works well for remarketing and wherever a retail channel runs next to B2B. If you target campaigns by job title and industry, LinkedIn Ads is the better fit. The two can run side by side.
Which actions reach Meta
The platform maps buyer actions to the Pixel’s standard events, the ones Meta knows by name and uses in its reports:
| Storefront action | Meta event |
|---|---|
| Product viewed | ViewContent |
| Added to cart | AddToCart |
| Checkout started | InitiateCheckout |
| Order placed | Purchase |
| Quote request submitted | Lead |
| Contact form submitted | Lead |
Note that a quote request and a contact form are both reported as the same Lead event. In Meta’s reports the two signals cannot be told apart until you give one of them a name of its own.
Your own event names
In the admin panel, under “Meta Ads”, any of the actions above can also be reported under a name you choose. The same goes for two actions that have no standard counterpart: adding to a shopping list and clicking the place-order button.
A custom event is additive: the standard event still fires, and yours fires beside it. A separate name for quote requests therefore lets you build an audience of people who asked for a quote without taking anything away from Purchase or Lead reporting. A mapping can target one sales channel or all of them, and it can be disabled without being deleted.
On Meta’s side, a custom event name must be a string of no more than 50 characters. Custom events can be used to define custom audiences; the details are in Meta’s conversion tracking documentation.
Settings per sales channel
Configuration consists of three settings: an on/off switch, the Pixel ID and the consent requirement. Each can be overridden for a specific sales channel, so a B2B store and a retail store on the same installation can report to different Pixels, or one of them can report nothing at all.
- The integration is off by default and only starts when the switch is on and a Pixel ID has been entered.
- The consent requirement is on by default.
- Permissions are split: one for viewing the configuration, another for changing it and managing custom events.
Visitor consent
With the consent requirement on, no Meta script runs, no cookie is set and no request is sent until the visitor accepts the cookie banner. The same decision applies to Google Analytics 4 and LinkedIn Ads, so the buyer answers once. After consent, the Pixel loads asynchronously and does not block page rendering.
What to prepare on the Meta side
- A Pixel created in Events Manager, and its ID. That is the only value you enter in the platform; you do not paste Pixel code into templates by hand.
- Access to Ads Manager for whoever will check that events are arriving.
- For verification after go-live, Meta recommends the Pixel Helper extension for Chrome, described in the Pixel get-started guide.
Limitations worth knowing
- No Conversions API. Reporting happens from the browser only. Browser pixels are frequently blocked by ad blockers, so the conversion count in Meta will be lower than the order count in the platform. Treat the figures in Ads Manager as a signal for campaign optimization, not as a sales record.
- No conversion retraction. A refunded or cancelled order does not correct a Purchase event that has already been reported.
- Storefront actions only. Meta receives what the buyer did in the browser after giving consent.
If the Meta Pixel is already deployed as a tag in Google Tag Manager, pick one path. Running both means duplicated events. The Meta Ads integration also does not send product data: the catalog for product ads comes from the separate Meta catalog feed.