📘
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.
Product Type: Advertising
Integration Type: Starter Kit & ID Sync
Event Source Type: Web
Event Scope: Full-Funnel Events
- 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.
- Events are rejected when the
ndclid (Nextdoor Click ID) is missing.
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
- Captures the
ndclid (Nextdoor Click ID) used for conversion attribution.
- Required by Nextdoor to associate events with prior ad clicks; events without it are rejected.
- Without this sync, events may not be accurately reflected in reporting.
- To collect the sync values (e.g.,
ndclid), you must implement a Nextdoor ID sync. Refer to the following documentation to complete the setup: Nextdoor - ID Sync Guide.
- Apply for Nextdoor API access to obtain your client ID.
- Access Token: Follow Nextdoor's documentation to obtain your access token. Note this token expires one year after it is generated.
- Pixel ID: Contact your Nextdoor support team for your Pixel ID.
- From the integration library, add a Nextdoor integration. Then, fill out the Connection Parameters:
| Connection Parameter | Description |
|---|
ACCESS_TOKEN | Access token generated once approved for API access. Note this token expires after a year. |
PIXEL_ID | ID from your Nextdoor pixel. |
- 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.
- In the Pipelines tab, add your Nextdoor integration.
- Select the correct integration revision.
- Click Add Integration to finalize deployment.
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.
| Output Key | Description | Expected Input |
|---|
pixelId Required | String: The unique identifier for the Nextdoor pixel. | $$PIXEL_ID$$ |
eventTime Required | Timestamp: The time when the event occurred, in milliseconds since epoch. | Enrichment – event timestamp in milliseconds |
eventId Required | String: The unique identifier for the event, derived from the Nextdoor Click ID. | context.providers.nextdoor.ndclid |
referer | String: The URL of the page that referred the user to the current page. | context.page.referrer |
eventSource Required | String: The URL of the current page where the event is taking place. | context.page.url |
| Output Key | Description | Expected Input |
|---|
eventName Required | String: Indicates that a page view event has occurred. | Enrichment – 'PAGE_VIEW' |
| Output Key | Description | Expected Input |
|---|
eventName Required | String: Indicates that a product has been viewed. | Enrichment – 'VIEW_CONTENT' |
| Output Key | Description | Expected Input |
|---|
eventName Required | String: Indicates that a product has been added to the cart. | Enrichment – 'ADD_TO_CART' |
| Output Key | Description | Expected Input |
|---|
eventName Required | String: Indicates that a cart has been viewed and the checkout process has started. | Enrichment – 'START_CHECKOUT' |
| Output Key | Description | Expected Input |
|---|
eventName Required | String: Indicates that an order has been completed. | Enrichment – 'PURCHASE' |
| Output Key | Description | Expected Input |
|---|
eventName Required | String: Indicates that a user has signed up. | Enrichment – 'SIGN_UP' |
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.
| Attribute | Example | Sync Injector Required? |
|---|
eventId Required | 123abc456def789ghi | Yes |
Coordinate with your Nextdoor representative, or use the Nextdoor dashboard, to confirm that events are being received and processed correctly on their backend.
