DocumentationExperience PlatformTags

Nextdoor Conversion API Extension - User Guide

Last update: Thu Feb 05 2026 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

  • Developer

Overview

Nextdoor is a social networking service for neighborhoods that connects people to their local communities. It’s a platform where neighbors can communicate, share information, stay updated on local events and news, and buy and sell items with others in their area.

Use the Nextdoor Conversion API Extension to send conversion events directly to Nextdoor’s Conversion API. This extension helps you track and measure the performance of your Nextdoor advertising campaigns by sending server-side conversion data.

This guide shows you how to install, configure, and use the Nextdoor Conversion API extension in your event forwarding rules.

Prerequisites prerequisites

You need a valid Nextdoor Ads Manager account to use this extension. If you don’t have one already, go to the Nextdoor Ads registration page to register and create your account.

Gather required configuration details configuration-details

To connect Experience Platform to Nextdoor, you’ll need the following information:

Credential
Description
Security Notes
Data Source ID
Your unique data source identifier from Nextdoor, which you can find in your Nextdoor Ads Manager account by accessing the Assets > Pixels page and generating a Nextdoor Pixel.
It is safe to share this within your organization.
Access Token
Your API authentication access token for secure communication. You can generate this token by logging into your Nextdoor Ads Manager account and accessing the API settings.
Keep this token secure, as it provides access to your account.

Install and configure the Nextdoor extension install

To install the extension, select Extensions in the left navigation. In the Catalog tab, select the Nextdoor Conversion API Extension and then select Install.

The extension catalog showing the Nextdoor extension card highlighting install.

On the next screen, enter the configuration values you generated from your Nextdoor Ads Manager:

  • Data Source ID
  • Access Token

When finished, select Save.

Nextdoor configuration screen for the Nextdoor conversion API extension.

Configure an event forwarding rule config-rule

Once all your data elements are set up, you can create event forwarding rules that determine when and how your events are sent to Nextdoor.

Create a new rule in your event forwarding property. Under Actions, add a new action and set the extension to Nextdoor Conversion API Extension. To send Edge Network events to Nextdoor, set the Action Type to Report Web Conversions.

The Report Web Conversions action type being selected for a Nextdoor rule in the Data Collection UI.

After you make this selection, additional controls appear that let you configure the event further, as outlined below. Once completed, select Keep Changes to save the rule.

Main-body parameters

These core parameters define your conversion event:

Parameter
Description
Data Type
Required
Options/Format
Example
Event Name
Specifies the type of conversion event being tracked.
String (dropdown)
Required
  • Purchase
  • Lead
  • Sign Up
  • Add to Cart
  • Initiate Checkout
  • Page View
  • Search
  • View Content
  • Add to Wishlist
  • Subscribe
  • Custom Conversion 1-10
Purchase
Event ID
Unique identifier to prevent duplicate event reporting. This will be auto-generated if blank.
String
Optional
Unique string identifier
order_12345
Event Time (Unix Epoch)
Timestamp when the conversion event occurred. Defaults to current time if left blank.
Integer
Optional
Unix timestamp in seconds
1703980800 (Dec 30, 2023)
Action Source
Channel or platform where the conversion occurred.
String (dropdown)
Required
  • website
  • email
  • app
  • phone_call
  • chat
  • physical_store
  • system_generated
  • other
website
Data Source ID
Override the global data source ID for specific events. Will inherit from the config if left blank.
String
Optional
Alphanumeric string
12345
Action Source URL
The specific URL where the conversion occurred.
String
Optional
Full URL including protocol
https://example.com/checkout/success

Privacy and compliance parameters

Use these parameters to ensure privacy compliance:

Parameter
Description
Data Type
Required
Values/Format
Example
Restricted Data Usage
Flag to restrict data usage for privacy compliance.
Integer
Optional
  • 0 = No restrictions
  • 1 = Restrict
0
Restricted Data Usage (Country)
Country-specific data processing restrictions.
Integer
Optional
1 = USA (other codes may be supported)
1
Restricted Data Usage (State)
State-specific restrictions for US users.
Integer
Optional
1000 = CA, 1001 = CO, etc.
1000
Test Event
Marks the event as a test for development/debugging.
String
Optional
Any non-empty string
test

Customer information parameters

