Feature request: Google Tag Manager source
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 39.9k
- Forks
- 3.4k
- Avg merge
- 6h 51m
- Merged PRs (30d)
- 232
Description
Feature request
Implement Google Tag Manager as a data warehouse source.
Current state: nothing exists as a warehouse source. No source directory, no registry entry, no scaffold. PostHog does ship a GTM CDP destination (#31658), which is a different surface and does not cover this.
Why: requested by a customer as a P1. GTM orchestrates all tags and eventing across their product, so container and tag configuration is part of the critical path they want observability over.
API reference: https://fivetran.com/docs/connectors/applications/google-tag-manager (for a schema comparison), Google Tag Manager API v2 for the implementation.
Suggested starting scope (confirm against the docs): accounts, containers, workspaces, tags, triggers, variables, and container versions.
Implementation guide: .agents/skills/implementing-warehouse-sources/SKILL.md. Update SOURCES.md as part of the PR.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read .agents/skills/implementing-warehouse-sources/SKILL.md first, then inspect existing warehouse sources and compare the Google Tag Manager API v2 with the linked Fivetran schema. Confirm the scope for accounts, containers, workspaces, tags, triggers, variables, and container versions; the work is done when the source is integrated and SOURCES.md is updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100