Check GA4 and GTM when conversions go missing
If purchases appear in GA4 but not in your ad conversions, inspect the tag’s firing conditions. Read the existing container in Neuro and review a proposal before publishing it.
On this page
GTM containers now connect to your Neuro workspace
Purchases appear in GA4, but Google Ads shows no purchase conversions. Before judging the campaign, check what fires the purchase tag and whether it receives the right value and currency.
Connect Google Tag Manager to Neuro to read an existing container’s tags, triggers, and variables and prepare changes. Reading the configuration does not prove that a tag fired on the live site. Use GTM preview and an actual purchase test to check behavior before and after a change.
How to connect: sign in with Google, then pick an account and container
- In the Data sources screen of your Neuro workspace, select Google Tag Manager.
- Sign in with Google and review the requested GTM permissions.
- From the list of GTM accounts you can access, choose the one to connect.
- From the containers under that account, pick the single container this workspace will manage.
- Once connected, you can query that container's tags, triggers, variables, and workspace structure in Neuro chats.
What you can check right after connecting
| What you can check | When marketers use it | Example question |
|---|---|---|
| Workspace list | Get context on in-progress drafts versus the live version. | Summarize this container's workspaces and the latest version status. |
| Tag list | See which names and types your Google Ads, GA4, and remarketing tags use. | Find the tags that look related to purchase conversions and show their firing triggers alongside them. |
| Trigger structure | Check whether event, page, and click conditions are too broad or too narrow. | Explain the purchase-related trigger conditions and blocking conditions in plain language. |
| Variables and parameters | Trace where values like value, currency, and transaction_id come from. | Find what's used as the purchase amount variable and the tags connected to it. |
Ask for a purchase-tag review
Paired with GA4, it's easy to start without dev knowledge
On its own, GTM can feel unfamiliar — tag types, trigger conditions, variable names. Connect GA4 to the same workspace and ad operators can speak in work terms, like 'I want to send the purchase event to Google Ads as a conversion,' while Neuro looks at your existing GA4 events and GTM structure together and lays out the tag, trigger, and variable changes you need.
Before publishing, drafts and versions are reviewed separately
GTM's model is to change tags, triggers, and variables inside a workspace, roll those changes into a container version, and then publish. Neuro respects that model as is. A draft change and a live publish are never treated as the same thing.
| Stage | What Neuro can do | What the operator checks |
|---|---|---|
| Structure lookup | Reads the container's workspaces, tags, triggers, and variables. | Start with diagnostics that have no live impact. |
| Drafting changes | Prepares create, edit, and delete requests for tags, triggers, and variables in a workspace draft. | Review target IDs, current values, and proposed values in a table. |
| Version creation | Bundles workspace changes into a container version. | Record the reason for the change in the version name and notes. |
| Publish | Publishes the container version after approval. | Before publishing, check preview, consent conditions, and rollback criteria. |
Sources
- Google Developers: Google Tag Manager API Overview
Official documentation confirming that the GTM API handles accounts, containers, workspaces, tags, triggers, variables, and versions as a hierarchy.
- Google Developers: Tag Manager API Authorization
Official documentation confirming that the GTM API uses OAuth 2.0 delegation and scopes, and that token and permission issues can surface as 401 and 403 errors.
- Google Developers: workspaces.create_version
Official documentation on the create_version operation that turns workspace changes into a container version, and the scope it requires.
- Google Developers: versions.publish
Official documentation on the publish operation that pushes a container version live, and the scope it requires.
Related posts
How to fill ad reports straight into Google Sheets
A guide for teams that run their client-facing and internal reports in Google Sheets: how to point Neuro at a URL, tab, and range in chat and let AI fill in the data for you.
Before you connect an ad account to Neuro
A guide to Neuro account connections, workspace access, default approvals and automatic execution, and AI API data policies.
Before AI changes your ad budget
How to review AI proposals for budget and bid changes, including approval settings and scheduled execution in Neuro.
How to ask AI when your ROAS numbers don’t match
Why attributed revenue can exceed actual sales, which dates and conversion definitions to align, and how to ask Neuro to investigate a ROAS discrepancy.