Meta Pixel
Meta Pixel is a Meta tool that records website browsing events to support ad measurement and audience creation for campaigns on Facebook and Instagram.
The integration with Falaê loads the pixel configured in the branch's forms and sends the page view event to Meta. You track these events in the Meta Events Manager.
Before you start
- Access the Integrations screen in Falaê. The Cashier profile cannot configure this integration.
- Have a pixel created in Meta and access to its identifier. If the account is managed by an agency or someone else, request the ID and access necessary to follow events.
If you manage more than one branch in Falaê, check which one is selected. The ID will be used by that branch's forms.
How to configure the integration
- Access Goal Event Manager with the account responsible for the pixel.
- Locate the pixel you want to use and copy its identifier. If you don't already have a pixel, see the official guidance for setting up Meta Pixel or ask the account owner to create it.
- In Falaê, access Integrations and open Meta Pixel, in the Marketing category.
- Paste the identifier in the Pixel ID field. Falaê only accepts numbers, with 15 or 16 digits.
- Click on Configure and wait for the message Integration completed successfully.
- Open the link for a branch survey and check the pixel details in the Events Manager for receipt of a PageView event. Meta advises to wait a few minutes and refresh the page if the event still does not appear.
In Falaê, you only enter your ID. The integration takes care of pixel loading; It is not necessary to paste the complete code into the field.
How integration works
When survey and branch data are loaded, the form uses the received ID to initialize the pixel and call the PageView event. Reception and analysis take place at Meta.
The sending made by Falaê is linked to the loading of this data. Advancing between questions, registration and the thank you page within the same survey does not, in itself, trigger a new PageView call from Falaê.
Audience rules and the use of events in campaigns are configured in the Goal account. The integration starts to act on accesses made after configuration and does not recover visits before installation.
Questions and maintenance
Does the integration send NPS score or survey completion?
The automatic sending of this integration is the page view event. It doesn't report NPS score, customer feedback, or a specific survey completion event.
To measure other actions such as conversions, arrange the configuration and validation of these events with the person responsible for the campaigns.
Does a view correspond to a response or a single access?
No. In the survey, the current initialization can generate two PageView calls on the same load. Additionally, test links also trigger the pixel when the ID is configured.
Therefore, the number of events should not be treated as the total number of responses or unique accesses. If you need a measurement without duplication, consult Falaê team and validate the behavior in Meta before using these events in campaigns.
Why is the Configure button disabled?
Check that Pixel ID is filled with numbers only and is 15 or 16 digits long. Remove spaces and make sure you copied the pixel identifier rather than the installation code or ID of another Meta resource.
I configured it, but I don't see events in Meta. What to do?
Check the branch selected in Falaê, the pixel consulted in Meta and the survey link used in the test. After configuring, open the form again so that it loads the updated ID.
Tracking blockers can prevent the pixel from loading. If the problem continues, inform Falaê team of the branch and the message presented.
How to change the pixel?
Open the integration, click Cancel integration and configure it again with the correct ID. Then, test receiving PageView on the new pixel.
If you also use the same pixel through Google Tag Manager, review the tags to prevent the same view from being sent by both configurations.
How to disconnect the integration?
On Falaê Integrations screen, open Meta Pixel in the desired branch and click Cancel integration.
Falaê removes the ID saved for that branch. When the form loads the updated branch data, this setting stops initializing the pixel. Tabs already open keep the code loaded; close or reload the form to check the disconnection.
The action does not delete the pixel in the Meta or cancel an installation made separately by Google Tag Manager.
