Nextdoor 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 Nextdoor Ads adds on top of that is a mechanical requirement: the ndclid click identifier has to reach the record that holds the money, because Nextdoor 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 Nextdoor specifically needs to accept it.
Free30 minutesNo obligation
Specific to Nextdoor × Marketplaces
Nextdoor for marketplace sellers: only a fit for local makers
Nextdoor cannot attribute orders placed on Amazon, Etsy or Walmart, because ndclid never reaches the marketplace order. Most marketplace sellers ship nationally and have no reason to buy hyperlocal ads; a local maker who also sells in person can test it with a neighborhood-specific code and Etsy's order data, and skip the Conversions API entirely.
Nextdoor sells reach by neighborhood, and a seller shipping nationwide from Amazon or Walmart gains nothing from that targeting. The cost per reached buyer runs higher than on a broad channel, and the handful of resulting marketplace orders cannot be identified, so there is no build worth commissioning.
The fit improves for local makers: a candle maker, baker, woodworker or jeweler who sells on Etsy and at weekend markets, whose neighbors would happily pick up in person. For them the useful outcomes are local pickups, market visits and Etsy orders from nearby, none of which an ad platform sees. A code used only in the Nextdoor ad, redeemed on Etsy or at the stall, is the measurement.
Etsy orders include the buyer's shipping address, so a maker running Nextdoor ads in a few zip codes can compare orders to those zip codes during the campaign with the weeks before. A mention in a local thread produces the same pattern with no ad involved, so note any such posts when reading the comparison rather than crediting all of the lift to the campaign.
Nextdoor · Marketplaces · what breaks
Why Nextdoor 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
The ndclid click identifier never reaches the record
Nextdoor appends ndclid to your landing page URL and the pixel stores it for later events. One parameter, simpler than Google's three. The complication is not the identifier, it is the audience: Nextdoor traffic is hyperlocal and low volume by design, so a single neighbourhood's worth of clicks can be a handful a week — small enough that losing a few identifiers to a redirect or a slow page materially changes the picture.
Nextdoor · Marketplaces · the fix
What working looks like — Nextdoor · 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.
Nextdoor · Marketplaces · architecture
How Nextdoor 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
Nextdoor Ads needs a click to match
An event name Nextdoor recognizes, a matching identifier between pixel and server event, a timestamp, hashed customer information, and ndclid where you have it. Read Nextdoor's delivery and match reporting rather than assuming a successful API response means the event was usable.
- 3
The identifier: the ndclid click identifier
Nextdoor appends ndclid to your landing page URL and the pixel stores it for later events. One parameter, simpler than Google's three. The complication is not the identifier, it is the audience: Nextdoor traffic is hyperlocal and low volume by design, so a single neighbourhood's worth of clicks can be a handful a week — small enough that losing a few identifiers to a redirect or a slow page materially changes the picture.
- 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
The standard pairing: the pixel and the Conversions API event must carry the same identifier and event name for the same conversion, or every conversion counts twice. At Nextdoor's volumes a doubling is easy to miss — going from four conversions a week to eight reads as a good week, not as a bug — so test it deliberately rather than waiting for the numbers to look wrong. Nextdoor's attribution windows are configurable and separate click-through from view-through. Confirm which window your reporting uses before comparing it against another platform, and check the accepted event-freshness limit for server events against Nextdoor's current documentation before backfilling anything.
Nextdoor · 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. |
Nextdoor · Marketplaces · diagnose
Diagnostic order — Nextdoor · Marketplaces
- 01
Count records carrying the ndclid click identifier
- 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 event delivery and match reporting in Nextdoor Ads Manager, reconciled against your own booked-job records
Nextdoor's ads sit in a feed next to genuine neighbour recommendations, and for local services those recommendations are the platform's real force. A business that gets recommended in a neighbourhood group will see calls that no ad produced, in exactly the areas it is advertising in — which makes the ad account look better than it is. The other structural issue is volume: a hyperlocal campaign frequently produces too few conversions a month for any automated bidding strategy to learn from, and the honest recommendation at that scale is accurate reporting with manual control.
Nextdoor · Marketplaces · prove
How it gets proven — Nextdoor · 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 event delivery and match reporting in Nextdoor Ads Manager, reconciled against your own booked-job records read directly, not inferred from an upload succeeding.
Nextdoor · Marketplaces · free audit
What we check in the free audit
- Count records carrying the ndclid click identifier
- No click identifier on the order
- Aggregate reporting treated as measured conversions
- Customer data the marketplace will not release
- Read the event delivery and match reporting in Nextdoor Ads Manager, reconciled against your own booked-job records
Checked against
The marketplace's own order and settlement reports, with their aggregation level understood before anything is compared
Free30 minutesNo obligation
Nextdoor · Marketplaces · when not to buy
When you don't need this — Nextdoor · Marketplaces
- If Nextdoor 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 the ndclid click identifier.
- If you are a national ecommerce brand, Nextdoor's hyperlocal inventory is not where your volume is and the Conversions API build will not pay for itself. It earns its keep for local service businesses with a defined service area.
Nextdoor · Marketplaces · what we deliver
What gets built — Nextdoor · 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 Nextdoor Conversions API
Server events posted to Nextdoor's Conversions API, which accepts website, app and offline conversions through one pipeline. The offline path is the one that matters here: Nextdoor's core audience is local service businesses whose conversion is a booked job or a completed visit, not a web purchase, and that event lives in a job system days after the click.
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
Nextdoor · Marketplaces questions, answered
Only if a meaningful share of buyers are local, for pickup or local delivery. For shipping-only shops the hyperlocal targeting buys nothing.
With a code used only in the Nextdoor ad and a comparison of orders to the targeted zip codes before and during the campaign.
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.
Nextdoor appends ndclid to your landing page URL and the pixel stores it for later events. One parameter, simpler than Google's three. The complication is not the identifier, it is the audience: Nextdoor traffic is hyperlocal and low volume by design, so a single neighbourhood's worth of clicks can be a handful a week — small enough that losing a few identifiers to a redirect or a slow page materially changes the picture.
Server events posted to Nextdoor's Conversions API, which accepts website, app and offline conversions through one pipeline. The offline path is the one that matters here: Nextdoor's core audience is local service businesses whose conversion is a booked job or a completed visit, not a web purchase, and that event lives in a job system days after the click.
By reading the event delivery and match reporting in Nextdoor Ads Manager, reconciled against your own booked-job records 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 Nextdoor · Marketplaces
- MarketplacesConversion tracking for marketplace sellers, and what is genuinely impossible
- Google Ads · MarketplacesGoogle Ads conversion tracking for marketplace sellers
- Meta · MarketplacesMeta 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
- Nextdoor · Crypto exchangesNextdoor Ads conversion tracking for crypto exchanges and platforms
- Nextdoor · FirearmsNextdoor Ads conversion tracking for firearms retailers
- Nextdoor · Add to cart → purchaseHow to track add to cart to purchase for Nextdoor Ads
- Nextdoor × Ecommerce OrdersHow to reconcile Nextdoor Ads against your store's order table
- Nextdoor · CannabisNextdoor Ads conversion tracking for cannabis businesses
- Nextdoor · Crypto and tradingNextdoor Ads conversion tracking for crypto and trading platforms
- Nextdoor · Cannabis dispensariesNextdoor Ads conversion tracking for cannabis dispensaries
Free · 30 min
Get Nextdoor reporting what marketplace sellers actually earn
WhatsAppFree30 minutesNo obligation
