Skip to content

Track ClarNow forms with the Meta Pixel

Add your Meta Pixel ID to a ClarNow form and every visit, start and lead from your Facebook and Instagram ads is counted in Events Manager — so you can see which ads bring leads and let Meta optimize for them.

When Meta event
The form opens PageView
The respondent reaches the first question ViewContent
The respondent submits, on a lead ending Lead

“Lead ending” is up to you: by default every submit counts as a lead; pick endings under Count as a lead to send Lead only for, say, the qualified ones. For a scorecard, that teaches your campaigns to find more people like your best leads.

  • A ClarNow organization on the Pro plan or higher.
  • Edit access to the form.
  • A Meta Pixel (a dataset in Events Manager) and its ID — 8 to 20 digits, shown in Meta Events Manager → Data sources.
  1. Open the form in the ClarNow builder and go to Connect → Analytics, then click the Meta Pixel tile.

  2. Paste the pixel ID and click Save. The panel shows “Connected — loads on the form’s direct link”.

  3. Choose lead endings (optional). Under Count as a lead, pick the endings that should send Lead. Leave it empty to count every submit.

  4. Check it. In Events Manager, open the pixel → Test events, open the form’s link and go through it. The events appear within seconds.

The pixel loads at once — you don’t need to republish the form. Use the form’s link, with your UTM tags, as the destination URL of your ads.

Turn on Cookie consent on the same Connect → Analytics tab and publish the form. Respondents then see an Accept / Decline banner, and nothing is requested from Meta until they accept. Events from before the answer go out on Accept and are dropped on Decline. The choice is remembered per form in the respondent’s browser.

With cookie consent off, the pixel loads as soon as the form opens. Whether you need consent depends on where your respondents are and how you use the data — the decision, and the responsibility, are yours.

What Where it goes Why
The page visit and the events above Your Meta Pixel, from the respondent’s browser Ad measurement and optimization

The pixel runs in the respondent’s browser under your Meta account, as on any page of your site: Meta sets its usual cookies and collects what the pixel collects by default. For that data you are the controller and Meta is your vendor, not ClarNow’s subprocessor. ClarNow sends Meta nothing from its servers and puts no answers in the events. See the Privacy Policy.

What ClarNow stores: the pixel ID and the chosen lead endings, on the form.

  1. Open the form → Connect → Analytics → Meta Pixel.

  2. Click Remove.

What changes: the pixel no longer loads on the form’s link, at once.

What stays: the events already in Events Manager.

Which ClarNow plan do I need for the Meta Pixel?

Pro (€24/mo billed annually, €30 monthly) or Business. On a lower plan the tile is locked. If you downgrade, the pixel stops loading; the ID stays so you can remove it.

Does it work when the form is embedded on my site?

Your pixel loads only on the form's own link. Inside an embed, the form sends clarnow.* events to your page instead; fire your site's own pixel from them, for example through Google Tag Manager or the embed's onSubmit callback.

Are answers or emails sent to Meta?

No. The events are sent without parameters — no answers, no email, no score — and ClarNow doesn't use Meta's Conversions API from its servers.

Why does Events Manager show no Lead events?

Test with the Test events tab in Events Manager first. If the form has cookie consent on, nothing is sent until the respondent clicks Accept. If you picked endings under Count as a lead, only submits that end on one of them send Lead.

Can I optimize an ad campaign for leads from the form?

Yes. Choose your pixel and the Lead event as the conversion event of a Leads or Sales campaign. Pick only qualified endings under Count as a lead, so Meta learns from the leads you actually want.

Email [email protected] or pick a case on the contact page — no account needed. We reply within two business days, usually within one. See also Support, the Privacy Policy and the Terms of Service.