Skip to content
Help Center

Follow the result of a Google publish ​

Step 5 of the Deployment Wizard for Google is Result. It opens when you press Publish on Review and publish. It lists what Commander created in your Google Ads account, reads each status from Google, and lets you switch the ads on, send failed ads again and save the setup. See Review and publish Google ads with the Deployment Wizard for step 4. The Meta page works the same way: see Review and publish Meta ads with the Deployment Wizard.

Problem and intended user ​

A media buyer (the person who runs your paid ads) has published ads to Google and needs to know which campaign, ad group and ads now exist, which are paused and whether Google refused any. Without that, a paused campaign is easy to forget, and a refused ad goes unnoticed. The ecommerce manager (the person who runs the store) wants to know whether the ads are running.

Current workflow ​

The media buyer opens Google Ads, finds the new campaign, ad group and ads, checks the status of each object and switches each level on by hand.

Prerequisites ​

How Commander works ​

Commander builds the table from its own record of the publish and from the status that Google Ads reports. Fixed rules, not AI, produce it. Reading a status changes nothing in Google Ads.

While the ads go out ​

A progress line shows how many ads Commander has made and how many are out, with the time so far and "about N s left" (minutes once it is over a minute). Publish log lists each action and folds when the publish is done. If you close or reload the tab while ads are made or sent, the browser asks first. Other pages in Commander do not ask: the activity chip, which names Google, follows the publish to them. A reload brings step 5 back.

Read the status from Google ​

Commander reads the status from Google as soon as an ad is out, after Switch on and when you select Check again. It also keeps reading while the ads are being published and while Google has not decided on an ad. If Google asks Commander to slow down, the automatic reads stop until you select Check again. Check again shows when it last read.

Switch on ​

WARNING

Switch on can start spending once Google approves the ads. The confirm names everything it turns on.

  1. Select Switch on. The button names what it turns on, for example Switch on campaign, ad group and 1 ad or, for Performance Max, Switch on campaign and asset group.
  2. Read the confirm. It names the ads, the daily budget Commander knows and each campaign or ad group it also turns on, and says that Google reviews the ads first, then they start spending. For Performance Max the confirm says "The asset group goes live", because the asset group is the ad. When the campaign goes on around an ad group that is already on, the confirm also says how many other active ads in the ad group start delivering too.
  3. Select Switch on in the confirm.

Switch on turns on only what this publish made, and the campaign or ad group that step 3 or this publish made. It never starts other paused ads in a campaign you picked. It does not appear after Publish and go live after review, because that publish already switched them on. If you pause the campaign or ad group in Google Ads after Switch on, the card offers Switch on again with the note "Paused in Google Ads after you switched it on." The line under the heading says what holds the spend, for example "The campaign is paused. Nothing spends until you switch it on." It says "Everything is paused" only while every row reads Paused. A campaign or ad group you made yourself and left paused stays paused. The page names it, with a link, and says the ads will not run until you resume it in Google Ads.

Send failed ads again ​

A publish can partly succeed, because Display ads per creative go out one at a time. A button names what it sends again, for example Retry the failed ad, Retry the N failed ads, Retry the N skipped ads or Retry the N failed and skipped ads. Failed means Google refused the ad or Commander could not make it. Skipped means the batch stopped before that ad went out. Retry sends those ads only. The ads that went out stay.

An ad that you left out on step 4 shows "Left out" with its reason and Fix and publish. It opens Review and publish with that ad alone.

Save as setup ​

Save as setup keeps the destination, the format and the call to action for your next publish. It does not keep the copy. The name starts as the campaign and ad group, for example "Spring sale · Autumn ad group", or the campaign alone for Performance Max. You can change it. If you type a name another setup already uses, the field says "A setup named "..." already exists. Pick another name." and waits for a different one; Commander does not add a number to a name you typed. Ads offers the setup first next time. Separately, Commander keeps your destination as Last used for Google when a publish ends with at least one ad out. See Set the Google campaign and ad group in the Deployment Wizard.

Leave the page ​

  • Start over clears the page and begins a new deployment. Nothing is undone on Google: the paused campaign and ad group, and the ads that went out, stay.
  • Back to review returns to step 4 after a stop, with your edits kept.
  • Also publish to Meta appears when the publish is done. It starts a new run with the same creatives and Meta as the platform, and steps 2 to 4 start fresh. It is greyed, with the reason beside it, when Meta is not connected or your access is view-only.

Exact output ​

The heading reads Publishing to Google while the ads go out, Published to Google when they are out, and, for a partial publish, for example "Published to Google, 1 of 3 ads". If it stopped, it reads Publish stopped. Under a finished heading: "Google must approve the ads before they run." Commander states no review time. Google explains how its review works on its own page: How Google Ads reviews ads.

