# Installing Trackingplan for ssGTM Docs DocsFor ssGTM [All docs](/docs) Get Started - [Overview](/docs/overview) - [How It Works](/docs/how-it-works) - [Your First Plan](/docs/your-first-plan) - [Post-Install Warm-Up](/docs/post-install-warm-up) - [Multi Account Management](/docs/multi-account-management) Install - [Installing Trackingplan](/docs/installing-trackingplan) - [For Websites](/docs/installing-trackingplan/installing-trackingplan-on-your-websites) - [For Apps](/docs/installing-trackingplan/installing-trackingplan-in-your-apps) - [Webhooks](/docs/installing-trackingplan/installing-trackingplan-using-webhooks) - [For ssGTM](/docs/installing-trackingplan/for-ssgtm) - [Environments](/docs/environments) - [SDK Update](/docs/sdk-update) The Agent - [Threads](/docs/threads) - [Reports](/docs/reports) - [Audits](/docs/audits) Use Cases - [Investigate a Warning](/docs/debug-warnings) - [For Analytics Teams](/docs/analytics-use-cases) - [For Performance & Paid Media](/docs/paid-media-use-cases) - [For Compliance & Legal](/docs/compliance-use-cases) - [For Agencies & Consultancies](/docs/agency-use-cases) Monitoring - [Warnings & Updates](/docs/warning-and-updates) - [Data Validation](/docs/data-validation) - [Data Layer Monitoring](/docs/data-layer-monitoring) - [Consent & Cookie Monitoring](/docs/consent-and-cookie-monitoring) - [Privacy Monitoring](/docs/data-privacy-monitoring) - [Pixel Monitoring](/docs/pixels-presence-monitoring) - [Naming Conventions Monitoring](/docs/naming-conventions-monitoring) - [Releases & GTM Monitoring](/docs/autodiscover-releases) Explore - [Explore](/docs/explore) - [Health Summary](/docs/health-summary) - [Data Explorer](/docs/data-explorer) - [Tracks Explorer](/docs/tracks-explorer) - [Presence Map](/docs/presence-map) - [Advanced Views](/docs/advanced-views) - [Session Finder](/docs/session-finder) - [Filters & Data Segmentation](/docs/attribution) - [Tags](/docs/tags) - [Notes & Labels](/docs/notes-labels) - [Starred Items](/docs/starred-items) - [Sharing](/docs/sharing) Your Trackingplan - [Destinations](/docs/destinations) - [Split Destinations](/docs/split-destinations) - [Events](/docs/events) - [Properties](/docs/properties) - [Attributes](/docs/user-attributes) - [Pages](/docs/pages) - [Compliance](/docs/compliance) - [Privacy](/docs/privacy) - [Consent](/docs/consent) - [Platform](/docs/platform) - [Daily Checks](/docs/daily-checks) - [Vitals](/docs/platform-metrics) - [Acquisition](/docs/acquisition) Connect - [Slack](/docs/slack) - [MCP Endpoint](/docs/mcp-endpoint) - [Ad Platforms](/docs/ad-platforms) - [Trackingplan Exploration API](/docs/trackingplan-exploration-api) - [Trackingplan Export API](/docs/trackingplan-export-api) - [Data Studio Connector](/docs/trackingplan-connector-for-data-studio) - [Chrome Extension](/docs/trackingplans-chrome-extension) - [Omnibug Extension](/docs/trackingplan-omnibug-extension) Account & Security - [Settings & Members](/docs/settings) - [Privacy & Security](/docs/privacy-and-security) - [JSON Export/Import](/docs/export-import-json-schemas) [Install](/docs) Updated July 14, 2026 # Installing Trackingplan for ssGTM Install the Trackingplan tag in your server-side GTM container, add our snippet to the tags you want to monitor and check it all works. > Before you start, we recommend talking to our [support team](mailto:support@trackingplan.com). They'll help you set everything up correctly from the start and avoid problems later. > To install it, you’ll need to: > > - [Install Trackingplan’s Tag](/docs/installing-trackingplan/for-ssgtm) > - [Add a snippet of code for the third-party templates you want to monitor](/docs/installing-trackingplan/for-ssgtm) ![When the Modified tag sends a request, it messages the Trackingplan Tag with a copy of the request, which then forwards it to the Trackingplan Server.](/images/spr-d78b04c0-attachment-84308fd0-9616-437f-aaa7-17c46752f752-CleanShot_2025-03-06_at_13.16.png) When the Modified tag sends a request, it messages the Trackingplan Tag with a copy of the request, which then forwards it to the Trackingplan Server. Prefer to watch? This video walks you through an installation from scratch: ## How to Install the Trackingplan Tag The Trackingplan tag captures GA4 requests and collects the messages from your modified tags, then sends it all to the Trackingplan server for monitoring. You have two options: install it from the Community Templates, or import it manually with the .tpl file. ### Manual Installation **Import the template into your SSGTM container** 1. Download the template from [https://github.com/trackingplan/trackingplan-ssgtm-tag/blob/main/template.tpl](https://github.com/trackingplan/trackingplan-ssgtm-tag/blob/main/template.tpl) 2. In your SSGTM container, go to Templates → New → Import from file ![](/images/spr-ac2b0b75-ssgtm_installation.png) ![](/images/spr-88c8c196-ssgtm_intallation_2.png) 3. Select the downloaded template file 4. Save ![](/images/spr-4d57a9b6-ssgtm_installation_3.png) **Create a new tag using the template**: 1. In your SSGTM container, go to Tags → New ![](/images/spr-373e2a40-CleanShot_2025-03-24_at_14.00.png) 2. Select the Trackingplan template ![](/images/spr-4019fec5-ssgtm_installation_4_4.png) 3. Add your Trackingplan ID ![](/images/spr-51d6f154-64ee3820-3c0c-4e11-8716-8f6e763f0101.png) 4. Set appropriate trigger rules (typically "All Events”, “All Pages") ![](/images/spr-bd22f050-CleanShot_2025-03-24_at_14.03.png) ![](/images/spr-a0ad77f0-CleanShot_2025-03-24_at_14.03.png) 5. Click Save 6. Publish your container > **Using Stape?** If your ssGTM container is hosted on Stape, Trackingplan detects it automatically. Just add your Trackingplan ID: there is no domain to configure by hand. ## How to modify the tags you want to monitor Do this on every template you want Trackingplan to monitor. 1. Open the tag template (this works on any tag) ![](/images/spr-2789befc-CleanShot_2025-03-06_at_13.18.png) 2. Add the Trackingplan Snippet to the top of the template ([see code below](/docs/installing-trackingplan/for-ssgtm)) ![](/images/spr-25d661ac-CleanShot_2025-03-06_at_13.19.png) 3. Remove/Comment the original `sendHttpRequest` and `sendHttpGet` methods. ![](/images/spr-dc29e214-CleanShot_2025-03-06_at_13.21.png) ![](/images/spr-43025afc-CleanShot_2025-03-06_at_13.22.png) 4. Enable the Send/Receive message permission ![](/images/spr-9fd0e464-CleanShot_2025-03-06_at_13.23.png) 5. Save ![](/images/spr-06dae4d3-CleanShot_2025-03-06_at_13.28.png) 6. Publish your changes ### Trackingplan Snippet ```javascript /* Trackingplan snippet to be included in on top of templates to be monitored by Trackingplan */ const sendHttpRequest = (url, options, body) => { require('addEventCallback')(() => { require('sendMessage')('tp_request', { url: url, body: body }); }); return require('sendHttpRequest')(url, options, body); }; const sendHttpGet = function (url, options) { require('addEventCallback')(() => { require('sendMessage')('tp_request', { url: url }); }); return require('sendHttpGet')(url, options); }; /* End of Trackingplan snippet */ ``` ### Using Custom domains > Many server-side tagging setups use first-party collection domains instead of the platforms' standard endpoints. If yours does, configure your custom domain with the `ssgtm` parser ID so Trackingplan can identify and parse those requests. Trackingplan recognizes requests sent to the standard collection domains of the analytics and marketing platforms it supports, automatically. Those domains map to **destination parsers**, which understand each platform's request format and turn the raw requests into the enriched event format you see across Trackingplan. If your implementation sends data to a custom collection domain instead of the platform's default one, Trackingplan can't identify it automatically. In that case, **configure the custom domain** when you install Trackingplan. To configure a custom domain, you need: - **The custom domain** that your implementation sends requests to (for example, your own collection domain instead of the platform's default endpoint). - **The parser ID** that tells Trackingplan which platform those requests belong to (for example, `ssgtm` for a server-side GTM endpoint or `tealium` for a Tealium Collect endpoint). > The parser value is **not** the name you'll see in Trackingplan. It is the internal identifier that tells Trackingplan how to read requests from that domain. For example, say your server-side GTM container receives requests at `metrics.example.com`. Trackingplan can't tell what that domain serves, so you tell it: ``` customDomains: [ { domain:"metrics.example.com", parser:"ssgtm" } ] ``` From then on, Trackingplan treats every request to `metrics.example.com` as a server-side GTM request and parses it with the `ssgtm` parser. Some common parser IDs include: | Platform | Parser ID | | --- | --- | | Server-side Google Tag Manager | `ssgtm` | | Stape | `stape` | | Tealium | `tealium` | | Adobe Analytics | `adobe` | | Adobe Target | `adobe_target` | | Jentis | `jentis` | | Piano | `piano` | These are only common examples. Not sure which parser ID fits your setup? Contact the [Trackingplan team](mailto:support@trackingplan.com) and we'll help you find it. ## How to debug & verify everything is running properly To check everything is running properly, look for the following in preview mode: ![](/images/spr-c5e83c87-CleanShot_2025-03-24_at_14.08.png) 1. Each time one of your modified tags sends a request (1 in the image), a Trackingplan request appears in its payload (2 in the image). 2. For each Incoming Request (3 in the image), there is a matching Trackingplan request (4 in the image). [← Previous**Installing Trackingplan Using Webhooks**](/docs/installing-trackingplan/installing-trackingplan-using-webhooks) [Next →** Environments**](/docs/environments) Was this useful? Write to [support@trackingplan.com](mailto:support@trackingplan.com) On this page 1. [*01*How to Install the Trackingplan Tag](#how-to-install-the-trackingplan-tag) 2. [*02*How to modify the tags you want to monitor](#how-to-modify-the-tags-you-want-to-monitor) 3. [*03*How to debug & verify everything is running properly](#how-to-debug-verify-everything-is-running-properly)