How to Set Up Ad Spend Alerts on Meta, Google, and TikTok

Meta, Google, and TikTok do not offer the same alert workflow. Meta and Google can create notification-oriented rules. TikTok’s documented setup requires an action and separately lets you enable Notify Me, so it should not be described as a notification-only rule.

Key takeaways

• Build and test each platform’s rules separately; conditions, object scope, timing, and campaign support differ.
• Billing alerts belong in account notification settings, while new-campaign and access checks may require change-history review, a script, or third-party monitoring.
• Reporting and rule schedules introduce latency. An alert is not a guarantee of detection, containment, recovery, or reimbursement.

Before you create a rule

For each account, write down:

1. the campaign, ad set/ad group, or ad the rule should cover;
2. the metric and reporting window;
3. a static threshold in the account’s currency;
4. the recipient and escalation owner;
5. the rule schedule and account time zone; and
6. whether an automatic change is authorized.

A “120% of trailing 30-day average” threshold is not normally a dynamic native condition. Calculate the baseline yourself, enter a static threshold, and update it periodically—or use a script or monitoring service that explicitly supports baseline comparisons.

Meta: create a notification rule

Meta says automated rules can apply to campaigns, ad sets, or ads and can make changes or send notifications. Its current rule-creation instructions provide two entry points.

Menu path and setup

1. In Meta Ads Manager, either select the campaign, ad set, or ad, choose More, then Create a new rule; or open the Automated rules page and select + Create rule.
2. Choose Custom rule.
3. Under Apply rule to, choose the intended campaigns, ad sets, or ads.
4. Choose the notification-only action when that option is available in your account. Do not select a pause, budget, or bid action unless it has been explicitly approved.
5. Add a condition such as Amount spent > [your static threshold], then choose the matching time range, such as Today.
6. Set the Schedule and add the intended Subscriber.
7. Name the rule, review it, and select Create.

Meta notes that the schedule controls how frequently the rule is checked. Its automated-rule best practices say rules are usually checked every 30–60 minutes, so “continuous” does not mean event-stream detection and spend can continue before a check runs.

Scope and limitations

• Native scope is campaign, ad set, or ad—not an alert for a newly created campaign object.
• Available conditions and actions can differ by object and account.
• A spend rule relies on reported data and cannot inspect logins, malware, or individual requests.

Safe test

Use notification-only mode on one low-risk campaign. Set a threshold that the campaign is expected to cross during staffed hours, confirm the correct subscriber receives both in-product and email notifications where configured, and review rule activity. Do not test by adding an unapproved pause or budget action.

Google Ads: create an email rule

Google documents automated rules for campaigns and other supported entities. Its setup guide and common-use examples describe creating a rule from the relevant table or the Rules area.

Menu path and setup

1. In Google Ads, open Campaigns and select the campaigns to monitor.
2. Select the three-dot More menu and Create an automated rule. You can also open Rules from the Tools menu and create the applicable campaign rule.
3. Choose the rule type and set the action to Send email rather than changing campaign status or budget.
4. Apply the rule only to the intended campaigns.
5. Add a condition such as Cost > [your static threshold] for the chosen reporting window.
6. Choose the available frequency, time, and date range that fit your review process.
7. Choose the email results/notification setting and recipients, preview the rule where the interface offers a preview, then save it.

Scope and limitations

Google rule types and conditions vary by entity and campaign type. Rule results depend on reporting availability, so do not treat the run time as the time the underlying spend occurred. Google’s official Account Anomaly Detector explicitly allows for basic statistics to be delayed by up to about three hours; use the same caution when interpreting near-real-time account reports.

Safe test

Limit the rule to one known campaign, use Send email, preview the matching entities, and choose a threshold expected to trigger during staffed hours. Verify the email and rule log before expanding the scope.

Google billing and policy notifications

Billing failure is an account notification, not the same workflow as a spend rule. In Google Ads, go to Admin > Notifications to review account email topics; Google’s email-notification guide says billing alerts are managed through payment contacts in Billing > Settings. Ensure at least one monitored address receives critical campaign, policy, and billing messages.

Test routing by confirming the listed recipients and your organization’s mail rules; do not intentionally fail a live payment.

TikTok: create an automated rule with notifications

TikTok’s November 2025 automated-rule instructions require an Action and provide Notify Me as a separate setting. The documented flow does not support a purely notification-only rule.

Menu path and setup

