Meta Pixel

How to connect the Meta Pixel (formerly Facebook)

Heyflow avatar
Written by Heyflow
Updated over a week ago

The Meta Pixel (formerly Facebook Pixel) is a tracking tool designed for businesses and advertisers on the Meta platform (Facebook, Instagram).

The Pixel monitors user interactions, such as page views or button clicks, and tracks conversions whilst establishing the connection between your flow and Meta. The data gathered enables you to optimize your Meta ad campaigns by providing insights into user behavior, which in turn facilitates the creation of custom audiences, optimize ad delivery, and support remarketing efforts.

Installing the Meta Pixel usually involves placing a code snippet on a website; in our case, however, Heyflow makes it much easier, by offering a native integration, that merely requires you to insert the Pixel ID.

In this guide, you learn how to set up the Meta Pixel with Heyflow to track your users' behavior and which events we automatically send.

🔎 Before you connect your heyflow, also check out our help article to verify your domain on Meta, if you are using a custom domain.

🔎 Since the Meta Pixel lives in the browser, it's often blocked, which reduces the quality of your analytics. The Meta Conversions API (CAPI) mitigates that problem by sending the same events through another route – an API. Take a look here for more information.


Step 1: Set up the Meta Pixel

The Pixel ID can be found in various places in your Meta. When accessing your Events Manager Overview, the ID of the respective pixel can be found right away on the right-hand side, just below the name of the pixel:

When clicking on the pixel, you access the actual Events Manager, where you can find the Pixel ID as well, under Settings:

Step 2: Connect your heyflow

Now, go to your heyflow and navigate to Integrate > Analytics. In the list, click the Meta Pixel and paste the copied access token into the Pixel ID field. You can also change the name of the submit event, in case you want it to be something different from CompleteRegistration.

Click on Connect and republish your flow… and that’s it! The Meta Pixel has been successfully installed in your heyflow!

Step 3: Testing

Now it's time to test if the events are correctly tracked in Meta. For this, return to the Events Manager and click on Test Events. Head over to Confirm your website’s events are set up correctly, and insert your flow’s URL:

After you have clicked on Open website, you’ll be redirected to your flow. Click through your flow as a test run. Once you hit the submit button and return to the Events Manager, you'll see the incoming browser events:

Congratulations. Your events are being tracked correctly in Meta!

❗ The triggered events are shown with a short delay (30–60 minutes) in your Meta event manager overview.


An event tracked automatically by Heyflow is:

  • PageView: Signals if a user views a screen of the funnel

  • CompleteRegistration: Signals if a user clicked on a “submit”-button

‌Heyflow also offers a standardized set of other events you can track with your pixel when integrating our Google Tag Manager container with your flow. To see how to integrate Google Tag Manager, click here.

Results of events named the same will be clustered automatically by Meta. Meaning, it is recommended to not create custom events via Google Tag Manager or with the Meta tagging tool named the same way as already prevalent events. If you create two events with the same name, the event data is not kept apart within the Meta event manager.

You can use these events to create custom audiences on Meta. Before creating a custom audience, you have to receive at least some data (1 user is enough) who triggered all your Meta events once. Before triggering your events at least once, you are not able to select them within your custom audience.

Custom Event Tracking

PageViews are tracked automatically. But you can track a lot more events with Heyflow. To set up tracking for buttons, picture or multiple choice clicks, go to the Build page of your heyflow, click on the block you want to track, and go to Tracking in the left sidebar. Activate Track button click and enter an event name below.

If you name your event one of the Meta Standard Events, like Contact or ViewContent, Meta will recognize it as such. If you name it anything else, it will get tracked as a Custom Event.


I don't see any events

There may be several reasons for this:

  • Changes not published yet: First, make sure that your flow has been republished after you have made changes to the integration.

  • Cookies declined: The pixel does not work if a user has declined the tracking cookies. Make sure you accept the cookies to see your test events, for example, or try again in a different browser.

  • Multiple integrations: If you have also integrated the pixel via the Google Tag Manager, this may lead to blocking. So choose one way: either via the GTM or only via our direct integration.

My submit event gets tracked twice

If the submit event gets tracked twice, this probably means that you have activated individual tracking of the submit button. This is not necessary, as the submit event will always be tracked as Complete_Registrationby default.

To make sure it only gets tracked once, open the block settings for your submit button and remove the checkmark in the tracking tab.

Did this answer your question?