Connect Invoca and Nextdoor Ads Manager to report phone calls and call outcomes from Nextdoor ads, for marketers who manage Invoca integrations.
Overview
Connecting Invoca and Nextdoor Ads Manager lets you map phone calls and call outcomes back to Nextdoor ad views or clicks. This improves ad measurement and shows which campaigns drive local conversions. Setup has three steps:
- Get your Conversions API (application programming interface) credentials from Nextdoor Ads Manager.
- Set up the integration tile and conversion Actions in Invoca.
- Update your Invoca Tag to capture the Nextdoor Click ID and visitor attributes.
Before you begin
- You have a Nextdoor Ads Manager account.
- You have an agreement with Nextdoor that allows you to create API access tokens. If you do not see an option to manage tokens in Ads Manager, contact your Nextdoor account manager or email ads-api@nextdoor.com.
- Your Invoca Tag is deployed on your website.
Step 1: Get your Nextdoor Ads Manager credentials
Collect the following from your Nextdoor account:
- Nextdoor API Token: Manage access tokens in the Nextdoor Ads Manager API settings. The token lets Invoca authenticate and send data to the Nextdoor Conversions API.
- Nextdoor Data Source ID: Also called the pixel ID. Nextdoor uses it to deduplicate events. Find it in Nextdoor Ads Manager under Assets > Pixels. If you do not have a pixel to track offline conversions from Invoca, create one.
- Nextdoor Account ID: Your Nextdoor Ads Manager (NAM) Advertiser ID. It is the numeric Account ID value under Ad Account in the upper right of Nextdoor Ads Manager.
Step 2: Set up the integration in Invoca
With your credentials ready, connect your accounts in Invoca and create an Action for each Call or Signal you want to report.
Connect your Nextdoor Ads Manager account
- In the Invoca sidebar, click Integrations, then click Manage Integrations.
- Click the Nextdoor Ads Manager tile.
- Enter a friendly name for the integration.
- Enter your Nextdoor API Token, Data Source ID, and Account ID.
Create an Action for each Call or Signal
An Action sets which Calls or Signals (call outcomes) Invoca reports to the Nextdoor Conversions API.
- Select the Send Conversions (with IP Address) Action type.
- Enter a friendly name and choose the transaction type from the Triggered By menu.
- Enter the Event Name. Nextdoor requires a standardized event name, and the value must match one of the following exactly:
purchase, lead, sign_up, add_to_cart, initiate_checkout, page_view, search, view_content, add_to_wishlist, subscribe, or custom_conversion_1 through custom_conversion_10.
- Click Save. Repeat for each additional Signal.
Note: Each custom conversion slot must map to a custom conversion that you created for Invoca-specific events in Nextdoor Ads Manager under Assets > Pixels > Event Configurations.
Step 3: Update your Invoca Tag to capture attribution data
To improve match quality, make sure your Invoca Tag captures the Nextdoor Click ID (ndclickid), IP address, and User Agent.
- Click the gear icon, select Invoca Tags, then select your Tag.
- In the Revision History tab, create a New Draft.
- In the Marketing Data section, find the Nextdoor Click ID (
ndclickid) field and set its Data Source Type to URL Param.
- Switch the Capture IP Address and Capture User Agent toggles to on.
- Test your Tag changes, then click Save & Go Live.
Note: An IP address is personally identifiable information (PII). Check your company’s privacy policies before you switch on Capture IP Address.
Validate that events reach Nextdoor Ads Manager
- Go to Integrations > Manage Integrations.
- Click the Nextdoor Ads Manager tile, then click the name of your configured Action.
- Use the Delivery Details and Delivery History tabs to confirm that server-to-server requests return positive (green) responses.
Frequently asked questions
What fields does Invoca send to Nextdoor Ads Manager?
Invoca sends the following:
- Attribution identifiers: The phone number hashed with SHA256 (a one-way hashing method), the Nextdoor Click ID, the client IP address, and the client User Agent.
- Event data: The Event Name, Event ID, timestamp, and action source (
phone_call).
- Financial data: A custom order value mapped from revenue, and an order ID mapped from the unique transaction ID.
Last modified on November 3, 2026