# Spotting the Meta Ad Account That Needs Attention Today

> A daily Meta Ads check for agencies running many accounts: the four signals worth watching, how to compare against a baseline, and what to do next.

Author: The DashOps Team  |  Published: 2026-10-08  |  Updated: 2026-10-13  |  Topic: Performance Marketing

You open Meta Ads Manager, you have a long list of client ad accounts to look after, and every one of them is technically "fine". Nothing is red. Nothing is broken. And yet somewhere in that list, one account did something yesterday that will cost your client money if you do not touch it this morning. The problem is not that you lack data. It is that you have a whole portfolio's worth of data and no fast way to tell which account is asking for you.

The usual answer is to open each account in turn and squint at the last seven days. That works while the list is short. It stops working as the list grows, because the effort scales with the number of accounts and your morning does not. What you need instead is a repeatable triage pass: a short, fixed sequence of checks that tells you quickly which single account gets your attention today and which ones can wait until their scheduled review.

![image_20261008_174300-httpsdashopsioresourcesswitching-between-ad-accoun-httpsdashopsioresourcesavoi](https://pub-ae7c0247bc134935855f21b665422e27.r2.dev/posts/1791912371995-aa4f20eddd92.jpg)

## Triage is a different job from optimisation

The mistake is treating the morning check as a mini optimisation session. You open an account, notice a slightly high cost per result on one ad set, and disappear into it for the rest of the morning. Meanwhile another account has been serving a disapproved ad since Tuesday and you have not looked.

Triage answers one question only: which account has changed in a way that needs a human today? It does not fix anything. It does not touch budgets. It produces a shortlist, usually of one account, occasionally of none, and then you stop. Optimisation is a separate block of work you do on the account triage flagged, with proper focus, after triage is finished.

Keeping the two separate is what makes the pass fast enough to actually do every day.

## The four signals worth checking

Across a portfolio, the signals that reliably mean "look at me" are narrower than you would think. Most of the metrics you care about in a monthly report are not useful for daily triage, because they move too slowly to tell you anything in a single day.

These four are worth a daily glance:

- **Delivery stopped or collapsed.** Spend that was steady and is now near zero, or an account that spent nothing yesterday when it should have. This is the highest-priority signal because it usually turns out to be a fault rather than a fluctuation: a rejected ad, a paused campaign someone forgot to unpause, a payment method that failed, a budget that hit its cap.
- **Delivery ran away.** Spend above the daily pace you expect, usually because a budget was edited, a campaign budget is being consumed by one ad set, or a new campaign launched alongside the old one instead of replacing it.
- **Cost per result moved sharply against you, on real volume.** The volume qualifier matters. A cost per lead that doubled on a handful of leads is noise. The same move on a campaign that normally produces a steady flow of leads is a signal.
- **A new issue appeared on an ad or ad set.** Disapprovals, learning limited, rejected creative, policy flags. These do not show up in your spend numbers at all until delivery has already suffered.

Notice what is absent. Frequency, reach, CTR, CPM, and audience overlap all matter, and none of them belong in a daily triage pass. They move gradually and you will catch them in the weekly or monthly review. Putting them in the daily pass adds items to scan without adding decisions.

## Compare against a baseline, not against zero

A number on its own tells you almost nothing. Yesterday's spend for Acme Interiors is meaningful only against what Acme Interiors normally spends. This is why period-over-period comparison is the single most useful thing you can put in front of yourself in the morning: it turns raw figures into deltas, and a delta is something you can scan.

Pick the comparison window deliberately. Yesterday against the day before is noisy, especially for accounts with weekday and weekend patterns. Yesterday against the same day last week is usually better for anything with a weekly rhythm, which is most local services and most business-to-business lead generation. The last seven days against the previous seven is the steadiest of the three and the one to lean on when an account has modest daily volume.

Whichever you choose, be consistent, because your eye learns the shape of a normal week for each account and it can only do that if the comparison stays the same.

## Run the pass in one place, not one account at a time

The whole approach falls apart if seeing the numbers means logging into every account in turn. That is the tax that makes people skip the pass on busy mornings, and skipping it is how a stalled account goes unnoticed for days.

A [multi-client dashboard for Facebook Ads](/resources/facebook-ads-multi-client-dashboard) exists precisely to remove that tax. In DashOps you connect every Meta ad account once, and the accounts overview puts them side by side with the period-over-period movement already calculated, so the scan is one screen rather than a queue of logins. You customise which KPI cards appear and drag them into the order you actually read, which means the two or three numbers that drive your triage decision sit at the top left where your eye lands first.

The point is not the tool. The point is that triage has to be cheap in time and attention, or it will not survive contact with a real week.

## Make the flags come to you

The next step up from scanning is not scanning at all for the routine cases. Two mechanisms help.

The first is alerts. DashOps sends notifications in-app, to your desktop, and to Slack or Discord, so the events that genuinely cannot wait reach you without you going to look. Keep these ruthlessly few. An alert that fires most days is not an alert, it is a background noise you will learn to dismiss reflexively, and the one time it matters you will dismiss that too.

The second is a scheduled digest. A [daily or weekly email digest](/resources/facebook-ads-weekly-digest) with each ad account's headline numbers and a spend chart gives you a passive baseline. You read it with your first coffee, you notice that Globex Fitness looks different from usual, and you go and look at only that one. Over a few weeks the digest does something more valuable than any individual number: it trains your sense of what normal looks like for each client, which is what makes an abnormal morning obvious at a glance.

## What to do when an account is flagged

Once triage has given you a name, the sequence for actually diagnosing it goes roughly:

- **Check delivery status first.** Is anything paused, rejected, or in review? A fault is a more common cause of a sudden change than a shift in performance, and it is quicker to rule out.
- **Then drill from campaign to ad set to ad.** Find the level at which the change actually happened. A campaign whose cost per result jumped often has one ad set responsible and the rest untouched.
- **Then check what changed and when.** Did someone edit a budget, launch a new creative, or change an audience? Line the date of the change up against the date the numbers moved. If your dashboard keeps an audit log of who changed what, this becomes a lookup rather than guesswork.
- **Only then decide.** And where the account is genuinely new to you, or you inherited it mid-flight, a structured pass is better than a spot fix. That is a different exercise, covered in [auditing a Facebook ad account you have just taken over](/resources/auditing-a-new-facebook-ad-account).

Resist the pull to fix the flagged account and then keep going through the rest "while you are in there". Finish triage first, then work. The whole value of the pass is that it stops you spending your best hours on the account that happened to be alphabetically first.

## Getting started tomorrow morning

Pick your comparison window and write it down, so you are not re-deciding it every day. Choose the two or three numbers that will drive your decision, put them where you will see them first, and ignore everything else during the pass. Set up a small number of alerts for the events that genuinely cannot wait a day, and turn on a digest so you build a feel for each account's normal rhythm.

Then give yourself a hard stop. If the pass is dragging on, the problem is your setup, not your discipline, and the fix is to cut what you are looking at rather than to look harder. Once the daily pass is reliable, the natural next move is to stop hand-building the recurring reports too, which is where [automating your Facebook Ads reporting](/resources/how-to-automate-facebook-ads-reports) picks up.

## Frequently asked questions

### How often should I actually run this triage pass?

Every working morning, if you run accounts with live spend. The pass is deliberately short so that daily is realistic. If daily feels heavy, that is a sign you are checking too many metrics rather than checking too often. Cut the pass down to delivery, spend pace, cost per result and new issues, and it should fit comfortably before your first meeting. Accounts that are paused or spending nothing can drop out of the daily pass entirely and move to a weekly glance.

### What comparison window should I use for the daily check?

For accounts with a clear weekly rhythm, compare yesterday against the same weekday last week, so a quiet Sunday is not read as a collapse. For accounts with modest daily volume, compare the last seven days against the previous seven, which smooths out single-day noise. The specific choice matters less than consistency. Your eye learns what normal looks like for each account only if the comparison stays the same week after week.

### Should I set an alert for every metric that moves?

No, and this is the most common way people ruin their own alerting. An alert that fires most days stops being information and becomes noise you dismiss without reading, including on the day it matters. Reserve alerts for the handful of events that genuinely cannot wait until your next scheduled look, such as delivery stopping or a broken connection, and let everything else surface through your daily pass or your scheduled digest.

### How do I tell a real problem from normal fluctuation?

Volume is the deciding factor. A sharp move in cost per result on a handful of conversions is usually noise, while the same move on a campaign that normally produces a steady flow is worth investigating. Rule out a fault before you assume a performance shift: something paused, rejected, in review, or a budget edited yesterday is quicker to check, and it turns out to be the cause more often than people expect.

### Can I run this pass without switching between ad accounts one by one?

Yes, and you should, because the switching cost is what makes people skip the pass on busy days. Connect every Meta ad account to one dashboard so they sit side by side with the period-over-period movement already calculated, then customise which KPI cards show and reorder them so your decision-driving numbers are the first thing you read. The scan becomes one screen instead of a login queue.

---

Full page: https://dashops.io/resources/spotting-the-ad-account-that-needs-attention