Nextdoor Ads clicks,each stored with its ndclid

The Nextdoor template reads ndclid, the click ID Nextdoor adds on each click, and stores it as the visit's External ID. There is no postback: Nextdoor learns about conversions from the Nextdoor Pixel on your pages or from your own Conversions API setup, using the ndclid ClickFlare kept.

ND
Nextdoor Ads
Neighborhood social network ads
At a glance
How it connects
ndclid read from the click URL
What syncs
Nextdoor click ID, plus CM360 IDs if trafficked there
Sync schedule
Real time, per click
Key parameters
ndclid, %eaid!, %ebuy!, %eadv!, %ecid!
Works with
Ads in the Nextdoor feed
Good to know
No postback, no cost in the URL. Use a CPC cost model.
Social ad platform
ndclid capture
Pixel or Conversion API

ClickFlare as the revenue record for Nextdoor

The click ID for the CAPI

Nextdoor's Conversions API can match on the click ID. ClickFlare stores ndclid per visit, so your own system can send it as click_id.

Optimize on what you can see

Sending traffic to an affiliate offer? Fire a Nextdoor Pixel event on your lander, and judge real sales and revenue in ClickFlare.

CM360 data when you use it

If your Nextdoor ads run through Campaign Manager 360, the template's %e...! rows fill in with ad, campaign, advertiser and creative IDs.
How it works

From ad click to profit per campaignattributed revenueattributed salesa matched conversion

01
Your ad
Visitor clicks
Ad on Nextdoor Ads
02
ClickFlare
Click recorded
A unique cf_click_id is created
03
Your offer
Conversion
Lead, sale or custom event
04
ClickFlare
Sent back to Nextdoor Ads
Through the Conversion API or postback
05
Cost API
Spend pulled in
Nextdoor Ads cost matched to each campaign
01
Your ad
Nextdoor Ads click
Macros fill the tracking URL
02
ClickFlare
Click recorded
Zone, site and device data stored
03
Offer or lander
Visitor converts
On your page or the offer
04
ClickFlare
Conversion logged
With payout and event type
05
Postback
Reported to Nextdoor Ads
So its optimization sees the result
01
Your ad
Visitor clicks
Any traffic source
02
ClickFlare
Click recorded
A unique cf_click_id is created
03
Your article
Keyword block
Click ID passed to the feed
04
Results page
Paid click
Conversion fired to ClickFlare
05
Nextdoor Ads API
Revenue matched
Pulled on a schedule and reconciled
01
Your ad
Visitor clicks
Any traffic source
02
ClickFlare
Click recorded
cf_click_id passed to the offer
03
Nextdoor Ads
Offer or call
The network tracks the action
04
Nextdoor Ads
Conversion
Lead, sale, call or rebill
05
Postback
Payout in ClickFlare
Matched to the original click
01
Your ad
Visitor clicks
Any traffic source
02
ClickFlare
Click recorded
A unique cf_click_id is created
03
Nextdoor Ads
Store or funnel
Click ID kept through checkout
04
Events
View, cart, checkout
Each step tracked
05
ClickFlare
Purchase recorded
Order value matched to the ad
Social ad platform

How an ndclid reaches your reports

Nextdoor opens your campaign URL and adds ndclid. ClickFlare stores it as the External ID and sends the visitor on. The conversion posts back to ClickFlare. Nextdoor sees it only through its Pixel or your own Conversions API call.
  • Leave Traffic source postback URL off
  • Delete any empty ndclid= from the campaign URL
  • Nextdoor attributes 7 days after click, 1 after view
Today, one campaign
example
Spend pulled from Nextdoor Ads
cost
$412.30
Conversions recorded
today
38
Sent back to Nextdoor Ads
per event
38/38
Profit
campaign
$227.70
Example numbers. Cost and conversions sit in the same report row.
Captured on every Nextdoor Ads click
key macros
ndclid, %eaid!, %ebuy!, %eadv!, %ecid!
captured
From the Nextdoor Ads template in ClickFlare. Use them as report columns and rules.
Revenue for one click
example
Paid click
day 0
$0.00
First revenue pull
+1h
$0.41
Scheduled updates
next days
$0.58
Final pull
last sync
$0.62
Example amounts. Sync timing for Nextdoor Ads is in the facts above.
Events for one click
example
Lead
day 0
$0.00
Sale
day 0
+$40.00
Upsell
day 1
+$15.00
Refund
day 9
−$15.00
Example events. Each one arrives by postback and is matched to the click.
One visitor's path
example
Product view
step 1
—
Add to cart
step 2
—
Checkout
step 3
—
Purchase
step 4
$68.00
Example order. Each event is tied to the ad that brought the visitor.
7 days
Nextdoor click window
1 day
Nextdoor view window
1h
CAPI event deadline
2.3B
Events tracked
Setup

