A relaunched campaign has three switches, and all three have to be on. You flipped one, the status says enabled, and your phone is still quiet.
A relaunched campaign serves only when three separate switches are on: the campaign, its ad groups and its ads. Turning one layer back on leaves the other two as they were, so enabled on the top row can still mean nothing is running.
The short answer
- Campaign, ad group and ad each carry their own paused or enabled status.
- An ad serves only when its own status and the two layers above it say enabled.
- Enabling one layer is one step of a go-live.
- Reload the account after the change and check every layer. A confirmation message only says the request went through.
Three switches, three separate statuses
Each layer in a Google Ads account carries its own paused or enabled status. Google's own status reference lists a paused campaign, a paused ad group and a paused ad as three separate reasons an ad sits paused (the status reasons Google documents). An ad is shown only when its own status, its ad group's status and its campaign's status all say enabled.
Pausing can happen in pieces: a campaign paused to stop a problem, an ad group paused for a test, an ad paused after a wording change. Each of those pauses was sensible when it happened. After a few rounds of that, it is easy to lose track of which layers are still off.
Picture a lamp plugged into a wall socket. The lamp switch can be on while the room stays dark, because the wall switch or the breaker is off. Every switch on the line has to be on.
- Before
Three layers sit paused
The campaign, its ad groups and their ads each carry a separate paused status.
- After the change
Only the top row looks live
You just switched the campaign on and it shows enabled, so the job looks finished.
- On the read back
Layers below are still paused
A check of each layer shows the ad groups or the ads still holding the account silent.
What we got wrong with an expansion
We once enabled only the ad groups of an expansion and called it live. Nothing served, because the layers around them were still paused. Our written standard now says it plainly: never call an expansion live after enabling only the ad groups.
The confirmation said the change had been made. It had been. A confirmation tells you the request went through. It does not tell you what the account is now doing. The paused layers showed up only when we read the account back after the change.
The obvious suspects for a silent campaign are bids and ad approval. They are worth checking, but here the cause was a status sitting one layer down, doing exactly what it was told.
The same check caught two other mistakes. One was a mistake in a landing URL. The other was bids that were too round. All three had passed the confirmation. Each looked fine until we checked the account itself.
A go-live checklist for the three layers
Going live means enabling the campaign, its ad groups and their ads, and only then checking each layer on its own. The checklist ends with a status report because enabling and serving are different events, and only a report tells them apart.
Go-live checklist
-
Enable the campaign
Turn on the top layer and note the status it shows.
-
Enable the ad groups
Enable every ad group you intend to run.
-
Enable the ads
Inside each of those ad groups, so no layer is left holding the others back.
-
Read the account back
Pull the three statuses fresh from the account.
-
Check the rest of the build
Bids that are not round numbers, a landing URL that loads the right page, and ad copy that matches the website.
Order matters less than completeness. Turn the ads on before the campaign if you prefer. What you cannot skip is the read back.
The last step carries a few rules from our own standard for building campaigns. Manual bids are set when the campaign is built, before any later tuning. They are set to the cent and never land on a whole or a half, and the ad group default bid is de-rounded the same way. Ad copy matches the phrasing the website can back, so a training-based credential is never upgraded to a license, and insured is not the same as licensed. No star ratings go in an ad while review data is empty.
If you would rather hand this build to a team, our paid search work follows this list, and how we build Google Ads campaigns is laid out on its own page.
Read the account back, then trust it
A status report beats a status screen. For an owner working in the Google Ads interface, reading the account back means reloading it and checking the status of every ad group and every ad, campaign row included, or asking whoever runs the account for that list. Look for anything still paused.
Do it twice. Once right after the change, to catch the paused layer. Once again after the account has had time to run, to see that the layers you enabled are still enabled and that impressions are arriving. The point of the second look is that a layer enabled today can be paused again by the next edit.
A confirmation tells you the request went through. It does not tell you what the account is now doing.
You can ask for the report in plain words. How many ad groups are enabled, how many ads, and which ones are paused? If whoever runs your account cannot answer in one message, that is worth a follow-up question.
We think most silent failures live in the gap between what a setting says and what is really shown. Two other posts rest on the same idea: keep the thing that matters where the reader will find it, and check what is really shown. The quarterly check on whether AI answers mention your business reads what the system says. What belongs in a video on a service website keeps what matters in the page itself, where the reader will find it.
This post was drafted with AI tools from our own project records, anonymized, and checked by us before it published. Read our editorial standards.
