Nextdoor

Elevate your local marketing efforts with Nextdoor Ads and drive business growth by reaching nearby customers in their communities

Supported syncing

For more information about sync modes, refer to the sync modes docs.

Connect to Nextdoor

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.

Sync configuration

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.

Syncing events

Nextdoor's Conversions API requires the following event parameters:

• event_name
• event_time
• action_source
• client_id
• at least one customer parameter

Event name

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:

• conversion
• lead
• purchase
• sign_up
• custom_conversion_1
• custom_conversion_2
• custom_conversion_3
• custom_conversion_4
• custom_conversion_5
• custom_conversion_6
• custom_conversion_7
• custom_conversion_8
• custom_conversion_9
• custom_conversion_10

Event timestamp

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

The 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

The 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

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.

Hashing

By default, Hightouch automatically hashes the following customer fields:

• email
• phone_number
• first_name
• last_name
• date_of_birth
• street_address
• city
• state
• zip_code
• country

If you want to turn hashing off, select No under Would you like Hightouch to automatically detect if your PII data requires hashing?.

Tips and troubleshooting

Common errors

To date, our customers haven't experienced any errors while using this destination. If you run into any issues, please don't hesitate to reach out. We're here to help.

Live debugger

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.

Sync alerts

Hightouch can alert you of sync issues via Slack, PagerDuty, SMS, or email. For details, please visit our article on alerting.