How BidSmart works
The end-to-end BidSmart model, how it analyses your account product by product, proposes bid changes, queues them for your sign-off, and executes only what you approve, with a full before/after audit trail.
BidSmart connects to your Google Ads account and studies performance one product at a time, then proposes changes, tROAS adjustments, incubator moves, budget flags. Every proposal lands in an approval queue and does nothing until you sign it off. There is no autopilot: BidSmart never executes against your ad account on its own, and every change it does make is recorded with its before and after state so you can review or reverse it.
The one thing to understand first
BidSmart is approval-first. It reads your Google Ads account, works out what each product could be doing differently, and proposes changes: but it does not execute them. Every proposal waits in an approval queue until you review and sign it off. There is no autopilot mode that bypasses the queue, and there never will be. That single rule shapes everything below.
The five stages, end to end
BidSmart runs the same loop continuously. Understanding the five stages tells you exactly where you sit in it and what is and isn't happening to your account at any moment.
1. Analyse
Once you've connected Google Ads, BidSmart pulls your Shopping performance and breaks it down to the product level: impressions, clicks, cost, conversions, conversion value and the resulting ROAS for each individual product, not just each campaign. It combines that with your feed data (price, margin signals, lifecycle stage) so it can judge each product on its own economics rather than the campaign average. See product-level tROAS analysis for how that judgement is formed.
2. Recommend
From that analysis, BidSmart forms concrete proposals: raise this product's target, lower that one, move these thin-data products into the incubator, graduate those proven ones out of it, or attend to a budget that's pacing badly. Each recommendation carries a plain-English reason and the numbers behind it: see reading your bid recommendations.
3. Queue
Recommendations don't act. They accumulate in the approval queue. This is the safety boundary: everything upstream of the queue is analysis and suggestion, nothing more. Your ad account is untouched while items sit here, however many pile up.
4. Approve
You review the queue and decide, item by item or in batches. Approve the ones you agree with, reject the ones you don't, leave the rest for later. Nothing you don't approve ever executes.
5. Execute (auditable, reversible)
Only approved items are written to Google Ads. Each executed change records its before and after state (the old target and the new one, the campaign a product moved from and to) so the change is fully auditable and can be reversed to exactly what it was.
Deep dive Why approval-first, and what it protects you from
The industry default for bid automation is a black box: you set a goal, hand over the keys, and hope. It fails in a specific, expensive way: the system makes an aggressive move (a big target jump, a budget reallocation) at the worst possible moment, spend collapses or runs away, and you find out days later from a revenue chart, with no clear record of what changed or when.
BidSmart is built to make that failure mode impossible. Three properties enforce it:
- Staged, not live. Recommendations are proposals until you approve them. The gap between "BidSmart thinks X" and "X happened to my account" is always an explicit human decision. You can let a week of recommendations accumulate and action them in one sitting with zero risk in the meantime.
- Auditable. Every executed change records its before/after state. You can answer "what changed on Tuesday and why" precisely, months later: which matters when you're explaining a performance swing to a client or a boss.
- Reversible. Because the before-state is recorded, any change can be rolled back to exactly what it was. A change you approve is never a one-way door.
This is also why BidSmart's proposals follow ramp discipline (small, relative target steps rather than dramatic swings) so that even the changes you do approve don't trigger a learning reset. Approval-first and ramp discipline together mean the worst realistic outcome of using BidSmart is a change you can see, understand, and undo. See Target ROAS explained for why step size matters so much.
What BidSmart does not do
- It does not execute anything you haven't approved.
- It does not run an autopilot or "set and forget" mode: that mode does not exist.
- It does not touch your product feed or your store. Feed enrichment is a separate, non-destructive module.
- It does not make one-way changes: every executed change keeps its before-state for reversal.
Where to start
- Connect your Google Ads account: read-only until you approve a write.
- Let BidSmart analyse; give it a few days of data to settle.
- Open your first bid recommendations and read the reasons.
- Work the approval queue: approve, reject, or leave items as you see fit.
Frequently asked questions
Will BidSmart change my bids without asking?
Never. Every change BidSmart proposes sits in the approval queue until you explicitly sign it off. There is no autopilot mode, by design, nothing touches your Google Ads account without your say-so.
What happens if I never open the queue?
Nothing executes. Recommendations accumulate safely, you can leave them for a week and action them in one sitting. An unopened queue means an unchanged ad account.
Can I undo a change after it's executed?
Yes. Every executed change records its before/after state, so any approved change can be reversed to exactly what it was before.