How to Set Up Ad Alerts Across Six Platforms
Marta Kowalczyk
Agency Operations Lead
Most ad-alert tutorials quietly assume you only run Meta. That is fine until you also have spend on Google, a creative test on TikTok, native campaigns on Taboola and Outbrain, and a catalogue campaign on Snapchat, at which point a Meta-only setup leaves five platforms unwatched. Whether you are planning an email, in-app or ad alerts telegram setup, the delivery channel is the last decision, not the first: the work that matters is choosing what to watch on each platform, setting thresholds, and routing events to the people who act on them.
Quick answer: To set up cross-platform ad alerts, connect each platform via official OAuth, decide which events need a human, and define thresholds (spend pacing, CPA, ROAS, budget) that apply across platforms. Route each alert type to its owner and pick a delivery channel by severity. In Wevion, alerts cover Meta, Google, TikTok, Taboola, Snapchat, and Outbrain. Alerts notify; a human approves action. Data reflects a ~15-minute sync.
The steps below assume you want alerts you will still trust six months from now, not ones you mute after a week of noise. Setup is the easy part; tuning is what makes it stick.
Why a six-platform setup, not a one-platform one
The case for going cross-platform from day one is simple: spend has fragmented faster than monitoring habits have. eMarketer's 2024 forecasting put US digital ad spend well into the hundreds of billions and increasingly spread across multiple major platforms rather than concentrated in one, which means the typical performance operator now answers for several managers at once. A Meta-only alert setup made sense when Meta was most of the budget; it leaves an expanding share of spend unwatched today.
The platforms themselves have grown the surface, too. Meta disclosed more than 12 million active advertisers across its apps in 2024 reporting, and the same operators running those accounts are usually the ones layering on TikTok, Google, and native channels. More platforms per operator means more blind spots per operator, unless the alert layer covers all of them from one place. Defining alerts once across six platforms is less work than maintaining six separate alert habits, and far less work than discovering an overnight problem on the platform you forgot to watch.
Step 1: Connect each platform via official OAuth
Before anything can alert, Wevion needs read access to your ad data on each platform. This happens through each provider's official OAuth flow (Meta, Google Ads, TikTok, Taboola, Snapchat, and Outbrain), the same authorised connection the platforms publish for partner tools. You grant access per account; you can revoke it at any time from the provider side.
Connecting through official OAuth matters beyond convenience. It means your alert pipeline reads data the way the platforms intend partner tools to read it (authorised, scoped, and revocable) rather than scraping or unofficial automation. The alert layer should never be the reason your account draws scrutiny; an official connection keeps the plumbing clean.
Connect every platform you actually spend on. A common mistake is wiring only the "main" platform and treating the others as secondary, but the unwatched platform is exactly where an overnight problem hides, precisely because nobody is checking it. Coverage is the goal; partial coverage just relocates your blind spot.
Step 2: Decide what is worth an alert on each platform
The same handful of events matter everywhere, but each platform has its own way of going wrong. Knowing the failure mode tells you where to set the tightest thresholds:
- Meta: CPA drift as frequency climbs and creative fatigues, budget burning fast on a newly scaled ad set, and ads rejected or limited by review.
- Google: campaigns spending their daily budget early in the day, CPA creeping up on broad-match search terms, and conversion volume dropping after a bid strategy change.
- TikTok: creative fatigue that arrives in days rather than weeks, so CPA and ROAS on a winning ad can turn quickly.
- Taboola and Outbrain: CPA spread across placements, with a few publishers able to absorb spend at a much worse cost than the campaign average.
- Snapchat: CPM swings that change the economics of a campaign without any change on your side, and catalogue campaigns pacing ahead of plan.
You do not need a different rule set per platform. You need the same core events, with thresholds set against each platform's normal behaviour, which is what the next step covers.
Step 3: Define thresholds that travel across platforms
This is where most setups go wrong, and where a good one earns its keep. Define alert rules around the events that need a human, and let them apply across your connected platforms rather than rebuilding them six times. The events worth wiring:
- Spend pacing: a campaign outrunning its expected curve, or a daily budget nearly spent before midday.
- CPA drift: cost per acquisition crossing a ceiling you would reject in a review.
- ROAS collapse: return on ad spend dropping under a floor on a previously profitable campaign.
- Budget exhaustion: an ad set or campaign about to go dark on its cap.
- Status changes: a campaign paused, rejected, or limited by the platform itself.
Set thresholds against a recent baseline rather than a fixed number wherever you can, so a noisy metric does not trigger constantly. And scale thresholds to spend: a small test campaign and a high-budget scaler should not share the same ceiling. The discipline test for every rule: if this fires at 2am, would I want to know? If not, it belongs in a scheduled report, not a notification.
The fastest way to ruin an alert setup is to make it ping for everything. Alerts that cry wolf train you to ignore them, and then the one alert that mattered dies in the noise with the rest. Wire the high-cost, unambiguous events; route the merely informational to a summary you read on your own schedule.
If a rule should apply to several platforms at once, Wevion's cross-platform rules (in beta) let you define it once instead of per platform; the automation rules deep dive covers how rules are built.
Step 4: Route the right alerts to the right people
A solo operator can send everything to one place. A team cannot, or rather, it can, but everyone learns to ignore notifications about things outside their job. Scope routing so the signal reaches the person who acts on it.
A practical split for an agency or a brand team: budget and spend-pacing alerts to whoever owns the money conversation; CPA and ROAS drift to the media buyer running the account; platform status and rejection alerts to whoever handles compliance and creative. The same event stream, filtered so each person trusts that a ping is theirs to handle.
Routing is what separates a team alert system from a feed nobody reads. When every member knows that a notification reaching them is actionable by them, alerts stay alive. When alerts are sprayed indiscriminately, the whole team mutes them, and you are back to checking dashboards, now with extra steps.
Step 5: Choose a delivery channel per severity
Only now does the channel question matter, and the answer is rarely a single channel. Wevion can deliver alerts by email, in-app, or Telegram, and each suits a different kind of signal:
- In-app: the natural home for alerts you review while working in the platform, with the campaign one click away.
- Email: good for lower-urgency signals and for anyone who wants a written record, such as a client lead or finance owner.
- A mobile messaging channel: for the few urgent events that cannot wait until you are back at a desk, like budget exhaustion on a top campaign overnight.
The rule of thumb: the more expensive it is to miss an alert, the closer to your phone it should land, and the fewer alerts should share that channel. For a fuller comparison of channels, see where ad alerts should land.
Every platform label travels inside the alert, so whichever channel you choose, a message reads as "CPA ceiling breached, TikTok, Campaign X". You think in events, not in platforms, and you never need a separate inbox per ad network.
Step 6: Tune for a week, then trust it
The first week is calibration. Some thresholds will fire too often; tighten them or move them to a report. Some events you wanted will not fire because the threshold was too loose; sharpen them. Treat the early alerts as feedback on the rules, not as failures of the system.
By the end of a calibration week, alerts should be quiet most of the time and right when they speak. That silence is the goal: a well-tuned ad account is boring, and boring is exactly what you want your notifications to confirm until they don't.
A useful habit during calibration: keep a short log of every alert and whether it was actionable. After a week, any rule that produced a string of "nothing to do here" messages is a candidate for tightening or demotion to a report. Any moment you wished you had been told but weren't is a candidate for a new rule. You are not just configuring software; you are encoding your own definition of "worth interrupting me," and that definition only becomes accurate against real account behaviour.
Account for the data cadence while you tune. Because Wevion syncs roughly every 15 minutes, an alert reflects a settled window, not a half-second flicker. That settling period is why cross-platform alerts stay sane: it filters the micro-volatility that would make a constant stream unbearable, while still closing the overnight and weekend gaps where manual checking fails completely.
The line to keep in mind: alerts notify, you act
It is worth restating because it shapes how you set thresholds. Wevion alerts inform; they do not execute. No alert here pauses a campaign, cuts a budget, or edits an ad on its own. A threshold breach produces a message; the response is yours, made with context the system cannot see: the launch you planned, the promo starting tomorrow, the client call from this morning.
If you want the system to go further and prepare a specific fix for your approval rather than just flag the problem, that is a separate, approval-first capability, and the trade-offs are laid out in our breakdown of manual, alert-only, and guarded automation. Alerts are the foundation that makes the rest worth having: they keep you informed without making spend decisions for you.
Where this fits in the bigger picture
A cross-platform alert setup is the front door to a consolidated workflow. The same six platforms that feed your alerts should also feed one cross-channel view, so an alert leads to a dashboard that already speaks every platform instead of a fresh round of six logins. The why-you-should-stop-dashboard-checking guide covers the workflow shift this setup unlocks; the Meta ads performance alerts guide and the Facebook ads alerts setup guide cover single-platform depth if Meta is where most of your spend lives.
You can set up the full six-platform alert layer during Wevion's 14-day free trial: plans run Starter €99, Pro €499, Plus €1,499/month (€14,388/yr billed annually), and Enterprise custom, so the alert layer scales with how many accounts you connect. Start in the automation-rules hub for the rest of the monitoring and approval-first series.