IMPORTANT
You must provide at least one customer information parameter for proper event attribution and matching.
Parameter
Description
Data Type
Required
Format
Example
Email
Customer’s email address for identity matching.
String
At least one customer field required
Plain text or SHA-256 hash
user@example.com
Phone Number
Customer’s phone number for identity matching.
String
At least one customer field required
E.164 format (hashed with SHA-256)
+15551234567
First Name
Customer’s first name for enhanced matching.
String
At least one customer field required
Plain text or SHA-256 hash
John
Last Name
Customer’s last name for enhanced matching.
String
At least one customer field required
Plain text or SHA-256 hash
Smith
Date of Birth
Customer’s birth date for demographic matching.
String
Optional
YYYYMMDD (SHA-256 hashed)
19900115
Gender
Customer’s gender for demographic targeting.
String
Optional
M/F/O (SHA-256 hashed)
M
External ID
Your internal customer identifier.
String
Optional
Any unique string
customer_12345
Street Address
Customer’s street address.
String
Optional
SHA-256 hashed
123 Main Street (hashed)
City
Customer’s city.
String
Optional
SHA-256 hashed
San Francisco (hashed)
State
Customer’s state/province.
String
Optional
Two-letter code (SHA-256 hashed)
CA (hashed)
Zip Code
Customer’s postal code.
String
Optional
First 5 digits US (SHA-256 hashed)
94102 (hashed)
Country
Customer’s country.
String
Optional
ISO-3166-1 alpha-2 (SHA-256 hashed)
US (hashed)
Click ID
Nextdoor click identifier for attribution.
String
Optional
Captured from ndclid URL parameter
nd_click_12345abcdef
Client IP Address
IP address of the user’s device.
String
Optional
IPv4 or IPv6 address
192.168.1.1
Client User Agent
Browser user agent string.
String
Optional
Raw browser user-agent string
Mozilla/5.0 (Windows...)

Custom parameters

These parameters provide additional context about your conversion event:

Parameter
Description
Data Type
Required
Format
Example
Order Value
Total value of the purchase transaction.
String
REQUIRED for Purchase events
ISO 4217 Currency + Amount (no spaces)
USD123.45
Order ID
Unique transaction or order identifier.
String
Optional
Any unique string
order_12345
Delivery Category
Method of product/service delivery.
String
Optional
  • in_store
  • curbside
  • home_delivery
home_delivery
Product Context
Detailed information about purchased products.
String (JSON array)
Optional
JSON array of product objects
[{"id":"SKU123","content_name":"Widget","item_price":29.99,"quantity":1}]

Mobile app parameters

You must include these parameters when Action Source = 'APP':

Parameter
Description
Data Type
Required
Format
Example
App ID*
Mobile application identifier.
String
REQUIRED for APP events
  • Bundle ID (iOS)
  • Package Name (Android)
com.company.app
App Tracking Enabled
iOS App Tracking Transparency consent status.
String
REQUIRED for APP events
Boolean string
true
Platform
Mobile operating system.
String
REQUIRED for APP events
  • iOS
  • Android
Android
App Version
Version of the mobile application.
String
REQUIRED for APP events
Version string as defined by your app
2.0.0-beta

Event types event-types

The following event types are supported for different conversion scenarios:

Event Name
Event Type
Description
Use Case
Required Fields
Notes
Purchase
Standard
Completed purchase transaction.
E-commerce conversions
  • Event Name
  • Order Value
  • Customer Info
Most important for ROAS optimization
Lead
Standard
Lead generation or inquiry.
Form submissions, contact requests
  • Event Name
  • Customer Info
High-value conversion for B2B
Sign Up
Standard
User registration or account creation.
Newsletter signup, account registration
  • Event Name
  • Customer Info
Top-funnel conversion tracking
Add to Cart
Standard
Product added to shopping cart.
E-commerce funnel tracking
  • Event Name
  • Customer Info
Mid-funnel engagement signal
Initiate Checkout
Standard
Checkout process started.
Purchase intent tracking
  • Event Name
  • Customer Info
Strong purchase intent indicator
Page View
Standard
Important page visited.
Content engagement, landing pages
  • Event Name
  • Customer Info
Use for high-value pages only
Search
Standard
Search performed on site.
Product/content discovery
  • Event Name
  • Customer Info
Indicates active user engagement
View Content
Standard
Content or product viewed.
Product page views, content engagement
  • Event Name
  • Customer Info
