Nextdoor

info

This is a pro feature. Get the pro version here

Nextdoor is the neighborhood advertising platform. Its Universal Pixel tracks the standardized conversion events Nextdoor uses for attribution and campaign optimization. Once a pixel ID is configured, the Pixel Manager loads the Nextdoor Universal Pixel and sends all conversion events automatically.

Setup

1. Open the Nextdoor Ads Manager: https://ads.nextdoor.com/

2. Browse to Assets > Pixels and create a pixel if you don't have one yet

3. Copy the Pixel ID. It is a UUID that looks similar to this: 550e8400-e29b-41d4-a716-446655440000

4. In the Pixel Manager, open Tracking Pixels → Nextdoor, paste the ID into the Pixel ID field, and save.

That's it. There is no need to manually add the Nextdoor base code snippet or event snippets to your site. The Pixel Manager loads the Universal Pixel and sends the events automatically.

Conversion API (CAPI)

The Conversion API is an optional addition to your Nextdoor pixel that sends conversion data to Nextdoor in real time through Nextdoor's server-to-server protocol. This provides more accurate conversion tracking, especially for events that might be missed by browser-based tracking due to ad blockers or privacy settings. Purchases are triggered directly by WooCommerce order events, so they are tracked even when the customer never returns to the order confirmation page.

The Pixel Manager sends every event with a shared event ID to both the browser pixel and the Conversion API, so Nextdoor automatically deduplicates the two channels. The Nextdoor click ID (ndclid) is captured on the landing page and attached to the server-side events for attribution.

Find more information on the Conversion API in the Nextdoor documentation.

1. Open the Nextdoor Ads Manager: https://ads.nextdoor.com/

2. Open the Ads API settings: https://ads.nextdoor.com/v2/manage/api

3. Click Generate token to create a new access token

4. Copy the generated token

5. In the Pixel Manager, open Tracking Pixels → Nextdoor, paste the token into the Conversion API Token field, and save.

Testing

To test the Conversion API events without polluting your real conversion data, the Pixel Manager offers a settings field where you can enter a test event code. While it is set, all Conversion API events are flagged as test events in Nextdoor.

1. In the Pixel Manager, open Tracking Pixels → Nextdoor, enter a test event code (e.g. TEST1234) into the Conversion API Test Event Code field, and save
2. Verify the events arrive in Nextdoor Ads Manager
3. Remove the test event code after testing

Server-Side Proxy

You can offload Nextdoor Conversion API calls from your WooCommerce server to the edge using the Server-Side Proxy. This reduces server load and improves tracking accuracy by routing events through a first-party subdomain.

Advanced Matching

With advanced matching enabled, the Pixel Manager sends the SHA-256 hashed email address of logged-in customers and purchasers to Nextdoor along with the events. Server-side purchase events additionally carry the hashed phone number, name, and location fields. This improves Nextdoor's ability to match visitors, which increases match rates and attribution accuracy.

All personal data is hashed before it leaves your server. Nextdoor receives only the hashes, never the plain values.

You can enable advanced matching in the Nextdoor advanced settings section of the Pixel Manager.

Supported Events

The Pixel Manager sends these Nextdoor events:

• PAGE_VIEW: sent on every page, the basis for Nextdoor's conversion event configuration.
• VIEW_CONTENT: sent on product detail pages, with the product details.
• ADD_TO_CART: sent when a product is added to the cart, with the product details, price, and quantity.
• INITIATE_CHECKOUT: sent when the checkout is started, with the cart value and items.
• SEARCH: sent on search result pages.
• PURCHASE: sent when an order is placed, with the order ID, order value, and all purchased items.

Here's a list of supported events.

note

Nextdoor matches the product IDs in the tracking events against your product catalog in Nextdoor. Make sure the product identifier setting in the Pixel Manager matches the IDs in the catalog you submitted to Nextdoor.