Nextdoor Sync

What is Nextdoor?

Nextdoor is a hyperlocal social networking service that connects neighbors and local communities. The platform facilitates neighborhood-level communication, allowing users to share updates, recommendations, and public safety information. Businesses and advertisers can engage users through targeted local campaigns, leveraging user interactions and localized data. Nextdoor's tools support community-building as well as location-specific marketing efforts.

Product Type: Advertising

Integration Type: Starter Kit & ID Sync


Capabilities

  • Captures ndclid from URLs and stores it for tracking conversions.
  • Stores the captured value in first-party storage using a consistent naming format.
  • Refreshes the value and its expiration whenever the parameter is redetected in the URL.
  • Adds the ndclid identifier to server-side events for improved attribution.
  • Enables advertisers to tie user engagement back to specific Nextdoor campaigns.

Sync Details

  • IDs:

    • ndclid – A campaign tracking parameter used by Nextdoor to associate user activity with specific ad clicks or impressions.
  • Description:

    • The sync captures ndclid from URL parameters.
    • Each value is stored in first-party storage for a configured duration.
    • Values are refreshed when new data is detected.
    • The identifiers are added to server-side event payloads for attribution or targeting.
  • Server-side Event Payload:
    Upon completion of all vendor's sync, the server-side events will incorporate all resolved identifiers as described above. The following object will be appended to the context.providers property within the event's JSON payload.

    {
      "nextdoor": {
        "ndclid": "URL parameter value from ndclid"
      }
    }
    
    
  • Cookie Name:

    • Cookie: _meta_nextdoor_ndclid
    • IndexedDB: [your storage prefix]_nextdoor_ndclid
    • For a general guide on ID Sync validation, see here.

Sync Setup Guide

1. Add a Nextdoor Sync in MetaRouter

To gather the ndclid, 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. Cookie Lifetime (in days) – Defines how long the ndclid value should persist in storage. Example: 30
  4. Scroll down and click the Save and Build File button.
  5. Deploy your AJS file to propagate changes to your web property.