ReferenceTracking error
Awaiting conversions
Google Ads recorded no conversions for that action in the last 7 days. Sometimes that is true: a new action, paused campaigns or little traffic. Often it is not: the form, the thank-you page or the import changed and nothing reported it. Compare against your own lead records, then send a real test conversion through Tag Assistant before trusting the zero.
At a glance
- Where it shows
- The Status column under Goals, Conversions, Summary. The older tracking status wording for the same thing is No recent conversions.
- What stops
- No ad stops. Any bid strategy that uses this action sees no results from it and bids on that basis.
- How serious
- No policy risk. The cost is budget and bidding decisions made on a count that may be wrong.
- How long
- Google says actions verified in a Tag Assistant session update in the account after about 30 minutes.
What it means
Google defines the status as no conversions recorded in the last 7 days, and gives three usual reasons: the action was created less than 48 hours ago, the campaigns are paused, or website traffic is too low.
What the status cannot do is tell a quiet week from a broken setup. Google can see that its tag is on the site; it cannot see that the tag stopped firing at the moment a lead happens. That is why the status is worth checking every time it appears, and why it is different from Misconfigured, where Google has already detected that recording stopped.
What actually triggers it
A new action, paused campaigns or low traffic
Google's three reasons, and the only ones where the zero is real. Check them first because they take a minute.
The thank-you page changed or disappeared
Not on Google's help page
Many conversion tags fire when someone reaches a thank-you page. A website update that swaps the redirect for a message on the same page, or renames the page, leaves the tag installed and silent. Nothing errors; the status only changes once 7 quiet days have passed.
A new form tool the tag cannot see
Not on Google's help page
Replacing the form with a booking widget or an embedded form from another service often moves the submission inside a frame from another domain, where a Tag Manager trigger on the page never hears it.
A Tag Manager change that was never published
Not on Google's help page
Edits made in a Tag Manager workspace do nothing until a version is published. The reverse also happens: a later publish from an old workspace quietly removes a working trigger.
An import that stopped sending
Not on Google's help page
For actions fed by uploads, such as calls from a call tracking service or sales from a CRM, the status describes the upload, not the website. A disconnected integration or an expired sign-in on the other system stops the conversions while the website tag looks fine.
A cookie banner that blocks the tag
A banner set to load Google's tag only after someone accepts leaves every visitor who ignores or declines the banner unrecorded. Google's consent mode exists to send what consent allows instead of nothing.
Fix it in this order
- Count the leads from paid clicks in your own records for the same 7 days: form emails, booked calls, the call tracker's log. If there were none, the status is probably right and the question is traffic, not tracking.
- Confirm the action is more than 48 hours old and its campaigns are running and spending.
- Hover over the status, click Troubleshoot, then Continue, and enter the page where the conversion starts. Tag Assistant opens; complete a real form or booking on the live site, then click Finish.
- If the test does not register, fix the trigger: the thank-you page address, the form submission event, or the frame the form sits in. Publish the Tag Manager container and run the test again.
- If the action is an import, open the system that sends it and check its connection to Google Ads and the time of its last upload.
Once a real conversion arrives the status changes to recording. Conversions are filed under the date of the ad click, so the missing days may fill in for clicks that happened before the fix.
Often confused with
Misconfigured
Google has detected that recording stopped because of a setup error or a broken tag. Hover over the status for Google's next steps.
Needs attention
Conversions are still recording, but Google has found something to fix, such as a tag missing from some pages.
Unverified
Google has not yet confirmed that the tag is on the website at all.