An account reports lost impression share due to budget and the obvious recommendation is to raise the limit. But visibility is not the client’s final outcome. The question is whether additional eligible auctions would add worthwhile customers within the agreed economics. This review builds a decision that can end in an increase, a reallocation or no change.
Make this useful for your client. Follow the worksheet, or use the ready-to-copy task with your connected data.
Try this task in 1ClickReport → · See the product workflow →Evidence → Decision → Review
How to run the investigation
Define the conversion that matters
State the client’s actual outcome and which conversion actions the campaign uses. Check whether the report counts a purchase, a qualified lead or a lightweight action such as a page visit. Low-cost microconversions can make a constrained campaign look deceptively attractive.
Locate the constraint
Inspect the campaign’s budget status and impression-share metrics in its native account. Separate budget limitations from rank limitations. Keep campaign type and metric availability explicit; do not interpret a missing field as zero lost opportunity.
Check where the next dollar goes
Review brand versus non-brand, search terms, geography and recent conversion maturity. A strong blended CPA can hide a small efficient segment alongside weak expansion traffic. Document the evidence for additional demand rather than assuming all missed impressions are equivalent.
Write a bounded experiment
If economics justify testing, specify the maximum amount, duration and stop rule for an approved change. Where total spend cannot rise, identify the donor campaign and quantify the tradeoff. A recommendation is not authorization to spend.
Decision worksheet
Use these rows to turn the investigation into an action. Add the actual account, date range, evidence and owner before sharing it with a client.
| What you find | Interpretation | Next move |
|---|---|---|
| Budget limited, good mature outcomes | Potential expansion case | Propose a bounded test, not an unlimited increase. |
| Rank limited | Budget may not solve eligibility | Inspect relevance and auction context. |
| Cheap unqualified conversions | Reported efficiency is misleading | Repair the outcome definition before scaling. |
Download this worksheet (CSV) ↓
Worked example: an illustration, not a customer result
A campaign with $500 spend and 25 form submissions has a $20 form CPA. If only two are genuine opportunities, the observed qualified cost is $250. Lost impression share does not make the $20 figure the correct scaling target. Supply lead-quality outcomes manually when they are not in your connected data.
MAKE THIS YOUR NEXT CLIENT TASK
Run the review on your own data.
Start with one client in 1ClickReport. Connect Google Ads, select the correct client and use the task below. The analyst keeps client-specific context as you work.
Read the ready-to-use task
Review whether this Google Ads campaign deserves more budget. Check the conversion definition, budget and rank limitations, brand mix, search intent and mature outcomes. If qualified lead data is missing, ask me for it. Compare an increase with a reallocation inside the existing account cap. Return a test plan for approval, not a change.
3-day free trial · No credit card required.
- Copy the task, then create your account in the new tab.
- Finish setup and connect the relevant client data.
- Return to this page and open the task in AI Analyst ↗. Review the prompt before sending.
Read-only analysis is available from Solo. Campaign execution requires Team or Agency and approval.
A question worth asking
Can an AI analyst guarantee the return on extra budget?
No. Historical averages do not determine marginal returns. Use them to design a limited test, then compare the additional spend and qualified outcomes after the agreed observation window.
References and method
Reviewed November 12, 2026. The decision process and worksheets are 1ClickReport’s editorial recommendations. Examples are hypothetical, not customer results. Platform behavior and access can vary; use the current native account view to verify settings.