Meta Pixel for NextDoor AI

• A paid plan (Starter or Growth). Events do not send on the free plan.
• Your Pixel / dataset ID. This is the numeric ID from Meta Events Manager.
• A Conversions API access token. In Meta Events Manager, open your pixel, then Settings, then Conversions API, then Generate access token. It is stored encrypted and never shown again.
• A Privacy Policy URL, saved in NextDoor AI under Settings, then Brand. This is required: your booking page shows a short privacy notice above the Book button that links to it, and events do not fire until it is set.

To connect, in NextDoor AI at crm.nextdoorai.in:

1. Go to Settings, then the Integrations tab.
2. Find the Meta Pixel (Conversions API) card and click Connect.
3. Paste your Pixel / dataset ID and your Conversions API access token, then Save.
4. The card shows "Connected," with your dataset ID.

NextDoor AI sends seven events. Three funnel events are optional toggles you turn on per pixel (any or all three, on a paid plan). The other four are automatic: they are always on once your pixel is connected on a paid plan.

Schedule, Contact, NoShow, and Purchase carry advanced matching: your prospect's email, phone, name, and country, each hashed before it leaves us, plus a per-person identifier that ties the booked call to its later attendance and payment. The three funnel events carry no contact details, because the visitor has not typed anything yet.

NoShow is a custom event on purpose. Use it only for suppression or exclusion audiences, never as an optimisation target: optimising toward it would teach Meta to find you more no-shows. Contact is a standard event and is a valid optimisation target.

Only hashed values ever reach Meta. Raw email, phone, and name never leave NextDoor AI, and intake answers, session titles, and page query strings are never sent.

Meta lets you configure eight conversion events per domain. NextDoor AI uses seven, which leaves one slot free. The most common thing coaches want in that slot is a Lead event. Rather than fire a separate Lead event, define it as a custom conversion off Schedule: a booked call is your lead, and Schedule already carries advanced matching, so your Lead conversion inherits the same match quality.

In Meta Events Manager:

1. Open Custom Conversions and click Create custom conversion.
2. Choose your dataset as the data source.
3. Choose Schedule as the conversion event.
4. Optionally add a rule so it only counts booking-page conversions: URL contains /book/.
5. Name it Lead, pick the Lead category, and click Create.
6. Open Aggregated Event Measurement for your domain, add your new Lead conversion to the configured events, and set its priority where you want it.

Your Lead conversion now updates every time a call is booked through your booking page, and you can optimise and report on it like any other Meta conversion.

You set this up in your own Meta Events Manager, against your own dataset. It is per coach: there is no central NextDoor AI step that creates the Lead conversion for you, so each coach who wants it defines it once in their own account.

Your Lead count reflects calls booked through your booking page only. It does not include calls booked over WhatsApp, which fire nothing (see "What does not fire, and why" below).

A call booked over WhatsApp fires nothing to your pixel. When your AI assistant books a call inside a WhatsApp chat, or you add a lead by hand, the prospect never opens your booking page. They never see the privacy notice, so no consent record is written for that booking.

Every Meta event we send has to be tied to a person who saw that privacy notice. Because a WhatsApp booking has no consent record, none of the events fire for it: no PageView, ViewContent, or InitiateCheckout (no page was loaded), no Schedule, and no Contact, NoShow, or Purchase later, because those are tied to the same booking. This is deliberate. We send nothing rather than send an event with no consent behind it.

So if a real call is missing from your Meta funnel, that is usually the reason: it came in over WhatsApp, not through your booking page. The call is still in your CRM and still counts for you. Judge your pixel and ad performance on the calls booked through your booking page.

Events also stop sending if your plan lapses or your Privacy Policy URL is removed. The Meta Pixel card shows "On, not sending" in that state, and resumes automatically once the plan and privacy URL are back in place.

On the Meta Pixel card, use Send a test event. It fires the funnel, Schedule, Contact, and Purchase events to your dataset with a Meta test code, so they land in the Test events tab in Events Manager and never count as real conversions.

The test proves the server side (Conversions API) end to end. It cannot confirm the pixel fires in your visitors' browsers, so also run one real booking on your own booking link and confirm it appears in Events Manager.

The Meta Pixel card shows the status of your last event and whether anything is retrying. If a send fails it retries automatically. If delivery keeps failing, your access token or dataset ID may no longer be valid: generate a fresh token in Events Manager and use Replace on the card to save it.

To stop reporting, open Settings, then Integrations, and click Disconnect on the Meta Pixel card. New bookings will no longer report to your pixel.

For how we handle the data sent to Meta, see our Privacy Policy at nextdoorai.in/privacy. Need help? Contact us at nextdoorai.in/contact.