Meta Ads conversion tracking for marketplace sellers
This page exists to say something most vendors will not: if your sales happen on Amazon, Etsy or Walmart, the marketplace owns the customer, the checkout and the data, and the per-order click attribution this site builds for other platforms is not available to you. What Meta Ads adds on top of that is a mechanical requirement: fbclid and _fbc have to reach the record that holds the money, because Meta can only credit a conversion it can tie back to a click it recognizes. This page covers both halves — what a conversion is in marketplace sellers, and what Meta specifically needs to accept it.
Free30 minutesNo obligation
Specific to Meta × Marketplaces
Meta ads for marketplace sellers: no Purchase event, only proxies
Meta cannot receive a Purchase for an order completed on Amazon, Etsy or Walmart, because neither the Pixel nor the Conversions API can see the marketplace checkout. Marketplace sellers should report Meta-driven sales through Amazon Attribution tags or campaign-specific promo codes, and send Purchase only from their own store, where fbclid and _fbc capture work normally.
Meta optimizes toward whatever event you pick, and a seller sending traffic straight to Amazon can only pick link clicks or landing page views, which find cheap clickers rather than buyers. Some sellers route ads through a page they own and fire a custom event when the visitor clicks through to Amazon. That gives Meta a signal with more intent than a click, but it is still not a purchase, and the drop between that click and the order is the part nobody can see.
Use a distinct Amazon Attribution tag per ad set or creative angle so Amazon's aggregate report can at least rank them. For a sharper read, check whether your Seller Central account offers social media promo codes; a code that appears in only one Meta campaign gives a clean count of the orders that campaign produced.
Etsy sellers should know that Etsy may already be buying Meta ads for their listings through its Offsite Ads program, and Etsy attributes and charges for those sales separately from any campaign the seller runs. Running both can mean paying twice to reach the same shopper, and Etsy's report will not say which ad that shopper saw. Check your Offsite Ads status before deciding how much of your own Meta budget is adding anything.
Meta · Marketplaces · what breaks
Why Meta under-reports for marketplace sellers
- 01
The marketplace owns the checkout and the customer
You get an order report, not a click-to-order join. No tool changes this.
- 02
Off-marketplace ads that cannot be attributed per order
You can drive traffic to a listing and you cannot see which click produced which sale.
- 03
Vendors selling per-order attribution that does not exist
The most common thing sold into this category, and it does not work the way it is described.
- 04
Fbclid and _fbc never reaches the record
fbclid arrives on the landing URL and is normally written into the _fbc cookie. If it isn't captured on landing, _fbc never exists — and _fbc is the strongest click signal Meta has, so its absence caps your match quality regardless of what else you send. Forward _fbp too, from the browser rather than regenerating it server-side.
Meta · Marketplaces · the fix
What working looks like — Meta · Marketplaces
A clear statement of what can and cannot be measured
Before you spend anything, so the decision is informed.
The marketplace's own tools used properly
Attribution programs, brand analytics and promo-code tracking each do something real within their limits.
Your own channels measured properly
If you also sell direct, that side is fully measurable and is usually where the attention should go.
Meta · Marketplaces · architecture
How Meta and marketplace sellers actually connect
- 1
The conversion in marketplace sellers
The conversion map here is mostly a map of what is missing. The marketplace records the order and shares an aggregate; there is no identifier that travels from your ad to that order, so the events below are the honest maximum.
- 2
Meta Ads needs a click to match
event_name from the standard set with exact casing, event_time in seconds, a shared event_id, an action_source, and hashed user_data that was normalized before hashing. Purchase additionally requires value and currency.
- 3
The identifier: fbclid and _fbc
fbclid arrives on the landing URL and is normally written into the _fbc cookie. If it isn't captured on landing, _fbc never exists — and _fbc is the strongest click signal Meta has, so its absence caps your match quality regardless of what else you send. Forward _fbp too, from the browser rather than regenerating it server-side.
- 4
Where it gets sent from
The marketplace's own order and settlement reports, with their aggregation level understood before anything is compared.
- 5
Deduplication and window
This is the mechanism that decides whether adding CAPI helps or doubles your conversions. Both the Pixel and the server event must carry the same event_id — the order or booking reference works best, because both sides can produce it without coordinating. A case difference in the event name alone produces two events even with a matching ID. Read the Deduplicated indicator in Events Manager over a full week, not one session. Meta's default attribution is a 7-day click and 1-day view. View-through is included by default, which is a large part of why Meta claims more conversions than your other platforms — that overlap is expected rather than a fault.
Meta · Marketplaces · events
The conversion map for marketplace sellers
Five things, only some of which are measurable, and the page says which.
| Event | What it means here |
|---|---|
| Off-marketplace ad click | Measurable on your side. It stops being traceable the moment it reaches the listing. |
| Listing view | Available in aggregate through the marketplace's own analytics, not per visitor. |
| Order placed | The marketplace records it. No click identifier attached, ever. |
| Attribution program reporting | Aggregate and delayed where the marketplace offers it. Directional, not reconcilable. |
| Promo code redemption | The one clean per-order signal you can create yourself. |
Meta · Marketplaces · diagnose
Diagnostic order — Meta · Marketplaces
- 01
Count records carrying fbclid and _fbc
- 02
No click identifier on the order
The structural fact underneath everything else on this page.
- 03
Aggregate reporting treated as measured conversions
Marketplace attribution programs report at a level that cannot be reconciled per order, and trying to will waste weeks.
- 04
Customer data the marketplace will not release
Which also limits what remarketing and matching are possible.
- 05
Read the Deduplicated indicator and the per-event match quality score, both read over seven days
Match quality is where most Meta accounts lose attribution, and it's almost always normalization rather than coverage. An email hashed with a capital letter, or a phone hashed with brackets, produces a perfectly valid hash that matches nobody and errors nowhere. Normalize first, then hash, and read the score per event rather than overall.
Meta · Marketplaces · prove
How it gets proven — Meta · Marketplaces
Source of truth
The marketplace's own order and settlement reports, with their aggregation level understood before anything is compared
- A plain statement of what is and is not attributable, before any work is commissioned.
- Promo-code redemptions reconciled per order where that mechanism is used.
- Direct-store revenue measured fully and reported separately from marketplace revenue.
- No number presented as measured when it came from an aggregate model.
- The Deduplicated indicator and the per-event match quality score, both read over seven days read directly, not inferred from an upload succeeding.
Meta · Marketplaces · free audit
What we check in the free audit
- Count records carrying fbclid and _fbc
- No click identifier on the order
- Aggregate reporting treated as measured conversions
- Customer data the marketplace will not release
- Read the Deduplicated indicator and the per-event match quality score, both read over seven days
Checked against
The marketplace's own order and settlement reports, with their aggregation level understood before anything is compared
Free30 minutesNo obligation
Meta · Marketplaces · when not to buy
When you don't need this — Meta · Marketplaces
- If Meta already reports conversions that reconcile against the marketplace's own order and settlement reports within a few percent, this is working and there is nothing to buy.
- Measure identifier coverage yourself first — pull your last hundred records and count how many carry fbclid and _fbc.
- If you're advertising a business type Meta restricts data collection for — health being the obvious one — the parameters you can legitimately send are narrower, and that constraint should shape the build rather than be worked around.
Meta · Marketplaces · what we deliver
What gets built — Meta · Marketplaces
Marketplace attribution tools configured where they exist
Amazon's attribution program and equivalent tools give aggregate rather than per-order insight. Useful, and not the same thing.
Unique promo codes or landing paths per channel
The practical way to separate channels without a click join.
Your direct-to-consumer store measured fully
Where a real per-order build is possible and worth doing.
Nothing claimed that the data cannot support
The reporting states its own limits.
Dispatch via the Conversions API
Server events go through CAPI with an action_source describing where the conversion happened. Offline outcomes flow through the same API rather than a separate product. Verify current field names against Meta's documentation before building — this surface changes.
Written guarantee
95%+ tracking accuracy
Measured against The marketplace's own order and settlement reports, with their aggregation level understood before anything is compared. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
Meta · Marketplaces questions, answered
No. Amazon does not allow third-party pixels on its pages, so Meta never sees the purchase. Use Amazon Attribution tags or promo codes instead.
If you have a direct store, campaigns sent there can optimize on real Purchase events and usually learn faster. Amazon-bound campaigns run blind, so keep them for products where Amazon's reviews or Prime delivery carry the sale.
No, and neither can anyone else. Amazon does not attach a click identifier from your off-site ad to the resulting order, and it does not release the customer data that would allow a match. Amazon's own attribution program gives aggregate, delayed reporting — genuinely useful, and not the per-order join this site builds for Shopify or WooCommerce. Anyone quoting you for the latter is describing something that does not exist.
Three things. Use the marketplace's own attribution and analytics tools properly, since most sellers do not. Use unique promo codes or channel-specific landing paths where you need a clean per-order signal. And if you also sell direct, put the real measurement effort there — that side is fully attributable and usually under-invested.
The data is a reason, not the reason. A direct channel gives you the customer relationship, better margins and full attribution together. If you are weighing it, the measurement gain is real and it should not be the whole argument.
fbclid arrives on the landing URL and is normally written into the _fbc cookie. If it isn't captured on landing, _fbc never exists — and _fbc is the strongest click signal Meta has, so its absence caps your match quality regardless of what else you send. Forward _fbp too, from the browser rather than regenerating it server-side.
Server events go through CAPI with an action_source describing where the conversion happened. Offline outcomes flow through the same API rather than a separate product. Verify current field names against Meta's documentation before building — this surface changes.
By reading the Deduplicated indicator and the per-event match quality score, both read over seven days and reconciling against The marketplace's own order and settlement reports, with their aggregation level understood before anything is compared. An upload that succeeds is not an upload that matched.
More on Meta · Marketplaces
- MarketplacesConversion tracking for marketplace sellers, and what is genuinely impossible
- Google Ads · MarketplacesGoogle Ads conversion tracking for marketplace sellers
- TikTok · MarketplacesTikTok Ads conversion tracking for marketplace sellers
RELATED GUIDES
More for marketplace sellers: other angles on the same outcome
- MarketplacesConversion tracking for marketplace sellers, and what is genuinely impossible
- Meta · CannabisMeta Ads conversion tracking for cannabis businesses
- Meta · Crypto and tradingMeta Ads conversion tracking for crypto and trading platforms
- Meta · Add to cart → purchaseHow to track add to cart to purchase for Meta Ads
- Meta × Ecommerce OrdersHow to reconcile Meta Ads against your store's order table
- Meta · Crypto exchangesMeta Ads conversion tracking for crypto exchanges and platforms
- Meta · Online gamblingMeta Ads conversion tracking for online gambling and betting operators
- Meta · Cannabis dispensariesMeta Ads conversion tracking for cannabis dispensaries
Free · 30 min
Get Meta reporting what marketplace sellers actually earn
WhatsAppFree30 minutesNo obligation