What Commander created is a table with the columns Object, Name, Google ID, Status and Actions. When a publish stopped before any ad went out, the campaign row still shows the status Google reports, so a paused campaign reads Paused; if Google does not report an object, its row reads "Status unknown" rather than an "Active" that Commander stored earlier. Each row has a Google Ads link that opens the object in your Google Ads account. A row for an ad opens its ad group's list of ads, and the asset group row opens the campaign's asset groups. If you manage several accounts, Google Ads may first show its account picker.

FormatRows
Performance MaxThe campaign, then one asset group row. The asset group is the ad, and its note counts the images, headlines, long headlines and descriptions.
Demand Gen ImageThe campaign, the ad group and one ad, for example "Image ad, 8 images".
Demand Gen CarouselThe campaign, the ad group and one ad, for example "Carousel, 5 cards".
Responsive Display Ad, 1 ad per creativeThe campaign, the ad group and one row per ad, named "Ad 1" and so on with the product title.
Responsive Display Ad, 1 ad from all creativesThe campaign, the ad group and one ad, for example "Responsive display ad, 8 images".

Status follows each object's own switch, as on Meta:

StatusMeaning
Paused or ActiveThe object's own switch in Google Ads. Each row reads its own switch, not the state of the row above it: an ad or ad group you switched on reads Active even while its campaign is paused, and it serves only once the campaign is on too. An ad you switched on also reads Active while Google reviews it.
RemovedThe object was removed in Google Ads.
Approved (limited)The ad's own switch is on and Google approved it with a limit, as Google Ads words it. It can run once its ad group and campaign are on.
Disapproved (red)Google refused it. Open it with Google Ads to read why.
Waiting, SendingThe ad has not gone out yet.
Failed with a reasonThe ad did not go out.
Skipped with a reasonThe batch stopped before this ad.
Left out with a reasonYou held it back on step 4.

Below the table are the Switch on and Save as setup cards once the publish has ended, then Publish log.

What to do with it ​

What you seeActionOwner
Published to Google with rows PausedSelect Switch on when you want the ads to run. Google must approve them first.media buyer
A paused campaign or ad group that you madeSwitch it on in Google Ads with Open the campaign or Open the ad group.media buyer
DisapprovedSelect Google Ads, read Google's reason and fix the ad.media buyer
Left out with Fix and publishFix the ad on Review and publish, then publish it.media buyer
Also publish to MetaRun the same creatives through the Meta steps.media buyer
A finished publishSelect Start over to deploy more creatives.media buyer

Expected value and measurement ​

To check the ads once they run, open Performance > Ad performance and read Spend and ROAS for them. You cannot isolate the effect of the wizard when other creative, budget or audience changes ran at the same time. See Ad performance.

Limitations and exceptions ​

  • Google decides when the ads run. An ad can read Paused or Active while Google has not yet approved it. Only a refusal shows in red.
  • Older publishes. Switch on does not work after a while. The message says "This publish is more than 7 days old. Switch the ads on in Google Ads."
  • Notes about extras. When Google took an ad but did not apply an extra, for example an audience signal, the note stays on the ad's own page, not here.
  • A restart during a Performance Max retry. If Commander restarts while a Performance Max publish is failing and you then press Retry, Google Ads may get a second paused campaign. Delete the one you do not need in Google Ads.

When something fails ​

MessageWhat to do
"Nothing went to Google"The message lists the error and each ad that could not be made. Select Back to review, change the ads and publish again. Your edits are kept.
"Google returned" followed by a reason, then "Your edits are kept."The publish stopped. The paused campaign and ad group from step 3 stay, and so do the ads that went out. Select Back to review or Retry publish.
"Google already has an asset group named "…" in this campaign. Retry uses a new name." (an ad group for Demand Gen and Display)Another asset group of the campaign was made with that name after step 3 read it, for example by a second publish. Select Retry: Commander numbers the name ("#2") and sends it again.
"Google was busy and asked Commander to slow down. Retry sends it again."Select Retry after a moment.
"Switch on failed" beside a rowRead the reason, then select Switch on again.
"Commander could not check Google just now, so it cannot confirm the campaign is on." (or "the ad group")Google did not answer when Commander checked the campaign or ad group, so Commander did not report it as on. Open it in Google Ads to see whether it runs, then select Switch on again.
"Some ads may already be on. Check Google Ads, then try again." or "Couldn't switch them on. Nothing changed on Google. Try again."In the first, a later switch failed after an earlier one worked: check Google Ads first. Then select Switch on again.
"Couldn't check with Google. Showing the answer from …"The table keeps Google's last answer. Select Check again in a moment.

Demo Mode ​

The page shows a Sample data badge next to the heading. Demo Mode creates nothing on Google. The Result step plays a sample publish, the Google IDs are stand-ins, and no row links to Google Ads. It has no Check again and no activity chip, because Demo Mode reads nothing from Google. Switch on asks first, then changes the rows on the page only. Save as setup answers "Demo Mode keeps no setups."

Commander is built by Omniconvert.