Introduction
Nextdoor is a neighborhood-focused social network where local businesses and national brands run advertising campaigns. Merchants advertising on Nextdoor can use UltraCart's built-in integration to report StoreFront conversions back to Nextdoor through the Nextdoor Conversion API, a server-to-server method of sending conversion events.
This integration is server-side only. UltraCart sends events directly from its servers to Nextdoor using your Conversion API access token, so there is no browser tag to install. A client-side Nextdoor Pixel may be layered on later. If you already have a Pixel ID, enter it now so the two sources deduplicate cleanly once the pixel is added.
This short tutorial walks you through obtaining your Nextdoor credentials and configuring Nextdoor tracking on your StoreFront.
Nextdoor Configuration
Before configuring UltraCart, gather two values from your Nextdoor advertising account:
- Conversion API access token (required): a secret token that authorizes UltraCart to send events on your behalf. In Nextdoor Ads Manager, go to Business Settings, then Ads API, then Generate token.
- Pixel ID (optional): your Nextdoor Pixel ID. It is used to deduplicate server-side events against browser pixel events.
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.
StoreFront Configuration
Once you have your access token, configure it in UltraCart:
-
Go to
Main Menu -> StoreFronts -> [Your StoreFront] -> Conversion Tracking -> Other. -
Scroll to the Nextdoor section.
-
Fill in the fields:
-
Access Token (input, required): paste your Nextdoor Conversion API token. This value activates the integration; clearing it turns Nextdoor tracking off.
-
Pixel ID (input, optional): paste your Nextdoor Pixel ID. Leave it blank if you do not have one yet.
-
-
Click Save.
Once the access token is saved, UltraCart begins sending server-side conversion events to Nextdoor for storefront activity.
Tracked Events
UltraCart reports the following StoreFront funnel actions to Nextdoor using the Conversion API standard event names:
| StoreFront action | Nextdoor event |
|---|---|
| Page view | page_view |
| Site search | search |
| Product or category view | view_content |
| Add to cart | add_to_cart |
| Registration or signup | sign_up |
| Begin checkout | initiate_checkout |
| Purchase (receipt page) | purchase |
The purchase event carries the order id, order value, currency, and line items. Each event also carries a stable event id (for example, purchase:<orderId> for purchases) that Nextdoor uses to deduplicate the server-side event against the browser pixel event once a client-side pixel is in place.
Monitoring
Events are delivered to Nextdoor asynchronously 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, run a test order through your checkout and then check your Nextdoor Ads Manager (Events Manager) for the corresponding conversion activity.
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.