Datapipe
Marketers
See which channels and pages bring visitors who convert.
Read & reportRead-only source
See your Google Tag Manager numbers in Claude.
Read a container's published tags, triggers and variables, its version history and changes waiting unpublished.
- Paused tags, unused triggers and unpublished changes in one overview
- A live tag inventory for each client container
- Ask ChatGPT or Claude what changed in the container
ClaudeStart free Connect Google Tag Manager
Updated November 2026
| Tag name | Tag type | Firing triggers |
|---|---|---|
| GA4 - Google tag | Google tag | Initialization - All Pages |
| GA4 - purchase | GA4 event | Purchase - dataLayer |
| Meta pixel - base | Custom HTML | All Pages |
- SetupGuided setup
- Reads89 report fields across 6 datasets
- ChangesNone, read-only
- RefreshDaily to every 15 minutes
Who uses Datapipe with Google Tag Manager
Founders
Get a weekly traffic summary without opening another dashboard.
Agencies
Send each client the same clean traffic report every month.
What you can do with Google Tag Manager
Read and report
One container stays bound.
- Container overview
- Live tags
- Live triggers
- Live variables
- and 2 more
Read-only source
Datapipe reads Google Tag Manager data for reports. It never changes anything in Google Tag Manager.
Full read details
Reports show the container as it is now, so report dates do not filter them. Read-only access; nothing is edited or published.
Examples for your team
Catch paused and unused items
The overview counts paused live tags, triggers no tag uses and unpublished workspace changes.
- Scheduled refresh
- Latest Google Tag Manager data
- Updated report
Keep a tag inventory per client
List every live tag with its type, firing triggers and consent setting in a sheet you can share.
- Scheduled refresh
- Latest Google Tag Manager data
- Updated report
Before you connect
What you need
An API key or token from your Google Tag Manager account.
Read-only
Read access only. Datapipe never changes anything in Google Tag Manager.
Limits and exclusions
This is configuration, not traffic, so report dates do not filter it. Tag Manager reports show the container as it is now, so report dates don't filter them.
Full details and limits
One Tag Manager container: the published version's tags, triggers and variables, paused and unused items, saved version history and changes waiting unpublished in workspaces. This is configuration, not traffic, so report dates do not filter it.
Sign in with Google and allow read-only Tag Manager access (tagmanager.readonly). Datapipe never creates, edits or publishes anything in Tag Manager. Your other Google data sources keep their own separate sign-ins.
Tag Manager reports show the container as it is now, so report dates don't filter them. Google does not return when a version was published.
Reports you can build
6 reporting datasets, each with its own fields. Pick one in the app, then choose your columns.
- Container overview
- Live tags
- Live triggers
- Live variables
- Version history
- Unpublished changes
What each dataset reports
- Container overview
Read-only Tag Manager configuration for one selected container. Report dates do not filter it. One row for the container: its published (live) version, how many tags, triggers and variables that version runs, paused tags, and how many changes are waiting unpublished in workspaces.
- Live tags
Read-only Tag Manager configuration for one selected container. Report dates do not filter it. One row per tag in the published version, with its type, paused state, firing and blocking triggers by name, folder, firing option, consent setting and schedule. A container with nothing published returns no rows.
- Live triggers
Read-only Tag Manager configuration for one selected container. Report dates do not filter it. One row per trigger in the published version, with its type, folder and how many live tags fire or are blocked by it. A trigger no tag uses shows zero.
- Live variables
Read-only Tag Manager configuration for one selected container. Report dates do not filter it. One row per user-defined variable in the published version, with its type and folder. Built-in variables are listed by name with the type Built-in.
- Version history
Read-only Tag Manager configuration for one selected container. Report dates do not filter it. One row per saved container version, newest first, with the counts Google stores for it and whether it is the live one. Deleted versions are left out. Google does not return when a version was published.
- Unpublished changes
Read-only Tag Manager configuration for one selected container. Report dates do not filter it. One row per tag, trigger, variable or folder that a workspace has added, changed or deleted but not published, plus any merge conflicts. Workspaces with no changes return no rows.
Metrics and dimensions
89 report fields across 6 datasets.
Hover or tap a field to see what it means. Custom fields from your own account appear after you connect.
No fields match. Try another search or choose All.
Send Google Tag Manager data anywhere
Google SheetsA sheet that refreshes every morning.
Data StudioCharts that read the same numbers.
BigQueryA warehouse table for the same columns.
Excel / CSVA Drive file you can open in Excel.ClaudeAsk Claude about these numbers in a sentence.
ChatGPTAsk ChatGPT about these numbers in a sentence.
APIRead the same rows from your own tool.Don't see yours? Use CSV or APIDownload the rows, or read them from your own tool.Ask AI about your data
Claude or ChatGPT can read the same numbers. You ask in a normal sentence, and the answer stays with your report.
What is waiting unpublished in our Tag Manager container?
The default workspace has 3 unpublished changes: a new form-submit trigger, an updated GA4 purchase tag and a deleted test variable.
Better than exporting by hand
- It refreshes on its own, so nobody pastes in a new export.
- The same numbers can be split by who they came from.
Start from a goal
Container overview
Read-only Tag Manager configuration for one selected container.
Use this template →Live tags
Read-only Tag Manager configuration for one selected container.
Use this template →Live triggers
Read-only Tag Manager configuration for one selected container.
Use this template →Live variables
Read-only Tag Manager configuration for one selected container.
Use this template →How it works
Create a project and choose Google Tag Manager in Data sources.
Pick where it goes. This one sends the numbers to Claude.
Choose the account and container, then pick the report and where it goes.
Sample report
Sample live tags from one container's published version. Tag Manager reports show the container as it is now, so report dates don't change them.
| Tag name | Tag type | Firing triggers | Paused | Additional consent |
|---|---|---|---|---|
| GA4 - Google tag | Google tag | Initialization - All Pages | No | Needed |
| GA4 - purchase | GA4 event | Purchase - dataLayer | No | Needed |
| Meta pixel - base | Custom HTML | All Pages | Yes | Needed |
Sample numbers, so you can see the shape. Your report uses your accounts.
Works well with Google Tag Manager
Add both to the same project. Each keeps its own report, so you can check them side by side or ask ChatGPT or Claude a question that needs both.
Google Tag Manager + Search Console“Are search clicks and site visits moving together?”See Search Console →
Google Tag Manager + Shopify“Did more visits mean more orders this week?”See Shopify →
Google Tag Manager + Stripe“Did the traffic spike bring new paying customers?”See Stripe →
Google Tag Manager + HubSpot“Which weeks with more traffic also brought more deals?”See HubSpot →Questions
Free to start. Paid plans add more data sources and refresh faster.
Free and Starter refresh once a day. Pro refreshes every hour. Agency refreshes every 15 minutes on the first 50 data sources.
No. Name a project, add a data source, then choose a report and destination.
OAuth means you sign in with the service and grant access, without pasting an API key. Datapipe works with multiple partners to provide that sign-in. Some partners already provide it. Some integrations are API-only at present, so you paste a key or token. OAuth is coming soon for some. Some partners do not provide OAuth at all. The setup steps on each integration page say how that source connects. Signing in is only how the connection is made. It is not permission to change records. Where a source supports changes, those writes stay off until the workspace owner turns specific actions on and approves each one. We do not promise OAuth on every source, and we do not share dates.
This integration is read-only in Datapipe. You can report on Google Tag Manager, send the reports to your destinations and ask an AI assistant about them. Datapipe never changes anything in Google Tag Manager. Sign in with Google and allow read-only Tag Manager access (tagmanager.readonly). Datapipe never creates, edits or publishes anything in Tag Manager. Your other Google data sources keep their own separate sign-ins.
This page lists 89 report fields across 6 datasets. You pick the columns when you build the report.
One Tag Manager container: the published version's tags, triggers and variables, paused and unused items, saved version history and changes waiting unpublished in workspaces. This is configuration, not traffic, so report dates do not filter it. Account permissions and the records available from the provider determine which rows can be read.
One for each Google Tag Manager account you add to a project. Adding the same account to another project counts again. Reports and destinations do not use extra data sources.
Yes. The same numbers can go to a sheet, a chart, a warehouse, or an assistant.
Try Google Tag Manager with sample data first
Build the report first, then add Google Tag Manager when you are ready.