Nextdoor Conversion API
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.
Automatic hashing: information is automatically hashed matching partner specifications.
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.
Destination setup
Configuration
Advertiser Id
Required
Your NAM advertiser identifier in Nextdoor Ads Manager. More details are available by following this LINK (See client_id
).
Access Token
Required
Your access token identifier as generated by accessing Nextdoor Ads Manager. More details are available by following this LINK.
Event Mapping
Change the standard mapping between Nextdoor's events and yours or add new mappings. Nextdoor event names must be one of the following: conversion
, lead
, purchase
, sign_up
and custom_conversion_X
, where X
is a number from 1 to 10.
Quick reference
purchase
purchase
generate_lead
lead
sign_up
sign_up
[Any Event]
[Any Allowed Event]
[1]
Field Mappings
Advertiser Id
client_id
(event_name
)
event_name
[1]
context.event_id
event_id
context.event_timestamp
event_time
[2]
partners.nextdoor.event_timezone
event_timezone
partners.nextdoor.action_source
action_source
[3]
context.page.url
action_source_url
partners.nextdoor.delivery_optimization
delivery_optimization
partners.nextdoor.test_event
test_event
user.email
email
[4][5][6]
user.phone
phone_number
[4][6][7]
user.firstname
first_name
[4][5][6]
user.lastname
last_name
[4][5][6]
user.birthdate
date_of_birth
[4][6][8]
user.street
street_address
[4][6]
user.city
city
[4][6][9]
user.state_short
state
[4][6][10]
user.zipcode
zip_code
[4][6][11]
user.country
country
[4][6][12]
context.device.ip
client_ip_address
[4]
partners.nextdoor.pixel_id
pixel_id
[4][13]
partners.nextdoor.click_id
click_id
[4][14]
id
order_id
[15]
currency
+ value
order_value
[15]
partners.nextdoor.delivery_category
delivery_category
[15]
items.X.id
id
[16]
items.X.product.name
content_name
[16]
items.X.product.price
item_price
[16]
items.X.quantity
quantity
[16]
context.app.namespace
app_id
[17]
context.device.ad_tracking_enabled
app_tracking_enabled
[17]
context.device.os.name
platform
[17]
context.app.version
app_version
[17]
Last updated
Was this helpful?