A lead-form business does not win on clicks. It wins on the leads that book a call and the calls that turn into sales, and most of those happen on pages Meta’s own pixel never sees clearly: a booking embed, a form on another domain, a deal closed in the CRM a week later. The October 30 release gives Nask AI its own pixel and a place to map that whole funnel.

What changed

Open a brand, go to the Growth tab and find Pixel and funnel. It has two cards.

1. Install the pixel gives one script tag to paste in the head of every page of your site. It loads nsk.js from t.nask.ai and carries the brand’s public ID, so events from your site land on the right brand. Nothing else needs to be installed on the page.

2. Funnels and stages is where you describe what counts. Each stage has a type (Lead, Schedule, StartTrial, InitiateCheckout, Purchase, Subscribe or CompleteRegistration) and a way to detect it:

  • a form on your page,
  • a page URL, such as a thank-you page,
  • a booking or form embed (Cal.com, Calendly, HubSpot, GoHighLevel, Jotform, Typeform),
  • a custom JavaScript call,
  • your CRM, Stripe or a webhook, for stages that happen after the visitor has left the site.

Stages you define under your own name, such as a qualified call, keep that name when they reach Meta. Stages that close later, offline, are sent with the timing Meta accepts for them, so a sale recorded weeks after the click still counts.

Testing a stage before you trust it

Each stage has Test this stage. Click it, Open the test page, and do what a visitor would do; Nask AI listens for the event for 90 seconds and tells you whether it arrived. If it shows Not detected, the debug panel lists the likely causes, and Send to Nask AI support sends the case to the team with the details attached, so you do not have to describe the setup from memory.

Choosing what goes to Meta

Every stage has a Send to Meta toggle. Turn it on for the stages you want Meta to optimize toward, and leave it off for the ones you only want to see in Nask AI. A brand starts in Dry run on the Sending to Meta card, so you can watch events arrive before anything is sent; Go live starts sending. Each send is stored with Meta’s answer, so a stage Meta refused leaves a record instead of disappearing.

Where it sits in the workflow

The pixel is the last box of the loop: Nask AI makes and publishes the ads, Meta delivers them, and nsk.js reports which ones produced booked calls and sales. The full loop is laid out on how Nask AI works, and the step-by-step setup is in the Nask AI pixel setup guide.