Elevate your local marketing efforts with Nextdoor Ads and drive business growth by reaching nearby customers in their communities
|Type||Description||Supported Sync Modes|
|Events||Sync data from any source to Nextdoor events||Insert|
For more information about sync modes, refer to the sync modes docs.
Go to the Destinations overview page and click the Add destination button. Select Nextdoor and click Continue. You can then authenticate Hightouch to Nextdoor.
Enter the following required fields into Hightouch:
- API token: Enter a valid API token.
Once you've set up your Nextdoor destination and have a model to pull data from, you can set up your sync configuration to begin syncing data. Go to the Syncs overview page and click the Add sync button to begin. Then, select the relevant model and the Nextdoor destination you want to sync to.
Nextdoor's Conversions API requires the following event parameters:
- at least one
Providing an event name is required to send an event to the Conversions API. You can either provide a static value or select to use a column from your model. Hightouch syncs the static or column value as the
event_name parameter the Conversions API requires.
Supported values include:
You can optionally select a column that contains timestamps of when events occurred. If this field is empty, Hightouch uses the time the event arrives at the server. Hightouch syncs the timestamp as the
event_time parameter the Conversions API requires.
If you select a column, it should be in ISO 8601 format. Hightouch automatically converts the data to the format Nextdoor expects.
action_source is a required parameter and indicates the channel through which conversion happened, for example, over email, on your website, etc. Knowing where your events took place helps ensure your ads go to the right people.
client_id is a required parameter, also known as the NAM Advertiser ID. To get your
client_id, reach out to your Nextdoor account manager.
Test event codes are special codes you can include in your event payload to simulate conversion events. This allows you to test your API implementation without actually recording real conversion data.
You can optionally enter a test event code as part of your sync configuration.
Make sure to remove the test event code if you're running a production sync.
By default, Hightouch automatically hashes the following customer fields:
If you want to turn hashing off, select No under Would you like Hightouch to automatically detect if your PII data requires hashing?.
To date, our customers haven't experienced any errors while using this destination. If you run into any issues, please don't hesitate to . We're here to help.
Hightouch provides complete visibility into the API calls made during each of your sync runs. We recommend reading our article on debugging tips and tricks to learn more.
Hightouch can alert you of sync issues via Slack, PagerDuty, SMS, or email. For details, please visit our article on alerting.