Google Tag Manager
Google Tag Manager is a Google tool for configuring, testing, and publishing measurement tags for Google and third-party products on websites.
The integration with Falaê loads the GTM container in the branch's forms and provides a page view event. The tags you configure and publish to the container define what information will be sent and to which platforms.
Before you start
- Access the Integrations screen in Falaê. The Cashier profile cannot configure this integration.
- Have a Google Tag Manager account with a Web container. If you need to create one, follow the official guide to creating an account and container.
- Have access to edit and publish tags or rely on the person responsible for the container to carry out these steps.
If you manage more than one branch in Falaê, check which one is selected. The container will be loaded into the forms in that branch.
How to configure the integration
- Go to Google Tag Manager and open the web container you want to use.
- In Workspace, find and copy the container ID, which starts with GTM-. If you need to check the code, click this tag to open Install Google Tag Manager.
- In Falaê, access Integrations and open Google Tag Manager, in the Marketing category.
- Paste the identifier in the GTM ID field. Enter the prefix GTM- followed by at least six capital letters or numbers.
- Click on Configure and wait for the message Google Tag Manager configured successfully!
- In GTM, configure the tags and triggers you want to use. To measure hits with Google Analytics 4, follow the Google Analytics guide.
- Click Preview, enter the link to a branch survey and click Connect. In Tag Assistant, check the container loading, the number of messages sent and the behavior of the tags when progressing to the thank you page.
- After checking the tags, click Submit, select Publish and create version, enter the name and description of the version and click Publish.
In Falaê field, enter only the container ID. Charging is done via integration; No need to paste the code blocks provided by Google.
Saving the ID in Falaê connects the container to the forms. Tag changes go live after publishing to GTM. Also see official guidance for checking and publishing tags.
How integration works
When the survey and branch data is loaded, the form uses the received GTM ID to initialize the container. Falaê provides the pageview event and the page field in the data layer, with the page path at the time of sending the message. These names can be used by those responsible for configuring custom variables and triggers in GTM.
The pageview event sent by Falaê accompanies the loading of this data. Changes of address when moving between questions, registration and the thank you page do not, in themselves, generate new events of this type through Falaê. To measure internal navigation, configure and test tags according to Google's guidance for history change triggers.
GTM executes tags according to published triggers and rules. Data analysis takes place in the destinations of these tags, such as Google Analytics. Therefore, connecting the container is a different step than setting up the measurement on each tool.
The integration does not automatically make NPS scores, comments, or a specific survey completion event available in the data layer. To measure other actions, arrange the event and its validation with the person responsible for tracking.
Questions and maintenance
Why do duplicate events or uploads appear?
The current survey initialization may load the same container twice and make two pageview events available. Therefore, a rule triggered by these events may record the same visit more than once.
Check the result in Tag Assistant and contact Falaê team if you need to correct the duplication. Also review the installation of the same tool by other integrations and the triggers you published.
Does the test link also load the container?
Yes. Survey test mode does not turn off GTM. Published tags can be triggered during this access, according to your rules. If you need to separate testing from production measurement, agree filters with whoever is responsible for the container.
What identifier should I provide?
Use the Web container ID, prefixed with GTM-. Identifiers for other resources, such as the Google Analytics G- or Meta Pixel number, do not belong in the GTM ID field.
Why is the Configure button disabled?
Check the prefix, the number of characters and the use of capital letters. Remove spaces and re-copy the full container ID.
I connected the container, but the data does not appear. What to do?
Check to see if tags are configured, triggers match tested access, and version is published. A tag may work in Preview mode and not yet be published to other visitors.
Open the form again after configuring and confirm that you are testing a survey from the connected branch. Tracking blockers can prevent tags from loading. If the container does not load, inform Falaê team of the branch and the message presented.
Can I change tags without configuring them again in Falaê?
Yes. If the container ID remains the same, change the tags and publish the new version to GTM. To change the container, click Cancel integration in Falaê and configure it again with the new GTM ID.
When installing Meta Pixel via GTM, check whether the same pixel is already connected via Meta Pixel direct integration, to avoid sending duplicate events.
How to disconnect the integration?
On Falaê Integrations screen, open Google Tag Manager in the desired branch and click Cancel integration.
Falaê removes the container ID from that branch. When the form loads the updated branch data, the container stops being initialized by this integration, also stopping the tags that depend on it in these forms. Tabs that are already open keep the container loaded; close or reload the form to check the disconnection.
The action does not delete the container in your Google account or change its installation on other sites. If you want to turn off just one tag, you can pause it and publish the change to GTM, keeping the container connected to Falaê.