Use case
Google Ads performance alerts for agencies
A client's ads stop spending on a Friday, or conversions drop to zero while the clicks keep coming, and nobody notices until the month-end report. Phloz checks every client's Google Ads account each morning against that account's own last four weeks. When something moves far outside its usual range, the alert shows on your overview and goes by email to the teammates assigned to that client.
See it in 58 seconds
A sample client in a demo workspace, captioned, no voiceover. Chapters and the on-screen text
Why agencies hear about it last
Google Ads can email you when a rule you wrote is met, and a manager account can run one rule across the clients that share a currency. But a rule is a fixed number: one cost or conversion threshold is wrong for every account it was not written for, and rules per account across twenty clients are a hundred thresholds to keep current. So most agencies rely on someone opening each account, and the problems that cost the most are the quiet ones: a billing failure that stops spend, a site release that drops the conversion tag while clicks carry on, a bidding change that makes every conversion cost half as much again. Each shows up as a bad week in a report, after the money is spent.
Each account against its own baseline
Every morning Phloz reads each mapped account's recent history, read-only, and compares the last 7 complete days with the 4 weeks before them. There are no thresholds to set: the baseline is the account's own. Conversions are judged against the traffic the week actually had, so a week with fewer clicks is not mistaken for a conversion problem, and a shortfall only counts when a Poisson test puts it at less than 1% likely by chance. The 2 most recent days are left out of the conversion figures while late conversions arrive, and an account too small to judge fairly gets no alerts rather than noisy ones.
Five things it checks
Spend that stopped (critical: the last 3 days at a tenth of a usual 3 days while campaigns are still enabled, open until it comes back), fell to half a usual week, or rose to 1.6 times it, with paused, removed and ended campaigns counted as decisions, not drops. Conversions well below what the clicks predict, critical when they reach zero. Cost per conversion up by half, with the alert saying whether clicks got more expensive or converted less often. Return on ad spend down by 40%, for accounts that record conversion value. Each alert names the campaigns that moved most and what to check first.
The right person hears about it, once
Open alerts sit at the top of your overview and on the client's page. The email goes to the teammates assigned to that client, or to owners and admins when nobody is, and each alert is emailed once, again only if it gets worse. Vacation mode, a muted client and each person's own email switch are respected. Anyone who has looked can mark an alert reviewed, which takes it off the overview, or turn it into a task on the client that says what to check, and an alert closes by itself after two mornings without it.
Next to the tracking behind the numbers
When conversions stop while clicks hold, the cause is often a broken tag rather than demand, and the client's tracking map and audit are one tab away. The weekly Google Ads audit adds wasted spend and setup findings, and an AI assistant connected through Phloz's MCP server can read the alerts, the daily figures and the audit together and explain what changed.
Common challenges agencies hit on this
The recurring obstacles agencies report when running this use case. Honest list — these aren't Phloz-specific problems, they're patterns we see across most agencies regardless of tooling. Worth recognising even if you don't end up on Phloz.
- Automated rules in Google Ads run on fixed thresholds someone has to set and keep current, and one number shared across a manager account fits few of its clients
- A billing failure or a disapproval stops spend on a Friday, and nobody opens that account until Monday
- A site release breaks the conversion tag: clicks keep coming, conversions stop, and smart bidding learns from the gap
- Alerts land in a shared inbox where everyone assumes someone else has it
How agencies use this in practice
The pattern that works across most agencies running 5–50 clients: scope the use case as a discrete operational surface, assign a single owner (usually the ops lead or tracking engineer), set a recurring cadence (weekly check, monthly audit, quarterly review), and connect it to the rest of the agency's work via the tracking map and the per-client task surface.
The 1-2-week setup window is the same regardless of tool — the differentiator is whether the tool ships the primitives you need (client, tracking node, recurring task, audit template) or makes you build them yourself out of custom fields. Phloz ships them; generic PM tools don't. That's the entire trade-off, and it's only worth paying for once you have the client volume to need it (typically 5+ retainers).
Frequently asked questions
The three questions agencies ask most often about this use case. Honest answers — same data we'd give a friend evaluating the approach.
- Doesn't Google Ads already send alerts?
- Partly. Automated rules can email you when a condition you set is met, such as spend over a fixed amount, and a manager account can run one rule across client accounts that share a currency. Explanations describe why a campaign's numbers changed when you open it and look. Either way the thresholds are numbers you choose and keep current. Phloz runs one check across every client's account, measures each against its own last four weeks with no thresholds to maintain, tests conversion drops for chance, and sends each alert to the teammates who look after that client.
- How quickly will I hear about a problem?
- The next morning. The check runs once a day at 13:00 UTC (6 AM in Vancouver, 9 AM in Toronto) and reads up to the last complete day in the account's own time zone. It is not real time: a problem that starts today shows tomorrow. Stopped spend is judged on the last 3 days, so a halt is caught within a day or two rather than averaged into a week.
- Will it flag a quiet week in a small account?
- It is built not to. Spend alerts need about US$70 a week of steady spend (the same in the account's own currency), with spend on at least 20 of the 28 days before the week; conversion alerts need enough clicks and conversions in the 4 weeks before to expect at least 5, and a shortfall less than 1% likely by chance. An account below those levels shows as not enough data, not as an alert.
- Does Phloz change anything in our Google Ads accounts?
- No. Phloz reads Google Ads through Google's API with read-only queries and never changes a campaign, budget or bid. The daily check and the weekly audit are included on Growth and above, for every client with a Google Ads account mapped.
Related in Phloz
Other use cases
Other ways agencies put Phloz to work.
14 days free for new workspaces · No credit card · Starter tier free forever