Nextdoor Conversion API
This destination is currently under final review and will be available soon.
Nextdoor operates a hyperlocal social networking service for neighborhoods. Using this destination you can send marketing data in the form of events or conversions to Nextdoor and get a more complete picture of their advertising outcomes on Nextdoor. This is based on Nextdoor Conversion API.
Key features
The Nextdoor Conversion API destination provides the following key features:
Events structure: our Events reference matches Nextdoor events, meaning that your data is properly bridged to the expected fields in an optimized way.
Prebuilt mappings: data mapping for event-based destinations happens automatically, which simplifies user inputs.
Smart mapping: data mapping can be readjusted using your datalayer defined fields.
Event mapping: change standard mapping between Nextdoor events and yours or add new mappings.
Support for multi-item data: information included in the item array is dispatched to Nextdoor.
Automatic hashing: information is automatically hashed matching Nextdoor specifications.
Destination setup
Before configuring this destination, you need access to Nextdoor Ads Manager.
Configuration
Settings | Description |
---|---|
|
|
|
|
| Change the standard mapping between Nextdoor's events and yours or add new mappings. Nextdoor event names must be one of the following: |
Quick reference
Commanders Act Events | Nextdoor Events |
---|---|
|
|
|
|
|
|
|
|
[1] See Event Mapping
in Configuration for more details.
Field Mappings
Most properties can be remapped using our "Smart Mapping" feature.
Commanders Act Properties | Nextdoor Properties |
---|---|
|
|
( |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
[1] See Event Mapping
in Configuration for more details.
[2] Automatically converted in ISO 8601 format.
[3] When Smart Mapping Action Source is not set, this value is automatically set by using the following information in the presented priority order: 1. Smart Mapping field Experience Type
2. property context.app
3. Smart Mapping field Conversion Type
.
[4] Set in customer
object.
[5] Pre-hashed format in lower case.
[6] Automatically hashed via SHA256 when provided in clear text.
[7] Pre-hashed format should consist of exactly ten digits, devoid of any special characters or international country codes.
[8] Pre-hashed format YYYYMMDD
.
[9] Pre-hashed format in lower case, no special characters.
[10] Pre-hashed format in lowercase and as two letter ANSI abbreviation code.
[11] Pre-hashed format with five digits for US.
[12] Pre-hashed format as two-character ISO 3166-1 alpha-2 code.
[13] Allows Nextdoor to deduplicate events for an advertiser that sends events via both the CAPI and the pixel making it soft required for multiple pixel implementation.
[14] This is the same as ndclid
parameter attached to clickthrough URL.
[15] Set in custom
.
[16] Set in custom.product_context.X
.
[17] Set in app
.
Last updated