> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/guides/administration-guides/guide-installing-analytics-and-tag-manager-scripts.md). # Guide: Installing Analytics and Tag Manager Scripts ### Overview PeakCommerce can inject your analytics and tag-manager snippets — Google Tag Manager, VWO, GA4, Heap, and similar tools — into the pages and journeys your visitors see. You paste the snippet once; PeakCommerce places head scripts as high in the page `` as possible (what GTM asks for) and body-start snippets (like the GTM `

window._vis_opt_queue = window._vis_opt_queue || []; window._vis_opt_queue.push(function () { _vis_opt_goal_conversion(<your-goal-id>); }); , )` on the final/success step to register the funnel completion. **Google Tag Manager example.** Either approach works — pick one per tool: * *Step-level snippet* — push a dataLayer event on each step's page, and build your GTM triggers on those events: ```html ``` * *Element-visibility trigger* — keep just the main container tenant-wide, and configure GTM triggers that fire when a step's element becomes visible (for example the billing form or the confirmation box). GTM does the step detection client-side. **Worked example — a three-step signup in VWO.** Say your signup journey has three steps: **Contact info**, **Billing**, and **Confirmation**, and you want a VWO goal recorded when a visitor reaches each one. First, put your **main VWO snippet** at the tenant-wide level (Section 1) so the VWO library is loaded on the page. Then add one snippet per step: in the **journey editor**, click each step and use its **Tracking scripts** section (Section 3). *On the Contact info step:* ```html ``` *On the Billing step:* ```html ``` *On the Confirmation step:* ```html ``` The result: as a visitor advances through the flow, VWO records goal **200** when they reach Contact info, **201** at Billing, and the funnel completion (test **5**, goal **21**) at Confirmation — each once per visitor, all on the same unchanging URL. Replace the goal and test ids with your own from VWO. ### 5. Tracking on the signed-in customer portal (optional) By default, **no scripts run behind login** — not even your tenant-wide default. If you want product analytics (for example Heap) on your customers' portal experience: 1. Go to **Settings** → **Tracking Scripts**. 2. Enable **Customer portal tracking** and save. Treat this as a deliberate decision: trackers on authenticated pages observe *identified* customer activity, and your organization owns the corresponding privacy disclosure to your customers. The switch is off until you turn it on, and page/journey snippets follow the same gate. ### 6. Verify your setup 1. Configure your snippet on staging first (Section 2). 2. Open your public signup or storefront page on the staging domain and use your tool's preview mode (for example **GTM Preview** or the **VWO** editor) to confirm the container fires. 3. For a multi-step flow (Section 4), step through the journey and confirm each step's event fires as you arrive at that step — and that events land in your **staging** property or account, not production. 4. Once staging looks right, open this page on your **production** site and paste the production snippet there. ### Troubleshooting * **My script doesn't fire.** Check you saved it on the same environment you're testing — staging and production are separate sites with separate scripts, so saving on one never affects the other. Also confirm you're viewing the page as a visitor or customer: admin and CSR sessions never execute tenant scripts. * **Nothing fires on the customer portal.** Enable **Customer portal tracking** (Section 5). * **My page-level snippet fires twice?** It shouldn't: injection is deduplicated per loaded page, including when a journey revisits a step. If you see double events, check whether the same snippet is pasted at two levels (tenant *and* page) — the levels stack. --- # 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.peakcommerce.com/guides/administration-guides/guide-installing-analytics-and-tag-manager-scripts.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.