For agencies and media buying teams running a large fleet of ad accounts
Every 2 hours SpendGuard pulls spend from every Facebook, Google Ads and TikTok ad account, checks tokens hourly and sorts accounts by status. When a token dies, Telegram gets a message right away, and the admin panel shows why.
Sound familiar?
Thirty profiles, dozens of BMs, hundreds of ad accounts. Overnight one profile hits a checkpoint, and twenty of its accounts just drop out of sight. Nobody shows you an error: Ads Manager only lists the accounts you still have access to.
Two more accounts owe money, one got disabled for policy, and three quietly stopped spending five days ago. It’s all spread across tabs, profiles and currencies. Piecing it together by hand eats half the morning.
So I built SpendGuard: it walks through every ad account on its own and shows what broke.
How it works
It runs on a schedule on your server: pulls spend, checks access, recalculates statuses and puts the results where you’ll see them — the admin panel, a Google Sheet and Telegram.
Via a one-time Facebook login link, a System User token or a CSV batch. The profile’s ad accounts and BMs come in on their own, with 30 days of spend history.
Batch requests to Meta, 50 accounts each. Every run re-pulls the last 3 days, since Meta adjusts spend after the fact. Then statuses, alerts, the sheet and a Telegram digest.
Checks every connection. A dead token immediately triggers a critical alert with the reason (password changed, checkpoint, expired) and a separate Telegram message.
Re-reads BMs to find new ad accounts, re-pulls 7 days of spend, and archives accounts that have been disabled for 60 days.
In the morning you open the dashboard: statuses, idle accounts, dead tokens and today’s top spenders are already counted.
Statuses
Every ad account lands in exactly one status, so they always add up to your whole fleet. The same numbers show up on the dashboard, in the list filters and in the Telegram digest.
Tokens
SpendGuard checks every connection hourly. A dead token is flagged with the reason, its ad accounts move to “access lost”, and Telegram gets a separate message.
Alerts
Facebook has three alert types: connection lost, ad account not responding, connection expiring. Open alerts are sorted by severity, so you start at the top.
Ad accounts
The tree collapses to profiles with total spend and expands down to every ad account. For each account you see its status and since when, how many campaigns are live, spend for the period and all time, and the balance.
Telegram
Each channel has its own bot and its own recipients: the team chat, finance, the owner. Notifications are toggles, so you can keep only what matters.
Idle accounts
A separate list of accounts in good standing that were spending and then sat at zero for 3+ days. Next to it — accounts that have never spent at all.
Three channels
On the home screen each channel gets its own card: spend for the period vs. the previous one, connections and statuses. There’s no combined total on purpose: channels have different statuses and different money, and lumping them together only confuses things.
Details
Accounts in UAH, EUR, PLN and USD are summed in dollars at the National Bank of Ukraine rate for the day of each spend. Original-currency totals sit right next to it.
One tab per month: profile → BM → ad account, status, total and days 1 to 31. Updated after every pull.
Calculates Meta’s fee for impressions in Austria and Turkey (5%), France, Italy, Spain (3%) and the UK (2%) — per account and country, at the rate on the day of spend.
An account that’s been disabled, closed or without access for 60 days goes to the archive and stops being polled. If Facebook brings it back, it returns on its own.
Reads usage from Meta’s headers: slows down at 75%, pauses at 90%. Glitches on Facebook’s side don’t paint healthy accounts as broken.
A report per account or selection: status, daily spend for 30 days, alerts. Or a daily spend sheet for accounting.
For teams
All channels, bot settings and team permissions. The Health page shows API load and when the next pull runs.
Ad accounts, alerts, idle accounts and tokens for their channel. They handle alerts and reconnect profiles.
Spend for any period in original currencies and dollars, Location Fee and XLSX exports.
Numbers and limits
FAQ
Spend is pulled in batches of 50 accounts, 5 in parallel, while a limiter watches Meta’s API usage. SpendGuard is built for fleets of hundreds to thousands of ad accounts. We’ll size it for your number of profiles and BMs.
No. SpendGuard only reads spend, account statuses and balances. It never touches campaigns, budgets or creatives.
Within an hour SpendGuard sees the token isn’t responding, records the reason and moves that profile’s ad accounts to “access lost”, so they don’t sit there showing zeros. Telegram gets a separate message. After you log back in via the link, the accounts return on their own.
A Meta token lasts about 60 days, and in practice Facebook won’t extend it. So SpendGuard warns you 7 days ahead and reminds you in Telegram, and renewing is one Facebook login via a one-time link. System User tokens never expire.
Yes: through a profile that has access, through a client login via a one-time link, or with a System User token from the BM. One caveat: the Meta app’s advanced access is still in App Review, so for other people’s BMs a System User is the more reliable option.
No. The admin panel and Telegram work without a sheet. If you connect one, each channel gets its own sheet with a tab per month.
On the server where SpendGuard is installed. Tokens and keys are encrypted in the database, the admin login needs a password and a 2FA code, and each team member only sees the sections they need.
We’ll walk through statuses, tokens and alerts, and I’ll explain how it fits your profiles and business managers.
Discuss on TelegramOther products