Meta Integration: Fitment-Aware Conversions API & Catalog
The only Meta catalog that knows which parts fit which truck. Vehicle fitment rides in the catalog labels and on every Conversions API event, deduped against the browser Pixel. Built into Web Shop Manager 6.0 and validated against Meta's Conversions API spec, July 2026.
Contact Meta
Reach out to us for any inquiries or support, and
let’s connect!
Get in touch with us
Reach out to us for any inquiries or support, and let’s connect!
The only Meta catalog that knows which parts fit which truck
Every catalog feed on the market ships Meta the same three fields: title, price, availability. Web Shop Manager ships those, plus the customer’s Year, Make, and Model mapped straight into Meta’s own catalog labels. That is the difference between an Advantage+ campaign that shows brake pads to everyone, and one that shows Wrangler owners Wrangler parts. Nobody else selling into this platform’s marketplace does that, and it is the one signal Meta’s own iOS and ad-blocker losses cannot touch.
Built and validated against Meta’s Conversions API spec, July 2026.
Fitment is the most valuable signal in automotive. Every other Meta catalog throws it away.
Your shoppers tell you exactly what they drive: in the year/make/model search, in the garage, at checkout. Generic catalog feeds and generic pixel apps drop that signal on the floor, because they were built for stores that sell one product to everyone. Web Shop Manager was built the other way around: the vehicle rides the catalog feed, rides the conversion event, and becomes a segment Advantage+ can actually target.
Fitment mapped into your catalog feed
Vehicle Make, Model, and Year range map into Meta’s custom_label_0 through custom_label_3 on every item (with a fourth label reserved for your own use), plus fitment written into the item description. Build an Advantage+ Shopping campaign or a dynamic retargeting ad segmented by vehicle, not just by SKU.
Purchase events straight from the order system
Purchase fires server-side the moment an order is fully paid, carrying value, currency, order_id, and line items straight from Web Shop Manager, not a browser guess. When Safari, an ad blocker, or a dropped cookie kills the Pixel’s view of the sale, the server event still lands.
Deduped, not doubled
The storefront Pixel and the server-side Conversions API event share one event id, seeded from the order token. Meta counts the conversion once. Get the setup wrong on your own and you are reporting phantom revenue to your own ad account.
Advanced matching, maxed out
Hashed email, phone, first and last name, city, state, zip, country, and a hashed external id ride on every event, normalized to Meta’s own spec. Higher match quality means Meta spends less of your budget finding the person it already knows bought from you.
Checkout signal, captured
InitiateCheckout fires the moment a shopper starts checkout, with the same fitment-aware line items and a shared event id with the browser Pixel. Retargeting sees the cart, the vehicle, and the parts left behind.
Paste it in, no developer, no app review
A pixel ID and a Conversions API access token, both self-generated in Events Manager. No Meta developer app, no business verification, no waiting on Meta’s review queue. Send a test event, confirm it lands in Meta’s own Events Manager, and it is live.
What Meta’s Events Manager sees
This is an actual Purchase event payload from a live test store, exactly as Meta’s Conversions API receives it. Every custom_label below is a filter Advantage+ can target on.
event_name: Purchase
event_id: ord_8f21c4 (shared with the browser Pixel)
order_id: 8f21c4
value / currency: 428.90 / USD
user_data: em, ph, fn, ln, ct, st, zp, country (all SHA-256 hashed)
external_id (hashed), fbp, fbc, client_ip, client_user_agent
custom_data: content_ids, contents
Catalog item: custom_label_0: "Ford" custom_label_1: "F-150"
custom_label_2: "2019" custom_label_3: "Lariat"
Web Shop Manager vs. everyone else
Generic platforms give you a Pixel and a catalog feed with no vehicle field. Bolt on a year/make/model lookup plugin and the vehicle still never reaches Meta. The purpose-built parts platforms do not expose a Conversions API integration at all. Every column shows the best case, measured against Meta’s own Conversions API and Catalog documentation.
| Capability | Web Shop Manager 6.0 | Generic platforms | Generic platforms with a Year / Make / Model plugin | Purpose-built parts platforms⁵ |
|---|---|---|---|---|
| Fitment and vehicle marketing | ||||
| Vehicle (Year / Make / Model) mapped into Meta catalog labels | ● | ○ | ○plugin data never reaches the feed⁴ | ○ |
| Fitment on Purchase and checkout events, not just the catalog | ● | ○ | ○ | ○ |
| Advantage+ / dynamic ads filterable by vehicle | ● | ○ | ◐last vehicle only, client-side⁴ | ○ |
| Fitment written into catalog item descriptions | ● | ○ | ○ | ○ |
| Conversions API | ||||
| Purchase events server-side, with order_id | ● | ● | ● | ○ |
| InitiateCheckout server-side for abandoned-cart retargeting | ● | ◐varies | ◐varies | ○ |
| Deduped browser Pixel + server event on one shared event id | ● | ◐manual setup, easy to get wrong | ◐manual setup, easy to get wrong | ○ |
| Advanced matching: hashed email, phone, name, address, external id on every event | ● | ◐varies, often email only | ◐varies, often email only | ○ |
| Retry handling and a broken-token alert when a delivery fails | ● | ○ | ○ | ○ |
| Setup and ownership | ||||
| Paste-credentials setup, no developer required | ● | ● | ● | ○ |
| No Meta app, no business verification, no App Review wait | ● | ● | ● | ○ |
| Managed, per-store catalog feed URL, kept current automatically | ● | ◐manual export or third-party feed tool | ◐manual export or third-party feed tool | ○ |
| Per-event on/off toggles and delivery log in your platform admin | ● | ○ | ○ | ○ |
● Live today, verified against Meta’s own Conversions API and Catalog documentation, July 2026 ◐ Possible with manual setup, or varies by platform ○ Not available
- ¹ Meta’s Conversions API documentation: matching relies on the fields you send; platforms that pass email only see lower match rates than a full hashed identifier set.
- ² Meta’s deduplication guidance: pixel and server events must share an identical event_name and event_id, or they double-count. Generic setups leave this to whoever wires up the Pixel.
- ³ Meta’s catalog fields (title, description, price, availability, link, image_link, brand, item_group_id) carry no vehicle field unless something upstream writes one in; generic feed exports do not.
- ⁴ The best year/make/model lookup plugins store a single client-side “last vehicle selected” value. It does not reach the catalog feed and does not reach server-side conversion events.
- ⁵ The purpose-built parts platforms offer no documented Conversions API or catalog-feed integration for Meta, verified against their marketplaces and Meta’s own partner directory, July 2026.
Score your current setup against this table, book 20 minutes
Meta’s Conversions API and Catalog, if you’re new to them
Meta’s Conversions API is the server-to-server path for sending Facebook and Instagram conversion events, built to survive the browser signal loss that iOS privacy changes and ad blockers cause for pixel-only tracking. Catalog feeds power Advantage+ Shopping and dynamic retargeting ads by giving Meta a live view of your product inventory. Web Shop Manager’s integration is built on Meta’s current Graph API, not a legacy plugin, and requires nothing on Meta’s side beyond a self-generated pixel and access token. The same fitment data also drives our Klaviyo and Google Ads integrations, if you are wiring up more than one channel. Learn more at developers.facebook.com, or ask us to walk you through it on your own catalog.
Meta and Web Shop Manager: what dealers ask
Straight answers for parts dealers weighing the connection between Web Shop Manager and Meta.
What is fitment-aware catalog advertising?
It means the vehicle a part fits, the year, make, and model, becomes real data on the catalog item Meta serves ads from, not just a search filter on your product page. That lets Advantage+ Shopping and dynamic retargeting target “Wrangler owners” or “Tacoma owners” directly, instead of showing the same brake pad ad to every visitor. Web Shop Manager maps that vehicle data into Meta’s own catalog labels, so it powers real ad targeting, not just an on-site lookup tool.
Do I need a developer or a Meta app to set this up?
No. Conversions API and catalog feeds both use credentials you generate yourself in Meta’s Events Manager and Commerce Manager, no Meta developer app or business verification required. Paste the pixel ID and access token into Web Shop Manager on a screen share, and events start flowing.
Will this double-count my conversions if I already have the Meta Pixel installed?
No, as long as the Pixel and the server-side event share the same event id, which Web Shop Manager handles automatically by seeding both from the order token. Meta’s own deduplication logic sees one event, not two, and only counts the conversion once.
What events does Web Shop Manager send to Meta?
Purchase fires server-side the moment an order is fully paid, and InitiateCheckout fires when checkout starts. Both carry value, currency, line items, and a shared event id with the browser Pixel. Every event carries hashed advanced-matching data: email, phone, name, address, and a hashed customer id.
Can I run Advantage+ Shopping ads segmented by vehicle?
Yes. Because Year, Make, and Model map into Meta’s custom_label fields on every catalog item, filtering an ad set or a dynamic retargeting audience by vehicle is a normal Commerce Manager filter, not a custom build.
What happens when Safari or an ad blocker kills the Pixel?
The Purchase event still lands, because it comes from the order system on our servers, not from a script running in the shopper’s browser. Your reported ROAS does not collapse when browser tracking does.
Does this include Custom Audiences or managing my ad campaigns?
No. This integration covers Conversions API events and the catalog feed. Building and managing the ad campaigns themselves stays in Meta Ads Manager, where it belongs. Custom Audiences syncing is not part of this integration today.
How is this different from a year/make/model plugin?
A typical year/make/model plugin stores only the last vehicle a shopper selected, in the browser, and that value never reaches Meta at all. Web Shop Manager writes the vehicle into the catalog feed itself and onto the conversion events, server-side. See how this fits into the bigger picture of automotive eCommerce.
Is customer data handled safely?
Yes. Email, phone, name, and address are SHA-256 hashed before they leave our servers, exactly to Meta’s own normalization spec. Raw personal data is never sent in the clear, and access tokens are encrypted at rest.
See your parts, your fitment labels, and server-truth conversions in Meta
Book 20 minutes. We will connect a demo store with your catalog and show you the vehicle-segmented Advantage+ campaign your competitors cannot build. Bring your best-selling SKU and the truck it fits. If you have a Meta Business portfolio and a pixel, we turn it on with you on a screen share. No developer required.
Get Started Now: Fitment-Aware Meta Advertising
Paste a pixel ID and a Conversions API token, no developer required. Click below to see it running on your own catalog.
See Meta Integrated on Your Store
Ready To Grow Your Business?
Ready to grow your aftermarket eCommerce presence and lift conversions across auto, truck, powersports, marine, and more? Connect with
Web Shop Manager for tailored solutions: strategy, platform, and performance in one team.