Nextdoor Conversions API Destination
Beta
This feature is in active development and may change before general availability.
Nextdoor Conversion API allows advertisers to track and send conversion events directly to the platform. This API provides a programmatic way to record and attribute conversions, enabling advertisers to measure the effectiveness of their advertising campaigns.
This destination is maintained by Nextdoor. For any issues with the destination, contact their Support team.
- From your workspace's Destination catalog page search for "Nextdoor".
- Select Nextdoor Conversions API and click Add Destination.
- Select an existing Source to connect to Nextdoor Conversions API.
- Go to the Nextdoor Ads Manager, then find and copy the API key, Nextdoor Advertiser ID and Nextdoor Pixel Id values. If these values are not visible in the Ads Manager, you may need to contact your Nextdoor Account Manager to ensure that your Nextdoor account has been whitelisted for the (Ads API) functionality.
- Enter the API key, Nextdoor Advertiser ID and Nextdoor Pixel Id values in the Nextdoor Conversions API destination settings in Segment.
- In the Mappings tab, configure the Actions to send data to Nextdoor Conversions API.
- Enable the Destination and Actions.
- See Nextdoor's documentation for additional instructions.
The Embed API Key for your account. You can find this on your settings pages.
Your Nextdoor Advertiser ID for self serve clients can be found in your NAM account for managed your support team can provide
Nextdoor Pixel Id. Used for deduplication when events are sent via CAPI and front end Pixel.
Build your own Mappings. Combine supported triggers with the following Nextdoor Conversions API-supported actions:
Mapping limits per destination
Individual destination instances have support a maximum of 50 mappings.
Send Conversion Event to Nextdoor
Send Conversion is a Cloud action.
The name of the event to track
Optional
A unique ID for the event. This is used to deduplicate events sent by the browser and server.
UCT Timestamp with ISO 8601 format. For example, 2022-11-23T03:30:52Z
Indicates the channel through which conversion happened.
Optional
The browser URL where the event happened (required for web events).
True indicates data can be used for optimization. False indicates the data will only be used for attribution
Flag to indicate if this is a test event.
Customer profile data used to match with Nextdoor users. At least one of the fields is required.
Optional
Custom objects contains fields specific to advertisers that are not already covered in standard fields.
Optional
Product details associated with the event.
Optional
Data about the source Mobile app. Required for app events
Enriches Segment payloads the Nextdoor Click ID
Nextdoor Browser Plugin is a Web action. The default Trigger is type = "track" or type = "identify" or type = "page" or type = "group" or type = "alias"
This action does not have any fields.
When the Nextdoor Conversions API destination receives website data from a Segment JavaScript source, the Nextdoor Browser Plugin automatically grabs the Nextdoor click ID / ndclid from the querystirng in the page URL, and passes it to the Send Conversion Action. Supplying the ndclid boosts attribution accuracy and is strongly recommended for website tracking. The plugin is enabled by default as soon as the destination is created.
You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule a demo.
For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property order_completed_last_30days: true. When the user no longer satisfies this condition (for example, it's been more than 30 days since their last order), Engage sets that value to false.
When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.
Real-time to batch destination sync frequency
Real-time audience syncs to Nextdoor Conversions API may take six or more hours for the initial sync to complete. Upon completion, a sync frequency of two to three hours is expected.
Segment lets you change these destination settings from the Segment app without having to touch any code.
The Embed API Key for your account. You can find this on your settings pages.
Your Nextdoor Advertiser ID for self serve clients can be found in your NAM account for managed your support team can provide
Nextdoor Pixel Id. Used for deduplication when events are sent via CAPI and front end Pixel.