> For the complete documentation index, see [llms.txt](https://docs.talkfurther.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.talkfurther.com/google-tag-manager.md). # Google Tag Manager Marketing and analytics teams often want to track what happens inside Further-powered web experiences without repeatedly editing website code. Google Tag Manager (GTM) gives them a flexible way to install the Further script, route conversion events into downstream tools, and control where Further runs on the site. Key outcomes * A more centralized way to manage Further web tracking and script deployment. * Less reliance on direct CMS edits for every analytics or ad-platform change. * More flexibility for marketing and analytics teams to control where Further runs and how web conversions are measured. *** #### What it is and what it does GTM support in Further includes: **Script installation** * Install the Further script in GTM as a Custom HTML tag. * Set the tag to fire on `All Pages - Page View` when appropriate. * Use exception triggers to prevent VSA or related web experiences from loading on pages where they should not appear, such as careers, resident portals, legal pages, or billing pages. **Legacy GTM event tracking** * Further can push legacy events such as `FurtherLead` and other Further event names into the `dataLayer` for GTM-based tag setup. * Those events can be used to trigger GA4, Google Ads, Meta, Bing, and similar marketing or analytics tags from GTM. **Web Analytics Profiles** * Web Analytics Profiles provide a newer, more standardized tracking layer for supported web experiences. * These profiles emit structured events such as `lead_created` and `tour_scheduled` without requiring custom JavaScript for standard tracking setups. * This tracking is web-focused and does not cover phone or IVR conversions. **Further-hosted pages** * GTM or analytics scripts can also be supported on Further-hosted Landing Pages through the relevant landing page or hosted-page setup paths. *** #### What problem it solves Customers often need to solve a few common problems: * They want Further web conversions to appear in GA4, Google Ads, Meta, Bing, or other reporting tools. * They do not want to hard-code every script or tracking update directly into the website. * They need more control over which pages show Further experiences and which do not. Further’s GTM-compatible setup helps solve those problems by creating a flexible web tracking layer that marketing and analytics teams can manage more easily. It helps teams: * One flexible setup for script deployment and downstream tag management. * Easier analytics activation for supported web experiences through either legacy `dataLayer` events or Web Analytics Profiles. * Better control over page-level visibility using GTM triggers and exceptions. * Lower implementation friction for standard web analytics tracking. *** #### How it fits in the Further ecosystem GTM is part of Further’s broader web tracking and conversion infrastructure: * It can be used to install the Further script on customer websites. * It can support tracking for supported Further web experiences such as chat, Static Webforms, and Landing Pages. * It complements Web Analytics Profiles, which provide a newer standardized analytics model for supported web experiences. * It is separate from backend products like Google Ads Offline Conversions, which do not rely on GTM to upload offline events. *** #### Important notes * GTM is a supported installation and tracking path, but it is not required. Further can also be installed directly in site HTML. * Legacy `dataLayer` events and newer Web Analytics Profiles are related but different tracking approaches. * Web Analytics Profiles are web-only and do not track phone or IVR activity. * If the site uses NitroPack or similar optimization tools, Further scripts may need to be excluded from aggressive optimization to avoid duplicate loads, delayed loads, broken loads, or stale cached behavior. *** #### How to set it up **1. Prerequisites** * An active GTM container on the site. * GTM access for the person managing tags and triggers. * A Further account with the relevant web experiences enabled. **2. Enable or access it** To install Further via GTM: * Create a new tag in GTM using `Custom HTML`. * Paste in the Further script snippet. * Set the trigger to `All Pages - Page View` if the experience should load sitewide. * Add exception triggers if there are pages where Further should not appear. * Save and publish the GTM container. **3. Required setup steps** For legacy GTM event tracking: * Identify which Further events should trigger downstream analytics or ad tags. * Create Custom Event triggers in GTM for those event names. * Attach those triggers to the relevant GA4, Google Ads, Meta, Bing, or other tags. For Web Analytics Profiles: * Configure the relevant analytics profile for the supported Further web experiences being tracked. * Confirm whether tracking should run on customer-hosted pages, Further-hosted pages, or both. **4. How to test it’s working** Use GTM Preview or the relevant browser tools to confirm: * The Further script loads correctly on the intended pages. * The expected `dataLayer` events fire for legacy GTM tracking setups. * The correct downstream tags fire when those events occur. * Page-level exclusions work correctly where exceptions have been set. *** #### Integrations and configuration overview **Required** * GTM container on the customer website if GTM is the chosen setup path. * Further script snippet. **Optional** * Web Analytics Profiles for standardized tracking across supported Further web experiences. * GTM or analytics script support on Further-hosted Landing Pages when needed. **Key configuration options** * Where the Further script fires on the site. * Which pages are excluded through GTM exception triggers. * Which legacy Further events or standardized analytics events map to downstream tags and reporting tools. *** #### FAQs * **Can we install Further without GTM?** * Yes. GTM is a supported option, but Further can also be installed directly in site HTML. * **How do we hide VSA on specific pages?** * Use GTM exception triggers for the relevant URLs or page types so the Further script does not load there. * **Does GTM track phone conversions too?** * Not through Web Analytics Profiles. That tracking is web-only. Phone and IVR activity are handled through separate products and tracking paths. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://docs.talkfurther.com/google-tag-manager.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.