Analytics & tracking · 3 min read
Google Tag Manager on your Electbase site — your responsibilities
Electbase lets you paste your Google Tag Manager container ID (GTM-XXXXXXX) and bakes Google's standard snippet into your published site. That's all Electbase does — the container, and everything that runs inside it, is yours. Because tags execute under your Google agreement, the obligations below sit with your campaign, not with Electbase.
The terms you're operating under
Your container is governed by Google's Tag Manager Terms of Service and Use Policy (linked from your GTM account and from the Connections card). The two obligations campaigns most often trip on:
- No personally identifiable information (PII) in tags. Never configure a tag, variable, or data-layer value that passes names, email addresses, phone numbers, or precise addresses to Google Tag Manager or through it to analytics/ad platforms. Supporter form data on your Electbase site is NOT exposed to your container by Electbase — keep it that way in anything you add.
- European-visitor consent. Google's EU User Consent Policy makes the container owner responsible for obtaining legally required consent for cookies and ad personalization. Electbase's sites emit a consent default before your snippet loads (denied-by-default categories wired to the site's cookie banner), and your tags must respect those consent signals — don't configure tags to fire regardless of consent state.
What this means practically
- Use Google's built-in tag types where possible; audit any custom HTML tag before publishing it — that's arbitrary JavaScript on your donors' browser.
- If an ad platform asks you to send "enhanced conversions" or hashed emails, stop and get advice first — that is exactly the PII line above.
- Political-ads policies (Google Ads, platform-specific) apply to what your tags do downstream; verification requirements there are yours to meet.
- If Google suspends a container for policy violations, that's between you and Google — Electbase can only remove the container ID from your site.
What Electbase does and doesn't do
| Electbase does | Electbase does not |
|---|---|
| Validate the container ID format and bake Google's snippet at publish | Create, own, audit, or administer your container |
| Emit the consent default BEFORE your snippet | Guarantee your tags honor consent — configure them to |
| Show "Container active" / "No container set" honestly (never "Connected") | Pass supporter PII to your container |
Not legal advice. Electbase publishes the Help Center as general information for campaigns. Google's terms, its Use Policy, and consent requirements change — confirm current details directly with Google, and get your own advice on your campaign's privacy obligations. Questions? Ask support before you publish a tag you're unsure about.