How to track checkout to purchase for Nextdoor Ads

Architecture

The exact event sequence

Five stages. Stage three is the one you often can't instrument, which is precisely why stage four has to be the source. The identifier has to survive all of them.

1. Step 1

   Checkout started

   Browser-side, with value. The last point you reliably control the page.

2. Step 2

   Payment info submitted

   Worth splitting out — it turns one opaque step into a diagnosable one.

3. Step 3

   Payment authorised

   Often on someone else's domain, and frequently invisible to your tags entirely.

4. Step 4

   Order created

   From the order webhook. This is the only step that sees every order regardless of how payment happened.

5. Step 5

   Purchase sent with the order ID

   Deduplicated on that ID, with refunds wired to reverse.

Diagnostic sequence

What's specific to Nextdoor Ads

The funnel logic above is the same wherever you advertise. These are the parts that change because it's Nextdoor Ads.

1. 1

   Click 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.

2. 2

   Import mechanism: the 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.

3. 3

   Deduplication

   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.

4. 4

   Window and timing

   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.

5. 5

   The Nextdoor gotcha

   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.

Source-of-truth validation

How to prove the chain works

One real journey, followed all the way, then a reconciliation. Neither on its own is enough.

• A live Nextdoor ad clicked, and the identifier confirmed present on the landing URL.
• The same identifier confirmed on the order record in your store after a full real journey through every step.
• Purchase sent with the order ID confirmed arriving at Nextdoor Ads, verified by the event delivery and match reporting in Nextdoor Ads Manager, reconciled against your own booked-job records.
• Your store's order records, web orders only reconciled against Nextdoor Ads per record over a fully closed window.
• The same reconciliation repeated 30 days later.

Straight talk

When this doesn't apply to you

Worth checking before you build anything, because two of these are common and both mean the work isn't worth doing.

• If your checkout is entirely on your own domain with no wallet options and a confirmation page every customer reaches, the browser-side event may genuinely be sufficient — reconcile a closed week and find out before building anything.
• 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.
• If your cycle from click to purchase sent with the order id regularly exceeds the import window, the final event can't drive bidding whatever you build. Optimize toward payment info submitted instead and use the later data for budget decisions rather than for bidding.
• If almost none of your orders carry a click identifier today, that's the whole project. Fix capture first — the import is the easy half and no tooling rescues a record with nothing to reference.