> For the complete documentation index, see [llms.txt](https://docs.limecall.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limecall.com/callback/install-with-google-tag-manager.md).

# Install with Google Tag Manager

Deploy the widget through GTM, with optional page targeting.

Use GTM if you already manage your marketing tags there, or if you cannot edit your site's code directly.

## Create the tag

1. Open your GTM container and go to **Tags → New**.
2. Click **Tag Configuration** and choose **Custom HTML**.
3. Paste your snippet from **Widget → Embed** in LimeCall.
4. Leave **Support document.write** unchecked.

## Set the trigger

1. Click **Triggering**.
2. Choose **All Pages** to show the widget site-wide.
3. Name the tag something recognisable, such as `LimeCall Widget`.
4. Save.

## Test before publishing

1. Click **Preview** in GTM and enter your site URL.
2. On the connected page, confirm the tag shows under **Tags Fired**.
3. Check the widget itself appears on the page.

## Publish

Return to GTM and click **Submit**, then **Publish**. Changes are not live for real visitors until you do this — a very common oversight when the widget "works in Preview but not in production".

## Targeting specific pages

You can restrict the widget using either GTM triggers or LimeCall's own display rules.

| Use                        | When                                                                      |
| -------------------------- | ------------------------------------------------------------------------- |
| **GTM trigger**            | You want the script not to load at all on some pages.                     |
| **LimeCall display rules** | You want the script everywhere but the widget visible only on some pages. |

LimeCall's rules are usually easier to change, because you edit them in the dashboard without republishing the GTM container. See [Display rules](/callback/display-rules.md).

To limit by GTM instead, create a **Page View** trigger with a condition such as *Page Path contains `/pricing`* and use that trigger instead of All Pages.

## Consent Mode

If you run GTM Consent Mode, decide whether the widget should fire before or after consent. The widget is a functional contact tool rather than an advertising tag, but the correct classification depends on your own privacy policy and jurisdiction. If you gate it behind consent, visitors who decline will not see a contact option at all — which is usually not what you want.