# How do the GTM metrics work on Fibr?

**Integrate Google Tag Manager(GTM) with the Fibr Dashboard.**

<figure><img src="/files/tdwWSIbZgJEw6mWy7jPx" alt=""><figcaption></figcaption></figure>

{% content-ref url="/pages/xbScfcqXQDmzk4JS9aNi" %}
[Integrate Google Tag Manager](/integrations/integrate-google-tag-manager.md)
{% endcontent-ref %}

Once approved, go to the Google Tag Manager workspace. You will find new tags created with the tag name in the format `fibr_{tag_name}`. Review and make sure that the duplicates for all the tags that you have selected are present, and then publish this new container version.

Once published, you are good to go!

## Tag Duplication and How Does Metric Tracking Work

This step is required for Fibr to track the exact same metrics that you are already tracking with your analytics tool. We do it in a way such that no customer data is received by Fibr, even if you have configured it in your original tag.

In tag duplication, Fibr creates a custom HTML tag on GTM, which informs Fibr's system once a metric is fired. In order to achieve the firing at the same time as your original tag, we create a trigger, which is a combination of your original trigger and a Fibr script load trigger.&#x20;

This compound trigger ensures that every time your original tag is fired, the Fibr tag also fires, thus maintaining data sanity across your analytics and Fibr analytics.

This way of setting up GTM ensures that Fibr does not miss any user activity you are already tracking and that the customer data remains intact within your systems.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://support.fibr.ai/tracking-and-analytics/success-metric-in-fibr-campaigns/how-do-the-gtm-metrics-work-on-fibr.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.