Connecting Google Tag Manager to your Electbase site
Paste your Google Tag Manager container ID into Electbase and, from your next publish, Google's standard Tag Manager snippet is on every page of your site. Your digital team then runs pixels and analytics tags from inside Tag Manager without touching your site. Electbase sets a consent default before the snippet loads, so no non-essential tag fires before a visitor has made a cookie choice. Available on Grassroots and above.
Finding your container ID
Sign in to Google Tag Manager and open your container. Its ID is shown at the top of the workspace and looks like GTM-XXXXXXX: the letters GTM, a hyphen, then capital letters and digits. Copy it exactly.
Connecting it in Electbase
- From your dashboard, open Connections in the top navigation and find the Google Tag Manager card.
- Paste the ID into GTM container ID and click Save setup. Electbase checks the format and the card reads Container active.
- Publish your site. The snippet is added at publish time, so nothing changes on your live site until you do.
If you change the ID later, publish again. The card never reads "Connected," because this is not a connection: Electbase holds no Google credential and makes no call to Google. It bakes a snippet.
What Electbase puts on your pages
Two things, in a fixed order:
- A consent default, as an inline script high in the page. It tells Google's tags that advertising storage, analytics storage and other non-essential storage are denied until the visitor says otherwise, and that only strictly necessary storage is allowed. Your site's cookie banner then updates that consent when the visitor makes a choice.
- Google's Tag Manager snippet for your container, immediately after the consent default, plus Google's standard no-script fallback at the top of the page body.
The order matters: a tag that fires when the container loads sees the denied defaults first. Configure your tags to respect consent signals rather than to fire regardless.
The snippet goes on every page of your site with one exception: Issue Poll pages never carry it, whatever your container does. A respondent's own answers are live on that page, and no third-party container should be able to see them.
Your responsibilities as the container owner
Everything inside the container is yours and runs under Google's Tag Manager terms, not Electbase's: no personally identifiable information in tags or the data layer, EU consent compliance, and the political-ads policies of whatever platforms your tags talk to. Supporter form data on your site is not exposed to your container, and you should keep it that way in anything you add. Google Tag Manager on your Electbase site: your responsibilities spells this out, and the card links to Google's Use Policy.
Removing it
Click Disconnect Google Tag Manager on the card, then publish. A removed container bakes nothing; the snippet disappears from your pages on that publish.
Checking it works
Electbase has nothing to test against Google here, so the check is yours: after publishing, open your live site with Tag Manager's preview mode and confirm the container loads and your tags behave as you expect under both consent states.
Quick checklist
- Copy your container ID (
GTM-XXXXXXX) from the top of your Tag Manager workspace. - On your Connections page, paste it into the Google Tag Manager card and click Save setup.
- Publish your site.
- Read your responsibilities as the container owner, and set your tags to respect consent.
- Check the container in Tag Manager's preview mode on your live site.