How to reconcile Nextdoor Ads against your store's order table
This is the check we run first on every account, written out so you can run it without us. It takes about thirty minutes and needs two numbers: what Nextdoor says it produced, and what your store's order table actually shows. The gap between them is the only honest measure of whether your tracking works — and if it comes back small, you do not need us.
Free30 minutesNo obligation
Specific to Nextdoor × Ecommerce Orders
Nextdoor Ads vs your store orders: a fit only for local sellers
For a national store, Nextdoor drives too few orders to reconcile meaningfully. For a local retailer, save ndclid on each order and send the order ID as the shared event identifier, then list matching orders one by one. At hyperlocal volume, single orders swing any percentage; view-through credit inside your delivery area is the usual surplus.
Nextdoor fits a store with a local delivery or pickup area, not a brand shipping nationwide. Where it fits, the join is ndclid saved against the order plus an event identifier shared between the pixel and the Conversions API. Volume is small enough that you can list every order carrying ndclid for the month and check each against Nextdoor's purchase count by hand, which is more useful here than any ratio.
Nextdoor separates click-through and view-through windows, so check which one your report uses. View-through credit matters more than usual because the audience is your own neighborhood: people who walk past your shop and would have ordered anyway can see an ad and be counted. Neighbor recommendations add orders in the same streets that no ad produced. Check whether the report dates purchases by the ad interaction or by the order.
Pull purchases from Nextdoor Ads Manager and compare click-attributed purchases with your ndclid orders, keeping view-through as a separate figure. Filter out point-of-sale and phone orders, which are common for local sellers and cannot be matched. A difference of one or two orders a month is normal. Purchases reported with no ndclid orders at all usually means view-through credit or a tag firing on a page other than order confirmation.
Nextdoor × Ecommerce Orders · what breaks
Why Nextdoor and your store's order table disagree
- 01
Refunds never subtracted
The most common cause and the easiest to check. Sum refunds for the same period — if the platform figure is roughly your gross and your own figure is net, that difference is the whole gap.
- 02
Purchase event firing on page refresh
A confirmation page that re-fires on reload counts one order several times. Compare distinct order IDs against total conversions.
- 03
Point-of-sale orders in the same table
If you have a physical shop, counter sales sit in the same order table and will be counted as advertising conversions unless the channel is filtered.
- 04
Post-purchase upsells arriving late
If the conversion fires at checkout and an upsell adds revenue afterwards, the platform is under-reporting by the upsell take rate.
Nextdoor × Ecommerce Orders · the fix
What you get from this — Nextdoor × Ecommerce Orders
A number instead of a suspicion
The likely cause, narrowed
A basis for deciding
Nextdoor × Ecommerce Orders · architecture
What each side is actually counting — Nextdoor × Ecommerce Orders
- 1
What Nextdoor counts
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.
- 2
How Nextdoor attributes it
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.
- 3
The window it uses
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.
- 4
What your store's order table counts
Paid orders with their totals, found in Shopify Admin → Orders, WooCommerce → Orders, or a direct query against the orders table.
- 5
The filter that makes them comparable
Financial status is paid, and the sales channel is online rather than point of sale.
Nextdoor × Ecommerce Orders · events
Reading the gap — Nextdoor × Ecommerce Orders
| What you see | What it usually means |
|---|---|
| 15%+ platform higher | Usually the wrong event entirely — the platform is claiming more than you took. usually refunds, duplicate firing, or a second channel bleeding into the same conversion action. |
| 20%+ platform lower | Usually structural — the platform is seeing fewer orders than you actually took. usually consent, ad blocking, or an identifier that never reached the order. |
Nextdoor × Ecommerce Orders · diagnose
Diagnostic order
- 01
Confirm both numbers cover the same period and channel
- 02
Refunds never subtracted
The most common cause and the easiest to check. Sum refunds for the same period — if the platform figure is roughly your gross and your own figure is net, that difference is the whole gap.
- 03
Purchase event firing on page refresh
A confirmation page that re-fires on reload counts one order several times. Compare distinct order IDs against total conversions.
- 04
Point-of-sale orders in the same table
If you have a physical shop, counter sales sit in the same order table and will be counted as advertising conversions unless the channel is filtered.
- 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 × Ecommerce Orders · prove
How to know you did it right — Nextdoor × Ecommerce Orders
Source of truth
your store's order table — orders for a fully closed month
Nextdoor × Ecommerce Orders · free audit
What we check in the free audit
- Confirm both numbers cover the same period and channel
- Refunds never subtracted
- Purchase event firing on page refresh
- Point-of-sale orders in the same table
- Read the event delivery and match reporting in Nextdoor Ads Manager, reconciled against your own booked-job records
Checked against
your store's order table — orders for a fully closed month
Free30 minutesNo obligation
Nextdoor × Ecommerce Orders · when not to buy
When the answer is that you do not need us — Nextdoor × Ecommerce Orders
- If almost all of your orders come from a channel with no click behind it, no tracking work will reach them — and knowing that is worth more than a build.
- 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 × Ecommerce Orders · what we deliver
The method, step by step — Nextdoor × Ecommerce Orders
Pull what Nextdoor reports
The event delivery and match reporting in nextdoor ads manager, reconciled against your own booked-job records.
Pull what your store's order table shows
Export orders for a fully closed calendar month, filtered to paid and online. Count them, and sum the total after discounts and before shipping and tax.
Filter both to the same thing
Financial status is paid, and the sales channel is online rather than point of sale.
Compare per record, not on totals
FAQ
Nextdoor × Ecommerce Orders questions, answered
They are view-through conversions from local residents, many of whom may have ordered anyway. Report them separately from click-attributed orders.
Pool at least a quarter. At a handful of orders a month, one missed or extra order changes the picture more than any tracking fault.
Because you should know the size of the problem before anyone quotes you for it. If the gap is small, you have saved yourself a purchase. If it is large, you now know what you are buying rather than taking our word for it.
No. Both numbers come from systems you already own and neither leaves them. There is no tool to sign up for and nothing to upload.
Then compare totals for a closed period and treat the result as directional rather than exact. The event delivery and match reporting in nextdoor ads manager, reconciled against your own booked-job records is still the right place to read the platform's side.
Under five percent is working. Five to fifteen usually means reversals are missing. Above twenty is normally the wrong event being counted, not a broken tag — which is why debugging tags first wastes so much time.
Then fix the filter before drawing any conclusion. Financial status is paid, and the sales channel is online rather than point of sale. A mismatch in scope produces a gap that looks like a tracking fault and is not one.
Book the free thirty-minute call and bring both numbers. We will tell you which of the causes above it is, and whether it is something you can fix yourself — which it sometimes is.
More on Nextdoor × Ecommerce Orders
- Google Ads × Ecommerce OrdersHow to reconcile Google Ads against your store's order table
- Meta × Ecommerce OrdersHow to reconcile Meta Ads against your store's order table
- TikTok × Ecommerce OrdersHow to reconcile TikTok Ads against your store's order table
RELATED GUIDES
Systems of record beside ecommerce orders, and the funnels it settles
- Nextdoor × Enrolment SystemHow to reconcile Nextdoor Ads against your application or enrolment system
- Nextdoor × Job SystemHow to reconcile Nextdoor Ads against your job management system
- Nextdoor · Quiz → segmented offerHow to track quiz completion to segmented offer for Nextdoor Ads
- Nextdoor · App install → purchaseHow to track app install to in-app purchase for Nextdoor Ads
- Nextdoor · Alcohol and wineNextdoor Ads conversion tracking for alcohol and DTC wine brands
- Nextdoor · FirearmsNextdoor Ads conversion tracking for firearms retailers
- nopCommerce → NextdoorConnecting nopCommerce to Nextdoor Ads
- Rakuten Advertising → NextdoorConnecting Rakuten Advertising to Nextdoor Ads
Free · 30 min
Found a gap between Nextdoor and your store's order table?
WhatsAppFree30 minutesNo obligation