1. In TikTok Ads Manager, select Campaigns in the top menu.
2. Select Automated Rules, then Create a New Rule.
3. Choose a custom rule or an appropriate template.
4. Under Apply rule to, choose campaigns, ad groups, or ads.
5. Define up to five conditions, such as cost crossing a static threshold.
6. Select the required Action. Only use a pause, budget, bid, or delivery action if it is explicitly configured and pre-approved.
7. Under Rule settings, choose Continuously, Custom, or Once.
8. Turn on Notify Me, add Business Center recipients, select the notification schedule, name the rule, and select Complete.

TikTok defines Continuously as every 30 minutes; Custom also checks every 30 minutes within selected days and times; Once runs at a selected time and then turns off. This is scheduled evaluation rather than event-triggered monitoring.

Scope and limitations

TikTok states that automated rules do not support reservation ads, Promote ads, or campaigns created in TikTok Shop Seller Center. Its documentation also says that if an account has more than 500 items in a selected tier, only the 500 most recently created items in that tier are included. Confirm current support in the interface before relying on the rule.

Safe test

Because the documented workflow requires an action, do not test it on a live revenue campaign unless that action has been approved. Use a dedicated test object, choose a reversible low-risk action, set a condition you can control, enable Notify Me, and confirm both action history and email delivery. If no production action is approved, use manual review or an external notification-only monitor instead of activating a TikTok native rule.

What belongs where

Native automated rules

Use for static metric conditions supported by the selected object, such as spend or cost crossing a threshold. Meta and Google can be configured for notification-oriented use; TikTok requires an action plus optional notification in its documented workflow.

Native account and billing notifications

Use for payment, billing, policy, and maintenance messages exposed by the platform’s notification settings. Confirm recipients and escalation ownership separately from automated rules.

Manual review checks

Use change history and campaign inventory to identify unexpected new campaigns, account-access changes, or conditions for which no native rule exists. A fixed review cadence is better than pretending that “new campaign created” is a standard spend-rule condition on all three platforms.

Scripts or third-party monitoring

Use when you need a dynamic baseline, cross-platform aggregation, custom routing, or supported account/security signals unavailable in native rules. For Google-only monitoring, the published Account Anomaly Detector script compares same-day performance with historical weekdays and emails on deviations. It depends on a spreadsheet configuration and accounts for reporting delay.

A starter control set

• Need: Daily spend ceiling; Recommended control: Native static spend/cost rule; Notes: Calculate the amount manually; align currency, time zone, and reporting window
• Need: CPA or cost-per-result ceiling; Recommended control: Native metric rule where supported; Notes: Add a sensible minimum data requirement to reduce noise
• Need: Spend flatline; Recommended control: Scheduled manual check, script, or monitor; Notes: $0 for three hours is not a reliable universal native-rule condition and reporting can lag
• Need: Unexpected campaign; Recommended control: Change-history/inventory review or supported monitor; Notes: Not a standard spend condition across all three platforms
• Need: Billing failure; Recommended control: Native billing/payment notifications; Notes: Maintain recipients independently of metric rules
• Need: Dynamic baseline; Recommended control: Script or third-party monitor; Notes: Document cold-start behavior and when sufficient history exists

Operating rules safely

• Start with notifications where the platform supports them without an action.
• Never attach an automatic pause or budget change unless the owner has explicitly pre-approved the scope and threshold.
• Test during staffed hours on a low-risk object.
• Record time zone, currency, reporting window, owner, recipients, and expected latency.
• Review rule activity after platform UI or campaign-structure changes.
• Recalculate static thresholds after planned scale-ups or seasonal changes.

FAQ

Which spend alert should I create first?

Start with a daily static spend ceiling for a narrowly scoped campaign or account segment. Derive the threshold from your approved plan and recent comparable days; do not copy a universal percentage. Add billing recipients and a documented escalation owner at the same time.

How often do native rules check?

Meta says rules are usually checked every 30–60 minutes. Google runs rules on the schedule selected. TikTok’s “Continuously” option means every 30 minutes. Reporting latency can delay the data each rule evaluates, so none guarantees an alert at the moment spend changes.

Can automated rules protect a compromised account?

Only partially. A spend rule may identify a metric change, but it does not detect every access, session, app, destination, or billing event. An authorized account user may also alter or remove rules. Containment requires platform remediation or an explicitly configured, pre-approved action; AdFence’s cross-platform hacked-account overview links preparation and recovery guidance.

Can AdFence use data from before connection?

Do not assume universal pre-connection history. Available history and cold-start behavior depend on what a supported platform integration exposes, plus permissions, configuration, and plan. A baseline-aware feature needs enough available data before it can make a meaningful comparison.

Bottom line

Meta, Google, and TikTok rules should be configured as three distinct systems. Use native rules for supported static conditions, account settings for billing notifications, manual or scripted checks for unsupported events, and explicit approvals for every automatic action. Test delivery and rule logs before treating any alert as operational.