Overview
GTM Pixel is the recommended Google Tag Manager setup for Octanist. It loads the Octanist pixel from a GTM Custom HTML tag, then lets the pixel capture sessions, page views, click IDs, consent state, and form activity.
GTM Pixel and GTM DataLayer
Use GTM Pixel when GTM is the easiest place to install website scripts. Use GTM DataLayer when your website already pushes clean lead events and lead fields into the dataLayer. Both setups remain supported, but GTM Pixel is the normal path for new installs.
How it works
Copy the Octanist pixel script from Pixel Setup, paste it into a GTM Custom HTML tag, and fire it on all pages. The pixel then manages the browser session and attribution capture. If a backend form submission sends the hidden session ID, Octanist can still link that server-side lead to the same GTM-loaded pixel session.
Use cases
Pixel through GTM
Install the Octanist pixel without changing website templates or asking a developer to deploy code.
DataLayer support
Keep using a dataLayer-based setup when your website already pushes reliable lead events and fields into GTM.
Attribution capture
Capture GCLID, FBCLID, MSCLKID, UTMs, referrers, landing pages, and page views through the pixel session.
Version control
Use GTM preview, publishing, and version history to test the pixel before pushing it live.
Conclusion
GTM is a practical install path when script management already lives in Tag Manager. For most new GTM installs, use GTM Pixel. Keep GTM DataLayer for sites that already have a reliable lead event pushed into the dataLayer.
