> 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/product/settings/developer-tools/tracking-scripts.md). # Tracking Scripts **Settings → Tracking Scripts** installs your analytics and tag-manager snippets — Google Tag Manager, GA4, VWO, Heap, and similar tools — on the pages your visitors see, with no engineering change and no theme edit. Paste the snippet once and PeakCommerce injects it into your public pages and journeys. Find it under the **user menu (bottom-left) → Settings → Tracking Scripts**, in the *Developer Tools* section. ## Why it matters Marketing and analytics teams usually queue behind engineering to get a tag-manager container installed or updated. Tracking Scripts removes that dependency: a system administrator pastes the vendor's snippet, saves, and it is live across the public buying experience — while the platform enforces the guardrails (who can author scripts, which surfaces run them, and which never do) so self-service doesn't become a security or privacy gap. The page is restricted to **system administrators** by design: whatever is pasted here executes verbatim in your visitors' browsers, so authoring access *is* the security boundary. ## Head scripts vs. body-start scripts The page has two fields, matching how analytics vendors split their install code: * **Head scripts** — injected as high in the page `` as possible (right after the charset declaration), which is what tag managers ask for. This is where the main `