Useful for remarketing audiences
Add to Wishlist
Standard
Product added to wishlist.
Future purchase intent
  • Event Name
  • Customer Info
Indicates strong product interest
Subscribe
Standard
Subscription to service/newsletter.
Recurring revenue, engagement
  • Event Name
  • Customer Info
High lifetime value indicator
Custom Conversion 1 - 10
Custom
Business-specific conversion event.
Define your own conversion type
  • Event Name
  • Customer Info
Customize for unique business actions

Data elements integration data-element

All fields support Adobe event forwarding data elements. Select the data element icon data elements next to any field to:

  • Select Existing Data Elements: Select from data elements that have already been created.
  • Add New Data Elements: Create and define new data elements as needed.
  • Apply Dynamic Values: Populate fields with dynamic content sourced from your website.

Best practices best-practices

Follow these best practices to ensure accurate conversion tracking, improve data quality, and comply with privacy regulations. These recommendations will help you maximize the effectiveness of your Nextdoor Conversion API integration and optimize your advertising performance.

Data Quality and Privacy Compliance

Proper data handling is essential for maximizing conversion attribution accuracy while maintaining user privacy and regulatory compliance. These practices help ensure your customer data is formatted correctly, processed securely, and handled according to privacy regulations.

  • Use consistent data formatting: Format emails, phone numbers, and other data consistently:

    • Email normalization: Convert emails to lowercase, trim whitespace, and remove dots from Gmail addresses.
    • Phone number standardization: Use E.164 format (+1234567890) for international compatibility.
    • Address normalization: Standardize street abbreviations (St., Ave., Rd.), and remove any extra spaces.
    • Name formatting: Convert names to lowercase, remove extra spaces, and handle special characters consistently.

  • Hash sensitive data: Consider hashing sensitive customer data before sending it. Always normalize your data before hashing to ensure consistent hash values:

    • Use SHA-256 hashing for phone numbers, addresses, and other PII.
    • The extension automatically hashes plain text emails - you can send either format.
    • Hash data consistently across all your tracking implementations.
      • Example: Normalize “John@Example.COM” → “john@example.com” before hashing.

  • Provide complete information: Include as much customer information as possible for better matching:

    • Include multiple identifiers (email + phone, or email + name + address) when available.
    • Use external customer IDs to link conversion events to your CRM data.
    • Provide demographic data (age, gender) when available and compliant with privacy laws.

  • Consent Management: Ensure you have proper consent for data collection:

    • Implement proper consent mechanisms before collecting customer data.

    • Respect user opt-out preferences and data deletion requests.

    • Use the Restricted Data Usage parameters for users who have opted out.

    • Resources:

  • Data Minimization: Only send necessary data for conversion tracking:

    • Only collect and send data that’s essential for attribution and optimization.
    • Regularly review and audit the data fields you’re sending.
    • Remove unnecessary customer information to reduce privacy risk.

  • Use accurate timestamps: Ensure event timestamps are accurate for proper attribution.

    • Use the actual time when the conversion occurred, not when you processed the data.
    • Ensure timestamps are in Unix epoch format (seconds since January 1, 1970).
    • Account for timezone differences in your timestamp calculations.

Event Deduplication

Prevent duplicate conversion events to ensure accurate campaign measurement and avoid inflated performance metrics. Implement proper deduplication so that each conversion is counted only once, providing reliable data for your optimization decisions.

  • Provide unique event IDs: Always use unique event IDs to prevent duplicate conversions.
  • Use consistent naming: Apply consistent event naming across your implementation.

Rate Limiting

The Nextdoor Conversion API is subject to rate limiting. The current rate limit is 100 requests/minute per advertiser. If you surpass the rate limit, the API will return an HTTP 429 Too Many Requests error code.

Conclusion conclusion

The Nextdoor Conversion API Extension provides a powerful way to track conversions and measure the effectiveness of your Nextdoor advertising campaigns. By following this guide and implementing the best practices, you can ensure accurate conversion tracking and optimize your advertising performance.

For the most up-to-date information and additional resources, visit Nextdoor Ads Manager.

Next steps next-steps

This guide showed you how to send server-side event data to Nextdoor using the Nextdoor Conversion API extension. To learn more about event forwarding capabilities in Adobe Experience Platform, see the event forwarding overview.

recommendation-more-help
12b4e4a9-5028-4d88-8ce6-64a580811743