How to track application to enrollment for Nextdoor Ads

Architecture

The exact event sequence

Five stages. The break in this funnel is a calendar, not a bug. The gap between the click and the enrollment routinely exceeds every ad platform's import window, so the design decision is which earlier stage is defensible as a bidding target — and saying plainly that the enrollment itself cannot reach the algorithm. The identifier has to survive all of them.

1. Step 1

   Inquiry

   Volume signal. Prospects inquire widely and it predicts very little.

2. Step 2

   Information session or tour attended

   A real time commitment and a much better predictor than the inquiry.

3. Step 3

   Application submitted

   The realistic optimization target, because it is recent enough to upload and correlated enough to bid on.

4. Step 4

   Offer accepted

   The commitment, usually with a deposit.

5. Step 5

   Enrolled and attending

   The revenue, valued at tuition times your own average length of attendance.

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 application and enrollment records in your admissions or student system after a full real journey through every step.
• Enrolled and attending 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 admissions system's applications by submission date and enrollments by start date, across the full cycle 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 you enroll continuously with a short application-to-start gap — most short professional courses — this funnel collapses to something much simpler and the enrollment itself is uploadable.
• 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 enrolled and attending regularly exceeds the import window, the final event can't drive bidding whatever you build. Optimize toward application submitted, valued at your own application-to-enrollment rate instead and use the later data for budget decisions rather than for bidding.
• If almost none of your enrollment records 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.