Ask Advisor in Google Ads: A Practical Guide to the Beta

Start with a question you can check

Look for the Ask Advisor beta icon near the top right of an eligible Google Ads account. It opens a conversation panel. Google's current Help page excludes manager accounts, so an agency should check inside the relevant client account. Availability is not proof that every announced capability has reached that account.

The documented jobs include performance analysis, reports, troubleshooting and creative suggestions. Begin with work you were going to do anyway. For example: “Compare our Non-brand Search campaign over the last two complete weeks. Show spend, conversions and cost per conversion. Which change in the numbers deserves a closer look?” This is an example prompt, not a promise about the exact report format.

Naming the campaign and period makes a vague answer easier to challenge. Ask follow-up questions where something is missing. A broad request such as “optimize the account” gives you much less to evaluate, especially if you have not supplied the business goal or constraints.

An explanation should survive a look at the reports

Suppose the answer attributes higher cost per lead to a recent budget increase. Start by checking whether the increase happened, when it happened and whether spend actually rose. Then look for competing explanations: a different mix of searches, a change in conversion measurement, a promotion ending, or leads that have not yet been recorded.

The timing may support the explanation without proving it. A budget change and worse results in the same week do not isolate cause. Ask what evidence would weaken the explanation, and use comparable periods before deciding the campaign needs a correction.

Likewise, distinguish an accurate observation from a useful recommendation. A higher optimization score is not the business objective. Google's score reflects its available recommendations; the suggestion still has to fit what the campaign is trying to achieve. A well-supported answer may be that the team needs more evidence or that no edit is warranted.

Do not manufacture a formal decision table for every question. A report request can end with a checked report. A consequential proposal deserves more attention because it could change spend, reach or measurement.

Before accepting a change, inspect the actual edit

Google documents that Ask Advisor can implement suggested changes with your approval. Read what is being changed, not only the explanation above it. Check the account, campaign, current setting and proposed value. For an exclusion, inspect the scope and match type; for a budget or target, consider what the new setting means for the business.

A controlled test may make sense for an uncertain strategy change, but not every edit needs an experiment. The relevant question is what could go wrong, how you would notice, and what recovery is actually possible. Restoring a setting cannot recover auctions already missed or money already spent.

After accepting an edit, inspect the resulting setting and the available change record. Permission to attempt an edit is not confirmation that it succeeded. If the result is unclear, establish what happened before attempting it again.

Keep whatever record a teammate needs to understand the decision: the proposal, the important evidence, the change actually made, and anything still uncertain. This can be a short note. The purpose is continuity, not another form to complete.