When an ad campaign starts underperforming, every hour of delay costs budget. Real time ad performance alerts give marketing teams the ability to catch problems the moment they surface, not days later during a weekly review. For B2B SaaS companies running paid campaigns across multiple channels, this kind of immediate visibility is the difference between controlled spend and wasted budget.
This guide walks you through exactly how to set up real time ad performance alerts, from defining the right thresholds to routing notifications to the right people on your team. By the end, you will have a working alert system that monitors your campaigns continuously, flags anomalies automatically, and gives your team the context needed to act fast.
Whether you are managing Google Ads, Meta campaigns, LinkedIn, or a multi-channel mix, the same principles apply. The key is connecting your ad data to a centralized system that can evaluate performance against your benchmarks in real time.
That is where a platform like Cometly becomes essential. Rather than checking individual ad platforms separately, Cometly pulls all of your campaign data into one place, tracks every touchpoint from first ad click to closed revenue, and gives your team a single source of truth. With that foundation in place, setting up meaningful alerts becomes straightforward.
Let us get into the steps.
Step 1: Define the Metrics That Actually Matter for Your Campaigns
Before you configure a single alert, you need to know what you are actually monitoring. This sounds obvious, but most teams skip this step and end up with alert systems that fire on metrics that do not drive decisions.
Start by identifying the core performance metrics tied directly to your campaign goals. For B2B SaaS companies, these typically include cost per lead, cost per acquisition, return on ad spend, click-through rate, conversion rate, and pipeline attribution. Each of these connects to a real business outcome, which is exactly the standard your alert system should meet. Understanding your campaign performance metrics in depth is the first step toward building alerts that actually drive decisions.
The next distinction is critical: separate vanity metrics from decision-driving metrics. Impressions and reach rarely warrant an alert. A spike in cost per lead or a drop in conversion rate absolutely do. If a metric would not change what your team does today, it probably should not be in your alert system.
For B2B SaaS specifically, the most powerful alerts connect ad spend to pipeline velocity and revenue attribution, not just top-of-funnel clicks. A campaign generating high lead volume but low opportunity creation rate is underperforming in a way that click-through rate will never reveal. This is why including downstream metrics in your alert framework matters so much. Cometly makes this possible by connecting your ad data to CRM events and revenue outcomes, giving you a complete picture rather than a partial one.
Once you have identified your metrics, document your current baseline for each one. Alerts without baselines produce noise, not signal. If you do not know what normal looks like, you cannot define what abnormal means. Pull your last 30 to 60 days of campaign data and calculate your average performance for each metric. This becomes the reference point for every threshold you set in the next step.
Common pitfall to avoid: Setting alerts on too many metrics at once creates alert fatigue. When every metric has an alert, teams stop paying attention to any of them. Start with three to five critical metrics per campaign and expand only after your system is running cleanly.
Leading indicators like CTR and CPC trends give your team more time to respond before budget impact becomes significant. Lagging indicators like CPL and ROAS tell you when damage has already occurred. A well-designed alert system monitors both, but prioritizes the leading indicators that let you get ahead of problems.
Step 2: Establish Performance Thresholds and Anomaly Benchmarks
With your metrics and baselines documented, the next step is defining what counts as an alert-worthy deviation. This is where most teams either set thresholds too tight and drown in false positives, or too loose and miss real problems entirely.
The most reliable approach is to set thresholds as percentage deviations from your baseline rather than fixed numbers. A 30% spike in cost per lead is meaningful regardless of your absolute CPL value. Percentage-based thresholds scale with your campaigns and stay relevant as your performance matures.
Build two tiers of alerts into your system. Warning thresholds signal an early deviation worth monitoring closely. Critical thresholds signal that immediate action is required. This two-tier structure gives your team time to investigate before escalating to urgent response, which reduces both panic and missed issues.
A practical threshold framework to start with: set a warning at 20% deviation from your 7-day rolling average, and a critical alert at 40% deviation. The rolling average accounts for recent performance trends rather than locking you into a static baseline that becomes outdated as campaigns evolve.
One factor many teams overlook is natural performance variance by day of week and campaign stage. Understanding daypart performance patterns is essential here — Monday CPL often differs meaningfully from Friday CPL, especially in B2B markets where decision-makers are less active on certain days. If your thresholds do not account for this variance, you will generate alerts on predictable patterns rather than genuine anomalies. Build day-of-week context into your evaluation logic where possible.
For B2B SaaS campaigns with longer sales cycles, include pipeline-level metrics in your thresholds, not just immediate conversion metrics. A campaign that stops producing qualified opportunities is underperforming even if lead volume looks steady. Alerts that only monitor form submissions will miss this entirely.
Tip: Review and recalibrate your thresholds monthly. As campaign performance matures and your baselines shift, thresholds that were accurate in month one may be too tight or too loose by month three. Treat your alert configuration as a living system, not a one-time setup.
Step 3: Connect Your Ad Platforms to a Centralized Attribution System
Here is where the technical foundation of your alert system gets built. Before alerts can work accurately, your data sources must feed into one unified system. Siloed platform data produces siloed, incomplete alerts, and incomplete alerts lead to incomplete decisions.
The first task is connecting all of your active ad channels to a single attribution platform. This means Google Ads, Meta, LinkedIn, and any other platforms where you are running campaigns. Cometly supports over 70 native integrations, which makes this connection process straightforward without requiring custom engineering work. Evaluating the right performance marketing platforms for your stack is worth doing before committing to a long-term attribution setup.
Once your channels are connected, set up server-side conversion tracking and Conversion API integration. This step is more important than most teams realize. Browser-based pixel tracking is increasingly unreliable due to ad blockers and browser privacy restrictions. When pixels miss conversions, your performance baselines are distorted, and distorted baselines mean your alert thresholds are calibrated against inaccurate data. Server-side tracking closes this gap by capturing conversion events at the server level, independent of browser behavior.
If you are running both pixel and server-side tracking simultaneously, event deduplication is essential. Without it, conversion counts are inflated, and your alert system will be working with numbers that do not reflect reality. Cometly handles deduplication as part of its Conversion API integration, keeping your event data clean and accurate.
The next connection to make is your CRM. For B2B SaaS, a lead that does not progress to an opportunity is not the same as a lead that converts to revenue. Your alert system needs to see both. Syncing your CRM data into your attribution platform means pipeline events, opportunity creation, and closed-won revenue all become visible alongside your ad performance data. This is what makes downstream alerts possible.
Before activating any alerts, verify your data accuracy. Check event match quality in your attribution platform and confirm that conversion events are firing correctly across all channels. If your tracking is broken, your alerts will fire on bad data and send your team chasing phantom problems.
Success indicator: All major ad channels are reporting conversions into a single dashboard with consistent attribution logic applied across all sources. When you see the same conversion event reflected consistently regardless of which channel drove it, your data foundation is ready.
Step 4: Configure Alert Rules Inside Your Analytics Platform
With clean, unified data flowing into your attribution platform, you can now build the alert rules that will monitor your campaigns continuously. This is where the thresholds you defined in Step 2 get translated into active monitoring logic.
Structure each alert rule around four components: the metric being monitored, the threshold that triggers the alert, the time window for evaluation, and the campaign or ad set scope. Every alert rule should be specific on all four dimensions. Vague alert configurations produce vague results.
In Cometly, alert configuration connects directly to your real-time campaign data, so the rules you build immediately start evaluating performance against your defined thresholds. This removes the lag that comes with manual monitoring or scheduled report pulls. A real-time analytics platform is what makes this continuous evaluation possible without manual intervention.
Set time windows appropriate to your campaign type and spend level. High-spend campaigns warrant hourly evaluation windows because budget burns faster and problems compound quickly. Lower-spend campaigns can use daily windows without missing critical shifts. Matching your evaluation window to your spend rate keeps alerts timely without generating excessive notifications on low-activity campaigns.
Build separate alert rules for different campaign objectives. A brand awareness campaign and a bottom-funnel retargeting campaign have fundamentally different performance expectations. Applying the same alert logic to both will either generate false positives on the awareness campaign or miss real problems in the retargeting campaign. Understanding retargeting audience performance benchmarks helps you set objective-specific rules that keep your alerts meaningful.
Include attribution model context in your alert configuration. If your primary attribution model is multi-touch, your alert thresholds should reflect multi-touch conversion values, not last-click. Mixing attribution models between your thresholds and your reporting creates a mismatch that makes alerts difficult to interpret and act on.
Common pitfall: Configuring alerts at the account level instead of the campaign or ad set level. Account-level averages can mask individual campaign problems. A strong performer in one campaign can offset a failing campaign in the same account, making the account-level metric look fine while budget is being wasted at the campaign level. Always configure alerts at the most granular level that is actionable for your team.
Step 5: Route Alerts to the Right People with the Right Context
An alert is only useful if the right person receives it with enough context to act immediately. This step is about making sure your alert system produces responses, not just notifications.
Start by defining ownership before activating notifications. Who is responsible for each alert category? Route campaign-level alerts to the media buyer or campaign manager responsible for that specific channel. Route revenue and pipeline alerts to growth leads or marketing operations. Clear ownership means clear accountability, and clear accountability means faster response times.
Every alert notification should include enough context for the recipient to understand the situation without having to open a dashboard first. Include the current metric value, the baseline value, the percentage deviation, the time window being evaluated, and a direct link to the relevant campaign view. When someone receives an alert at 9am on a Tuesday, they should know exactly what changed, by how much, and where to look, all from the notification itself. A well-structured marketing performance dashboard makes it easy to build these direct links into every notification.
Match your notification channel to the urgency level. Critical alerts that require immediate action should trigger Slack messages or SMS notifications. Warning alerts that need monitoring but not immediate intervention can go to email. This distinction keeps urgent issues visible and prevents important notifications from getting buried in an inbox.
Avoid sending all alerts to the entire team. Broad distribution leads to alert fatigue and diffuses accountability. When everyone receives an alert, it becomes no one's responsibility. Assign specific owners and route accordingly.
Success indicator: When an alert fires, the recipient immediately knows what changed, by how much, and where to look to investigate further. If your team is regularly asking follow-up questions to understand what an alert means, your notification context needs improvement.
Step 6: Build a Response Playbook for Common Alert Scenarios
Alerts create urgency. A response playbook provides direction. Without one, your team knows something is wrong but has to figure out what to do next in real time, which adds delay and inconsistency to your response.
A response playbook maps each alert type to a standard first response action. It does not need to be complex. A simple document that covers your most common alert scenarios is enough to eliminate the decision latency that slows teams down when problems surface.
Here are the most common alert scenarios and their standard first responses:
CPL spike above critical threshold: Check audience saturation and bid strategy first. Review frequency metrics and audience overlap. If the audience is exhausted, refresh creative or expand targeting before adjusting bids.
Conversion rate drop: Verify tracking integrity immediately. Confirm that conversion events are firing correctly and that landing pages are loading without errors. A sudden conversion rate drop is often a tracking issue or a page problem before it is a campaign problem.
ROAS decline: Review creative performance across active ad sets. Check for audience overlap between campaigns that may be causing internal competition. Compare current creative performance against your top performers from the previous period. Applying proven tips to improve ad performance can help you systematically work through these scenarios.
Pipeline contribution drop: Check CRM sync status and confirm that opportunity creation events are being captured correctly. If tracking is intact, review lead quality metrics and assess whether a change in targeting or messaging may be attracting lower-intent leads.
For B2B SaaS teams using Cometly, the AI ads manager can surface recommendations alongside alert data, helping your team prioritize which campaigns to scale and which to pause rather than making those decisions from scratch under pressure.
Document your playbook in a shared location accessible to every team member who might need to respond. Include an escalation path for each scenario. If the first responder cannot resolve the issue within a defined timeframe, the playbook should specify who gets notified next and what information they need to receive.
Review your playbook quarterly and update it based on patterns you observe from past alert responses. Over time, your playbook becomes a knowledge base of how your campaigns behave and how your team has learned to respond effectively.
Step 7: Review Alert Performance and Refine Over Time
Your alert system is not static. The campaigns it monitors change, the baselines it references shift, and the team using it develops new patterns of response. Building a regular review cadence into your process is what keeps the system accurate and useful over time.
Set a monthly cadence to review alert performance. Track three things: how many alerts fired, how many required action, and how many were false positives. These three numbers tell you almost everything you need to know about whether your thresholds are calibrated correctly.
A high false positive rate means your thresholds are too tight. Your team is receiving alerts on normal performance variance and will eventually start ignoring notifications. Loosen your thresholds and shift toward rolling averages that account for more historical context.
A low alert frequency combined with ongoing performance issues means your thresholds are too loose. Real problems are slipping through without triggering notifications. Tighten your thresholds and consider adding leading indicator alerts that catch problems earlier in the performance degradation cycle. Reviewing your marketing performance analysis process regularly helps you identify which thresholds need adjustment before they become a systemic problem.
Use Cometly's customer journey analytics and pipeline attribution data to validate whether your alerts are catching the issues that actually affect revenue, not just surface-level metric fluctuations. An alert system that catches CPL spikes but misses pipeline contribution drops is only doing half its job for a B2B SaaS team.
As your campaigns scale and your data volume grows, consider adding AI-driven anomaly detection to complement your manual threshold alerts. Fixed thresholds are effective for known patterns, but gradual performance degradation over time can fall below threshold triggers while still representing a meaningful problem. AI anomaly detection identifies these subtle shifts that fixed thresholds miss, giving your team earlier warning on trends that would otherwise go unnoticed until they become significant.
Track the business impact of your alert system over time. Measure how quickly your team responds to alerts and whether faster response correlates with better campaign outcomes. This connects your alert system directly to business results and gives you a clear picture of the ROI your monitoring infrastructure is generating.
Success indicator: Your alert system produces a high signal-to-noise ratio, your team responds quickly and consistently, and your overall ad performance data shows fewer extended periods of underperformance. When your alert system is working well, you will spend less time reacting to campaign problems and more time making proactive decisions that improve results.
Putting It All Together
Setting up real time ad performance alerts is not a one-time task. It is an ongoing system that becomes more valuable as your campaigns grow and your data matures. The seven steps in this guide give you a structured path from defining the right metrics to building a response playbook your team can execute consistently.
The foundation of any effective alert system is clean, unified data. Without accurate attribution across all your channels, your alerts will fire on incomplete information and lead your team in the wrong direction. Cometly solves this by connecting your ad platforms, CRM, and website into a single attribution view, so every alert is grounded in reliable, real-time data. Every touchpoint from the first ad click to closed-won revenue is captured, giving your team the context needed to act with confidence rather than guesswork.
Start with three to five critical metrics, set tiered thresholds, and route alerts to the people who can act on them. Then refine your system monthly based on what you observe.
Here is a quick-start checklist to keep you on track:
1. Define your core campaign metrics and document your baselines.
2. Set warning and critical thresholds as percentage deviations from your rolling average.
3. Connect all ad platforms to a centralized attribution system with server-side tracking enabled.
4. Configure alert rules with the right time windows and campaign-level scope.
5. Route alerts to owners with full metric context included in every notification.
6. Build a response playbook for your most common alert scenarios.
7. Review and recalibrate your thresholds and playbook monthly.
With this system running, your team spends less time monitoring dashboards and more time making decisions that move the needle. Ready to build your alert system on a foundation of accurate, real-time attribution data? Get your free demo and see how Cometly connects every touchpoint to revenue so your alerts are always working from the right data.
