Nextdoor Ads

Datafly Signal delivers conversion events to Nextdoor server-to-server using the Nextdoor Pixel API. This enables local advertising attribution and neighbourhood-level campaign measurement without loading client-side tags.

Why route Nextdoor Ads through Datafly Signal

• Conversions survive ad blockers and tracking prevention. A browser tag served from an advertising domain is blocked outright for part of your traffic, and Safari’s ITP shortens the cookies it can set. Signal sends the event from your own server, so the conversions Nextdoor Ads optimises against are not filtered by the browser.
• Email and phone number are hashed before leaving your infrastructure. Signal normalises (trim and lowercase) and applies SHA-256 inside your own deployment, so Nextdoor Ads receives match keys rather than raw personal data.
• Client IP and user agent are preserved. Server-to-server delivery normally loses both, which weakens matching. Signal forwards the genuine visitor values as request headers so Nextdoor Ads attributes the event to the right session.
• Presets for Retail and Lead Generation. The mapping starts from a working configuration for your vertical instead of a blank field map.
• One consent decision governs every destination. Nextdoor Ads is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.
• No vendor tag on the page. Removing it removes its page weight and its independent access to your visitors.

Prerequisites

Before configuring Nextdoor Ads in Signal, you need a Nextdoor Business account with an active Pixel and an API access token.

Configure in Signal

Now that you have your Advertiser ID, Pixel ID, and access token, configure the integration in Signal.

Configuration Fields

Management UI Setup

1. Go to Integrations > Add Integration > Nextdoor.
2. Enter your advertiser_id, pixel_id, and access_token.
3. Select consent categories (typically advertising).
4. Click Save.

Management API Setup

curl -X POST http://localhost:8084/v1/admin/integrations \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "source_id": "src_abc123",
    "vendor": "nextdoor",
    "name": "Nextdoor Ads Production",
    "enabled": true,
    "config": {
      "advertiser_id": "nd-adv-12345",
      "pixel_id": "nd-px-67890",
      "access_token": "ndat_abc123..."
    },
    "consent_categories": ["advertising"]
  }'

API endpoint

POST https://ads.nextdoor.com/v2/api/conversions/track

Allow egress to ads.nextdoor.com from the network your delivery workers run on.

Event Mapping

The default Retail preset maps:

To customise or extend, edit the integration’s Field Mappings in the Management UI.

Testing Your Integration

Step 1: Send a Test Event

1. Trigger a page view or conversion event on your website.
2. Check the Signal event debugger in the Management UI to confirm the event was captured and delivered.

Step 2: Verify in Nextdoor Ads Manager

1. In Nextdoor Ads Manager, go to Events > your Pixel.
2. You should see events arriving within a few minutes.
3. Click on individual events to inspect the payload.

Step 3: Validate Attribution

1. Create a test campaign targeting a small audience.
2. Confirm that conversion events are attributed correctly in the campaign reports.

Troubleshooting