Google Tag Manager
by Google
Google Tag Manager data is metadata rather than traffic: containers, tags, triggers, variables and published versions show what fires on which site and when it changed. Analytics teams need that audit trail when numbers move. With container versions in the Lake beside GA4 and ad platform data, a sudden drop in conversions can be traced to the publish that caused it.
- Category
- Analytics & Attribution
- Type
- Tag management & tracking plans
- Interface
- REST API
- Built with
- Connect Any API
- Credentials
- OAuth 2.0, Service account key
02Data
What you can sync.
- Containers
- Tags
- Triggers
- Variables
- Versions
Join Google Tag Manager containers with orders, subscriptions and CRM data, so a question about growth gets one answer instead of three dashboards.
Need more? Name any other Google Tag Manager data the API returns, and the AI adds it to the connector.
03Credentials
Credentials you will need.
- OAuth 2.0 (client ID, client secret, refresh token)
- A service account key
Google Tag Manager uses OAuth 2.0 (client ID, client secret, refresh token) or a service account key. You add the credentials once, when the AI asks for them, and it tells you where to create them in Google if you need help.
04Questions
Questions you can answer.
Once Google Tag Manager data is in your Lake, ask an AI Mind in plain words or build the answer in DataPrism BI.
- Which container versions were published in the week our purchase events dropped?
- How many tags fire on all pages, and which vendors do they load?
- Which tags have not changed in two years and may no longer be needed?
- How many tags, triggers and variables changed in each version published last month?
- Which triggers are shared by marketing pixels and analytics tags?
05How it works
How it works in DataMind.
-
Pick Google Tag Manager.
Open Lake, pick Google Tag Manager in the source picker and name the connection. Connect Any API opens with a ready prompt that points the AI at the Google Tag Manager API docs.
-
Answer a few questions.
The AI reads the Google Tag Manager documentation, then asks which credentials you will use, which data to sync (for example containers and tags), whether you want a one-time load or a recurring sync, and which accounts or filters apply.
-
Your data lands in Lake.
It builds the connector, tests it and shows you sample rows. Then Google Tag Manager data loads into your Lake on your schedule, ready for the Warehouse, DataPrism BI and AI Minds.
06Pairs
Works well with Google Tag Manager.
Sources teams join with Google Tag Manager in the Warehouse, each one connected the same way.