Nextdoor Tracking
Nextdoor is a neighborhood-focused social network where local businesses and national brands run advertising campaigns. If you advertise on Nextdoor, UltraCart's built-in integration reports your StoreFront conversions back to Nextdoor so you can measure campaign performance and optimize against real purchase activity.
This tutorial walks you through gathering your Nextdoor credentials, configuring tracking on your StoreFront, and confirming that events are arriving.
How UltraCart reports conversions to Nextdoor
UltraCart sends every tracked event to Nextdoor twice, over two independent paths, and Nextdoor merges the pair into a single conversion.
- Nextdoor Universal Pixel: a browser tag UltraCart injects into your StoreFront pages automatically. No code for you to paste.
- Nextdoor Conversion API: a server-to-server feed sent directly from UltraCart's servers, which still reports conversions when a shopper's browser blocks the pixel.
Both paths carry the same event identifier, so Nextdoor recognizes them as one event rather than counting a conversion twice. You do not need to configure anything for this to work. It is handled for you once both credentials are saved.
Before you begin
Gather two values from your Nextdoor advertising account. Both are required. Nextdoor tracking stays off until both are saved.
- Pixel ID: create a Universal Pixel in Nextdoor Ads Manager under Assets → Pixels. The Pixel ID identifies your pixel to both the browser tag and the server-side feed.
- Conversion API access token: in Nextdoor Ads Manager, go to Business Settings → Ads API → Generate token.
You should also turn on auto-tagging in Nextdoor Ads Manager. Auto-tagging appends a click identifier (ndclid) to your ad destination URLs, which is the strongest signal Nextdoor has for matching a purchase back to the ad that drove it. Auto-tagging is not enabled by default.
For more detail, see Nextdoor's documentation:
- Conversion API reference: https://developer.nextdoor.com/reference/conversion-api
- Getting started: https://developer.nextdoor.com/reference/conversion-getting-started
The Conversion API access token is a secret credential. Treat it like a password and do not share it publicly. Nextdoor access tokens also expire annually. See Keeping your access token current.
Configure Nextdoor tracking on your StoreFront
-
Go to
Main Menu -> StoreFronts -> [Your StoreFront] -> Conversion Tracking -> Other. -
Scroll to the Nextdoor section.
-
Fill in both fields:
-
Pixel ID: paste your Nextdoor Pixel ID.
-
Access Token: paste your Nextdoor Conversion API access token.
-
-
Click Save.
Once both values are saved, UltraCart injects the Universal Pixel into your StoreFront pages and begins sending server-side conversion events. Clearing either field turns off the whole integration, including both the pixel and the server-side feed.
Tracked events
UltraCart reports the following StoreFront actions. The pixel and the Conversion API use different spellings for the same event, which is why both columns are listed.
| StoreFront action | Universal Pixel event | Conversion API event |
|---|---|---|
| Page view | PAGE_VIEW | page_view |
| Site search | SEARCH | search |
| Product or category view | VIEW_CONTENT | view_content |
| Add to cart | ADD_TO_CART | add_to_cart |
| Registration or signup | SIGN_UP | sign_up |
| Begin checkout | INITIATE_CHECKOUT | initiate_checkout |
| Purchase (receipt page) | PURCHASE | purchase |
The purchase event carries the order id, order value, currency, and line items.
How click attribution works
When a shopper clicks your Nextdoor ad and auto-tagging is enabled, Nextdoor appends an ndclid click identifier to the destination URL. UltraCart stores that identifier in a first-party cookie the moment the shopper lands, keeps it for 365 days, and attaches it to the conversion events it sends, including the purchase however many days later it happens.
Storing the identifier server-side matters because browsers such as Safari aggressively expire cookies written by JavaScript. Without this step, click attribution would quietly degrade for a large share of your traffic.
If auto-tagging is off in Nextdoor Ads Manager, no ndclid ever reaches your StoreFront. Attribution then falls back to matching on the shopper's hashed email address, which works but matches fewer conversions.
Shopper privacy and consent
Nextdoor tracking respects your StoreFront's privacy settings. Register nextdoor as a marketing service in your theme's privacy configuration, and UltraCart will hold back both the pixel and the server-side events until a shopper grants marketing consent.
The customer information UltraCart sends for matching (email address and phone number) is hashed before it leaves UltraCart's servers. Plain-text customer details are never placed on the page or sent to Nextdoor.
If a shopper asks you to delete their data from Nextdoor, submit that request through Nextdoor's own privacy process. UltraCart does not have a Nextdoor-facing deletion endpoint to call on your behalf.
Keeping your access token current
Nextdoor access tokens expire one year after they are generated, and Nextdoor does not provide a renewal flow. You generate a fresh token and paste it into UltraCart. UltraCart does not currently email you a reminder before a token expires.
When a token expires, tracking stops silently: your StoreFront looks completely normal and no error is shown to shoppers. The two symptoms to watch for are conversions disappearing from Nextdoor Ads Manager, and authorization failures appearing in your integration logs. Setting your own calendar reminder for eleven months out is the simplest way to avoid a gap.
Verifying that events are arriving
Server-side events are delivered by a background process, so allow a short delay between a StoreFront action and the event appearing on Nextdoor's side.
To confirm data is flowing:
-
Place a test order through your StoreFront checkout.
-
Open Nextdoor Ads Manager and check Events Manager for the corresponding conversion activity. The purchase should appear once, not twice. Seeing it once confirms the pixel and server-side events are pairing correctly.
-
Review the purchase event in Integration Logs, which records the request UltraCart sent and Nextdoor's response. Purchase events are logged here; other funnel events are not.
If you have configured a Custom Thank You Page URL, the standard UltraCart receipt screen is bypassed. The purchase event is generated from the receipt flow, so a custom thank-you page can prevent the purchase event from firing.
Availability outside the United States
Nextdoor's advertising footprint is primarily the United States, along with the United Kingdom, Australia, Canada, Germany, France, and the Netherlands. If your customer base sits outside those countries, Nextdoor is unlikely to be a productive advertising channel regardless of how the integration is configured.
Related documentation
- Pinterest Tracking - server-to-server conversion tracking for Pinterest
- TikTok Tracking - server-to-server conversion tracking for TikTok
- Integration Log Health Report - reviewing integration requests and responses