Three places a relaunched campaign can still be paused

You switched the campaign back on, 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

• Pauses travel downward: a paused campaign keeps its ad groups and their ads from running.
• A confirmation message says the request went through, not what the account is now doing.
• Read the statuses back twice: right after the change, and again once the account has run.
• A layer enabled today can be paused again by the next edit, which is why the second look matters.

Only the campaign switched back on

1. 1 Campaign Enabled
2. 2 Ad group Paused for a test Still paused
3. 3 Ad Paused after a wording change Still paused

Nothing is running

All three switched on

1. 1 Campaign Enabled
2. 2 Ad group Enabled
3. 3 Ad Enabled

Serving

Every switch on the line has to be on.

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).

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.

The pauses also travel downward. Google's help page on ad group status says an ad group inherits the paused status of its campaign, and it lists a paused ad group or a paused parent campaign as a common reason ads are not running (the ad group status page).

Tap a card

• Campaign Why it was paused To stop a problem What to read back The campaign row's own status

  Campaign What to read back The campaign row's own status
• Ad group Why it was paused For a test What to read back The status of every ad group you intend to run

  Ad group What to read back The status of every ad group you intend to run
• Ad Why it was paused After a wording change What to read back The status of every ad inside those ad groups

  Ad What to read back The status of every ad inside those ad groups

Each pause made sense when it happened. Each one has to be undone and checked on its own.

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. In an account, the trap is the moment right after the change: the top row shows enabled, the job looks finished, and a layer below is still holding everything 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 read back caught a mistake in a landing URL and bids that were too round. Both had passed the confirmation too.

What the confirmation told us

• The change had been made
• The ad groups we touched showed enabled
• The expansion looked live

What the read back showed

• The layers around those ad groups were still paused
• A mistake in a landing URL
• Bids that were too round

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

1. 01

   Enable the campaign

   Turn on the top layer and note the status it shows.

2. 02

   Enable the ad groups

   Enable every ad group you intend to run.

3. 03

   Enable the ads

   Inside each of those ad groups, so no layer is left holding the others back.

4. 04

   Read the account back

   Pull the three statuses fresh from the account.

5. 05

   Check the rest of the build

   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 that page lays out how we set up Google Ads campaigns.

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. The quarterly check on whether AI answers mention your business is the same move: read what the system shows, not what the setting says. So is opening the sitemap after a build, which is how a lastmod date repeated on every page gets caught. A check that cries wolf teaches people to ignore it, which is how a silent failure slips through, as an alert that cries wolf stops being read shows. Reading the Google Ads IP exclusion list itself, instead of trusting that it saved, is one more case.

Before you call a relaunch live

• Enable the campaign, every ad group you intend to run, and the ads inside each of them.
• Reload the account and check the status of every layer, campaign row included.
• Ask whoever runs the account for the count of enabled ad groups and ads, and the list of anything still paused.
• Open each landing URL and confirm it loads the right page.
• Check the statuses again once the account has run, and confirm impressions are arriving.

Ready to call it live

This post was drafted with AI tools from our own project records, anonymized, and checked by us before it published. Read our editorial standards.