How to Track Facebook Lead Form CTA Clicks with Conversions API

How can you track COMPONENTS in a lead form

Hey there,

Is it possible to track certain clicks within the Lead form flow?

For instance, at the end there is a final CTA at the bottom, usually the button goes to your website or sometimes a file download.
How would you track this specific click in the lead form within Facebook, so that I know “of the people that click my lead form, x number of people also click that final CTA button?

The short answer is:

The long answer is:

The challenge you’re facing is common because the user never leaves the Facebook environment until the final CTA click, so the standard client-side Meta Pixel on your website can only fire a Lead event when the form is submitted, and a PageView or another event if the user lands on your website after the final click.

It cannot track the specific click inside the Instant Form.

To get the data point “of the people that click my lead form, x number of people also click that final CTA button,” you need to track the “Thank You” screen event which contains that final CTA.

The recommended best-practice solution is to utilize the Conversions API (CAPI) to send server-side events directly to Facebook.

You can configure your setup to capture the user’s interaction with the Instant Form, including the final CTA click, as a specific, high-quality event.

The key is to recognize that Facebook Lead Forms automatically generate certain events.

When a user submits the form, Facebook automatically registers a Lead event.

However, to track the next step (the final CTA click), you have to create a custom event, and the most robust way to do this is with a server-side tagging infrastructure.

The process involves connecting your Lead Form data to a server-side environment.

Facebook allows you to set up tracking parameters within the form itself to pass unique identifiers.

When a user submits the form, you receive the lead data, which includes a unique lead ID and other user data (hashed for privacy).

You then use this data to send a new, server-side event back to Facebook via CAPI.

For the final CTA click on the Thank You screen, you would set up a distinct event, let’s call it Final_CTA_Click, which is triggered only when a new lead hits that last screen.

Using the Facebook Conversions API with Google Tag Manager’s server container and a service like Stape or Google Cloud Platform is an excellent and cost-effective solution for several reasons.

First, it bypasses browser-side tracking limitations like ad blockers and restrictive cookie policies (iOS/Safari) that often cause the Meta Pixel to lose data.

Second, it gives you granular control over the data you send.

Instead of relying on the standard Lead event, you can create a custom Final_CTA_Click event with high-quality data parameters like the form ID and a conversion value.

Third, it is remarkably stable and scalable.

By using server-side Google Tag Manager (s-GTM) with a cloud provider like Google Cloud Platform or a specialized platform like Stape, you create your own tagging server.

The s-GTM container acts as a central hub: it receives data from the Facebook webhook or your CRM when a lead is created, processes it, and then sends the Final_CTA_Click event through the Conversions API directly to Facebook.

Stape, in particular, offers a pre-built, one-click hosting solution for s-GTM that is often much cheaper and simpler to maintain than setting up a server on Google Cloud Platform yourself, making it an incredibly cost-effective method to achieve precise, cookieless, and privacy-compliant tracking for every specific component of your lead funnel.

This level of detail allows you to accurately measure the drop-off between a form submission and the final website/download click, giving you real insights to improve your form design and overall funnel performance.

About The Author