Nextdoor Conversions API (CAPI)

Datafly Signal delivers conversion events to Nextdoor server-to-server using the Conversions API. This provides enhanced local advertising attribution and privacy-safe campaign measurement without relying on client-side tracking.

Prerequisites

Before configuring Nextdoor CAPI in Signal, you need a Nextdoor Business account with the Conversions API enabled, a conversion event configured, and an API access token.

Create a Nextdoor Business Account

Go to business.nextdoor.com and click Create Account.
Enter your business details and verify your email address.
Complete the onboarding wizard to set up your business profile.

Enable the Conversions API

In Nextdoor Ads Manager, navigate to Events in the left sidebar.
Click Set Up Conversions API (or contact your Nextdoor account representative to enable CAPI access).
Review and accept the Conversions API terms.

The Conversions API is a server-to-server integration. Unlike the pixel-based integration, no client-side snippet is required. Signal sends events directly from your infrastructure to Nextdoor’s servers.

Configure a Conversion Event

In Nextdoor Ads Manager, go to Events > Conversions.
Click Create Conversion to define a new conversion event.
Name the conversion (e.g. “Website Purchase”), select the conversion type, and configure attribution settings.
Note the Conversion ID — you will need this for Signal configuration.

Generate an API Access Token

In Nextdoor Ads Manager, go to Account Settings > API Access.
Click Generate Token and ensure the token has conversion write permissions.
Copy the access token immediately — it may only be shown once.
Note your Advertiser ID from the Account Settings page.

⚠️

Store the access token securely. If you lose it, you will need to generate a new one. Ensure the token has conversion write permissions — a read-only token will not work.

Configure in Signal

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

Configuration Fields

Field	Required	Description
`advertiser_id`	Yes	Your Nextdoor advertiser ID. Found in Nextdoor Ads Manager under Account Settings.
`access_token`	Yes	CAPI access token with conversion write permissions. Generated in Nextdoor Ads Manager under API Access.
`conversion_id`	Yes	The conversion event ID configured in Nextdoor Ads Manager under Events > Conversions.

Management UI Setup

Go to Integrations > Add Integration > Nextdoor CAPI.
Enter your advertiser_id, access_token, and conversion_id.
Select consent categories (typically advertising).
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_capi",
    "name": "Nextdoor CAPI Production",
    "enabled": true,
    "config": {
      "advertiser_id": "nd-adv-12345",
      "access_token": "ndat_abc123...",
      "conversion_id": "nd-conv-98765"
    },
    "consent_categories": ["advertising"]
  }'

Event Mapping

Datafly Event	Nextdoor CAPI Event	Notes
`page` (page view)	`PageView`	Sent for every page view
`Order Completed`	`Purchase`	Requires `value`, `currency`
`Product Added`	`AddToCart`	Includes product details
`Checkout Started`	`InitiateCheckout`	Includes `value`, `currency`
`Product Viewed`	`ViewContent`	Includes content identifiers
`Lead Generated`	`Lead`	Lead form submission
`Signed Up`	`CompleteRegistration`	User registration
Custom events	Passed through	Sent as custom event name

Identity Signals

The Conversions API relies on identity signals to match server events to Nextdoor user profiles. The more signals you provide, the better the match rate.

Automatic Signals

These are sent automatically by Signal — no configuration needed:

Signal	Description
IP address	Visitor’s IP address, forwarded from the original request.
User agent	Visitor’s User-Agent string, forwarded from the original request.
External ID	Set to the Datafly `anonymous_id` (hashed).

User-Provided Signals

When a user is identified via _df.identify(), additional signals can be sent to improve match quality:

Signal	Description
Email (hashed)	User’s email address, SHA-256 hashed before sending.
Phone (hashed)	User’s phone number, SHA-256 hashed before sending.

All PII hashing is performed server-side by the Delivery Worker before the data leaves your infrastructure. Raw PII is never sent to Nextdoor.

Testing Your Integration

Step 1: Send a Test Event

Trigger a conversion event on your website (e.g. a purchase or lead form submission).
Check the Signal event debugger in the Management UI to confirm the event was captured and delivered.

Step 2: Verify in Nextdoor Ads Manager

In Nextdoor Ads Manager, go to Events > Conversions.
Click on your conversion event to view received events.
Events should appear within a few minutes of delivery.

Step 3: Validate Match Quality

Review the match rate reported in the Conversions dashboard.
If the match rate is low, add user identity signals via _df.identify() when users log in or submit forms.

Troubleshooting

Problem	Solution
Events not appearing in Nextdoor	Verify the `advertiser_id`, `access_token`, and `conversion_id` are correct. Ensure the token has conversion write permissions.
`Permission denied` errors	The access token lacks conversion write permissions. Regenerate with the correct permissions.
Low match rate	Add user identity signals (email, phone) via `_df.identify()`. Ensure IP address and user agent are being forwarded.
Events delayed	Nextdoor CAPI may take up to 15 minutes to reflect server-side events. Allow time before investigating further.
`Invalid conversion_id` error	Verify the conversion event exists and is active in Nextdoor Ads Manager under Events > Conversions.

Visit Nextdoor CAPI documentation for full API documentation and credential setup instructions.

Nextdoor Perion