Nextdoor Ads

Nextdoor Ads Features

The Ours Nextdoor Ads feature allows you to securely track conversions and other events for Nextdoor Ads in a HIPAA-compliant manner. By routing all events through our server, we ensure that Nextdoor never interacts directly with your clients' browsers. We also allow you to redact and/or hash data before it is sent over to Nextdoor.

With Ours, you can capture meaningful engagement data while safeguarding privacy, helping your Nextdoor Ads account stay compliant and optimized with actionable insights.

Ours automatically captures the Nextdoor click ID (ndclid) from the URL query string and saves it for dispatching future events.

The Nextdoor Conversion API (CAPI) allows Ours to send events directly from our servers to Nextdoor's servers, bypassing the client browser. This server-to-server connection enhances privacy by keeping user information secure and avoiding direct exposure of user data to Nextdoor.

Configuring a Nextdoor destination

To add a destination, click on Destinations from your Ours platform. Click the Add destination button and select Nextdoor as the destination type to add.

Then, copy and paste your Nextdoor Client ID (this is your Advertiser ID from Nextdoor), your Nextdoor API Access Token (usually provided by the Nextdoor support team), and your Nextdoor Pixel ID (your web pixel for deduplication) into the Ours destination configuration tool. After successful configuration, you will see a message that says "Your destination is configured and ready."

Find your Nextdoor Client ID (Advertiser ID)

1. Log in to your Nextdoor Ads Manager account
2. Navigate to the Settings section
3. Look for your Advertiser ID in the account information
4. Copy and paste that Advertiser ID as your Client ID into the Ours destination configuration tool

Find your Nextdoor API Access Token

1. In your Nextdoor Ads Manager account, go to Settings
2. Navigate to the API Access section
3. If you do not have an API Access Token, you will usually need to request one from the Nextdoor support team
4. Copy the API Access Token provided by support
5. Paste that API Access Token into the Ours destination configuration tool

Find your Nextdoor Pixel ID

1. In your Nextdoor Ads Manager account, go to the Web Pixels or Pixel Setup section
2. Locate your Web Pixel ID
3. Copy and paste that Pixel ID into the Ours destination configuration tool for deduplication

---

Limited Data Use (LDU)

Nextdoor calls its version Restricted Data Usage (RDU). When it is set, Nextdoor uses the event for reporting only, not for optimization or targeting. Advertisers typically apply it to people covered by US state privacy laws such as the CCPA.

Three fields in the destination mapping control it:

• Restricted Data Usage: set to true or 1 and the event is reporting-only at Nextdoor. Map it to the opt-out signal you already collect, such as a consent choice or a Global Privacy Control signal.
• Restricted Data Usage Country and Restricted Data Usage State: the location you want associated with the restriction.

Setting the flag restricts what Nextdoor may do with the event; it does not stop the event from being sent. To withhold events entirely, use Global Data Governance rules or your consent configuration.

See Limited Data Use for every destination that supports a flag like this and what each platform calls it.