📘

For Nextdoor CAPI, see HERE.

What Is Nextdoor Ads?

Nextdoor ads are targeted advertisements on the Nextdoor platform, a social networking service for neighborhoods. These ads are designed to reach local audiences, leveraging user data to provide relevant content based on geographical location and community interests. Businesses can use Nextdoor ads to connect with nearby potential customers, promoting services, events, and offers in a trusted, community-centric environment.

What are the benefits of integrating MetaRouter with Nextdoor Ads?

• Reduced Latency: Eliminates client-side tags, resulting in faster page load times.
• Tag Management: Simplifies the removal and management of Nextdoor tags.
• Data Accuracy: Ensures accurate and reliable data collection via server-to-server integration.
• Improved Targeting: Enhances ad campaign optimization for better ROI.

Capabilities and Considerations

• Flexible and Efficient Data Handling:
  • Request only the specific data needed from Nextdoor's GraphQL API.
  • Combine multiple data requests into a single query.
  • Efficiently handle large volumes of data, reducing redundancy and improving performance.
• Customizable Event Processing:
  • Reject events if the ndclid (Nextdoor Click ID) is missing.
  • Allow events based on specific event names.
  • Validate data against specific conditions to maintain data integrity.
• Event Mapping, Enrichment, and Transformation:
  • Map incoming data fields to desired output fields for Nextdoor.
  • Enrich events with static values and timestamps.
  • Assign static event names for specific events.
  • Utilize complex transformations to format data correctly.
• Simplified API Interactions and Data Management:
  • Simplify interactions with Nextdoor's API through MetaRouter’s integration layer.
  • Centrally manage data flows and transformations within MetaRouter.
  • Monitor and troubleshoot data integration issues with MetaRouter’s tools and logging.
• Token Expiration: Your Nextdoor access token will expire in a year after it’s been generated. Please mark your calendar to update the token in the MetaRouter integration a year from when the token was generated.

Nextdoor Ads vs Nextdoor CAPI

Nextdoor Ads:

• Endpoint: https://ads.nextdoor.com/graphql/api/v1
• Filters: Reject events if the ndclid (Nextdoor Click ID) is missing.
• Event-Specific Configurations: Static string enrichments for eventName for events like cart_viewed, order_completed, and signed_up

Nextdoor CAPI:

• Endpoint: https://ads.nextdoor.com/v2/api/conversions/track
• Filters: Allow events based on their names without extra conditions.
  • This means that any event with a specified name is accepted and processed.
  • No additional conditions or criteria are required for these events to be allowed.
  • The filter list is set to accept events simply if their names match the allowed list.
• Mappings: Use Lua scripts to hash customer information (email, phone number, address) for increased user matching
• Event-Specific Configurations
  • For order_completed events:
    • Map order_id, product_context, and order_value with complex transformations
    • Calculate the total order value by summing product prices and adding the currency code

---

Getting Started - From Your Nextdoor Account

• Apply for API access: Please follow the instructions here to apply for API access. Once granted, you will be given a client ID that you will need to use for this integration.
• Access Token: Please follow the instructions here to obtain your access token.
  • **IMPORTANT NOTE: Your Nextdoor access token will expire in a year after it’s been generated. Please mark your calendar to update the token in the MetaRouter integration a year from when the token was generated.*
• Pixel ID: Please contact your Nextdoor support team for your Pixel ID.

---

Getting Started - From Your MetaRouter Account

Adding a Nextdoor integration.

From the integration library, add a Nextdoor integration. Then, fill out the Connection Parameters:

Adding a Nextdoor Sync

To gather the ndclid value, you must add a Nextdoor sync.

1. From the Pipelines page, find the pipeline associated with the web property you’d like to add a sync to. Hover over the three dot dropdown and select “Build AJS File.”
2. In the Identity Syncs section, select the Nextdoor sync.
3. Fill out the following fields:
   1. Consent Type - We recommend that you consult with your legal team when determining your consent requirements.
   2. Cookie Lifetime (in days) - 7 days default
4. Scroll down and click the Save and Build File button.
5. Deploy your AJS file to propagate changes to your web property.

---

Event Mappings

MetaRouter provides all of the event mappings that Nextdoor integrations typically require. You may add custom events, parameters or mappings in accordance with Nextdoor’s API documentation.

Global

Global mappings will be applied to all events. If your parameter names do not match the Expected Inputs provided, you will need to overwrite the Inputs provided with your own.

Event Specific

All parameters are required.

Cart Viewed

Order Completed

Page

Product Added

Product Viewed

Signed Up

---

Required Identifiers

These identifiers must be mapped to Nextdoor in order for successful user matching to occur. Without these IDs, any events sent to Nextdoor may not be accurately reflected in reporting. For your convenience, required IDs are mapped as Global parameters to ensure they are added to every event.