Skip to main content
Nextdoor × SubscriptionsRun this yourself

How to reconcile Nextdoor Ads against your billing system

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 billing system 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 × Subscriptions

Nextdoor vs new subscriptions: local service plans only

Store ndclid at signup and send the first plan payment through Nextdoor's Conversions API as an offline event, then compare against a closed quarter of new service plans. Use click-through only. Expect thin volume and a loose fit; Nextdoor reading higher usually means neighbor recommendations or view-through are inflating its count.

Nextdoor fits recurring local services: lawn care plans, pest control contracts, cleaning schedules, gym memberships. For national software or consumer subscriptions it is a poor fit and not worth reconciling. Where it fits, the billing record often lives in field-service or membership software rather than Stripe, and the first charge happens after an on-site estimate. Capture ndclid on landing, store it with the lead, and make sure it is copied onto the plan when the office creates it.

Nextdoor separates click-through from view-through and both windows are configurable, so restrict the comparison to click-through before anything else. Because the first plan payment can come days after the click, check the event-freshness limit for offline events in Nextdoor's current documentation before backfilling from billing.

Monthly volume is usually too small for one month to mean much; compare a quarter. A Nextdoor figure close to your new plans from those neighborhoods is fine. A figure well above them typically reflects plans that came from a neighbor recommendation in the same area, which the ad account is happy to claim. The most common breakage is plans created by phone or by a technician on site, with no ndclid ever attached.

Nextdoor × Subscriptions · what breaks

Why Nextdoor and your billing system disagree

  1. 01

    Every renewal firing as a conversion

    The single most common subscription error. A customer who stays two years produces twenty-four payment events, and counting them all inflates the conversion count by exactly your retention rate.

  2. 02

    Trial starts counted as paid conversions

    A free trial costs the user nothing. Optimising toward trials reliably finds people who start trials and never pay.

  3. 03

    Cancellations inside the first period never reversed

    Early churn on discounted offers is high, and the reversal is almost never wired.

  4. 04

    Lifetime value assumed rather than measured

    An industry figure for tenure will either starve a channel that works or overfund one that does not. Your own churn data says something different.

Nextdoor × Subscriptions · the fix

What you get from this — Nextdoor × Subscriptions

  • A number instead of a suspicion

  • The likely cause, narrowed

  • A basis for deciding

Nextdoor × Subscriptions · architecture

What each side is actually counting — Nextdoor × Subscriptions

  1. 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. 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. 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. 4

    What your billing system counts

    First successful payments on new subscriptions, found in Stripe, Chargebee, Recurly, Paddle or whatever charges the card.

  5. 5

    The filter that makes them comparable

    New subscriptions only — exclude renewals, and exclude trials that have not yet converted.

Nextdoor × Subscriptions · events

Reading the gap — Nextdoor × Subscriptions

15%+ platform higherUsually the wrong event entirely — the platform is counting renewals, trials, or subscriptions that cancelled before the first real charge.
20%+ platform lowerUsually structural — the platform is missing subscriptions it produced — usually a signup-to-payment gap longer than the attribution window.

Nextdoor × Subscriptions · diagnose

Diagnostic order — Nextdoor × Subscriptions

  1. 01

    Confirm both numbers cover the same period and channel

  2. 02

    Every renewal firing as a conversion

    The single most common subscription error. A customer who stays two years produces twenty-four payment events, and counting them all inflates the conversion count by exactly your retention rate.

  3. 03

    Trial starts counted as paid conversions

    A free trial costs the user nothing. Optimising toward trials reliably finds people who start trials and never pay.

  4. 04

    Cancellations inside the first period never reversed

    Early churn on discounted offers is high, and the reversal is almost never wired.

  5. 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 × Subscriptions · prove

How to know you did it right — Nextdoor × Subscriptions

Source of truth

your billing system — new subscriptions for a fully closed month

    Nextdoor × Subscriptions · free audit

    What we check in the free audit

    • Confirm both numbers cover the same period and channel
    • Every renewal firing as a conversion
    • Trial starts counted as paid conversions
    • Cancellations inside the first period never reversed
    • Read the event delivery and match reporting in Nextdoor Ads Manager, reconciled against your own booked-job records

    Checked against

    your billing system — new subscriptions for a fully closed month

    Get my free conversion tracking audit

    Free30 minutesNo obligation

    Nextdoor × Subscriptions · when not to buy

    When the answer is that you do not need us — Nextdoor × Subscriptions

    • If almost all of your new subscriptions 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 × Subscriptions · what we deliver

    The method, step by step — Nextdoor × Subscriptions

    • Pull what Nextdoor reports

      The event delivery and match reporting in nextdoor ads manager, reconciled against your own booked-job records.

    • Pull what your billing system shows

      Export subscriptions by creation date for a closed month, filtered to those that took a first successful payment, and record the plan value.

    • Filter both to the same thing

      New subscriptions only — exclude renewals, and exclude trials that have not yet converted.

    • Compare per record, not on totals

    FAQ

    Nextdoor × Subscriptions questions, answered

    Ask how the customer heard about you and record it at creation. Without an ndclid or a tracked call number, that plan cannot be tied to a Nextdoor click.

    Free · 30 min

    Found a gap between Nextdoor and your billing system?

    Free30 minutesNo obligation