Connected in four steps

You need a Nextdoor Ads Manager account, your own tracking domain, an offer in ClickFlare and a page where you can install the Nextdoor Pixel.
  1. Add the Nextdoor traffic source In the campaign editor, click + New Traffic Source and pick the NextDoor template. Keep the External ID row, leave the postback off and save.
  2. Choose how Nextdoor sees conversions Install the Nextdoor Pixel on your conversion page, or on your lander with an event such as view_content. Or send the External ID as click_id through your own Conversions API setup.
  3. Copy and clean the campaign URL Set a CPC cost model. Copy the campaign URL and delete any empty ndclid= in it, so the only ndclid is the one Nextdoor adds.
  4. Launch and check the External ID Paste the URL as the ad's landing page URL in Nextdoor Ads Manager. Click the live ad and check the visit has an External ID in ClickFlare.
app.clickflare.com/integrations
ND
Nextdoor Ads
Social ad platform
Connected
Nextdoor Ads account connected
Signed in from ClickFlare
Cost syncing
Spend matched to campaigns
Conversions sent back
Your chosen events
Nextdoor Ads template selected
Macros pre-filled
Tracking URL in Nextdoor Ads
Click ID captured
Conversions reported
Payout included where supported
Nextdoor Ads connected
Credentials saved in ClickFlare
Conversion event set
Click ID passed to the feed
Revenue syncing
On the feed's schedule
Nextdoor Ads added
Offer URL carries the click ID
Postback set in Nextdoor Ads
Payout and event included
Conversions arriving
Matched to the click
Nextdoor Ads connected
Click ID kept to checkout
Events mapped
View, cart, checkout, purchase
Purchases tracked
Order value in reports
Ready to track
The %e...! tokens are Google Campaign Manager 360 macros, not Nextdoor ones. Without CM360, those columns stay empty or show raw macro text. Use fixed values such as nd_campaign=spring_promo.
Nextdoor Ads postback setup guide
Open the guide
In your reports

What you see once it's connected

  • Visits by External ID (ndclid)
  • CM360 ad ID breakdown
  • CM360 campaign ID
  • Advertiser and creative IDs
  • Conversions by fixed campaign tag
Use cases

How media buyers run it

Nextdoor → your store

Nextdoor to your own store

Fire the purchase pixel event on the thank-you page and keep ClickFlare as your revenue record.
Nextdoor → lander → offer

Nextdoor to affiliate offers

Fire a custom_conversion_ event on the offer click-through, and judge real sales in ClickFlare.

Server-side conversions

Export converting visits with their External ID and send them to Nextdoor's Conversions API as click_id within an hour.
Frequently asked questions

Questions about Nextdoor Ads

No items found.
Setup guides
Nextdoor Ads postback setup guide
{"@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "Does ClickFlare integrate with Nextdoor Ads?", "acceptedAnswer": {"@type": "Answer", "text": "Yes, for click tracking. The NextDoor template stores ndclid as the External ID. Conversions reach Nextdoor through its Pixel or Conversions API, not through ClickFlare."}}, {"@type": "Question", "name": "Why is there no postback in the Nextdoor template?", "acceptedAnswer": {"@type": "Answer", "text": "Nextdoor doesn't take conversions by postback URL. It uses its pixel or its Conversions API, which needs an authenticated server request a postback can't make."}}, {"@type": "Question", "name": "Does ClickFlare integrate with the Nextdoor Conversions API?", "acceptedAnswer": {"@type": "Answer", "text": "No. ClickFlare stores the ndclid as the External ID, so you can send it to the Conversions API from your own system."}}, {"@type": "Question", "name": "Why are my campaign and ad group columns empty?", "acceptedAnswer": {"@type": "Answer", "text": "Those rows use Campaign Manager 360 macros. Without CM360 they stay empty. Add a fixed-value parameter per campaign, such as nd_campaign=spring_promo."}}, {"@type": "Question", "name": "Why do Nextdoor's numbers differ from ClickFlare's?", "acceptedAnswer": {"@type": "Answer", "text": "They come from a different data path, and Nextdoor applies its own attribution windows: 7 days after a click, 1 day after a view."}}, {"@type": "Question", "name": "How do I track cost from Nextdoor?", "acceptedAnswer": {"@type": "Answer", "text": "No cost is passed and ClickFlare has no Nextdoor cost integration. Use CPC, or your CPM bid divided by 1,000, and correct it with a manual cost upload."}}]}