The key idea
Verify account scope, reporting boundaries and metric availability before evaluating a rule. Then check the trigger, submitted action and platform readback separately. A successful rule run alone does not prove that an ad was paused.
Define the objects and reporting boundary
Specify the accounts, advertising level and reporting window covered by a rule. An operator should be able to explain why an object is included and confirm that excluded objects are outside the scope. Record evaluation time, account time zone and data refresh time so spend and conversion value refer to the same period.
This is a verification method, not a universal pause threshold. The person responsible for advertising should define thresholds using the business reporting conventions.
- Confirm accounts, object level and filters.
- Confirm the reporting window, time zone, currency and conversion-value source.
- Identify who can change the rule and resolve exceptions.
Check availability before comparing values
An observed zero and an unavailable result carry different information. If a rule requires order value but the relevant business data has not synchronized, replacing the missing amount with zero cannot establish low ROAS.
Keep available data, pending updates, insufficient access and inapplicable metrics distinguishable in the review record. When a required metric is unavailable, inspect the data and the rule’s handling of that state before allowing execution. Missing evidence does not establish a business loss.
Recalculate a sample condition
This is a logic example, not a threshold recommendation or an actual campaign result. Suppose a rule requires spend of at least 100 and ROAS below 1. An object with spend of 120 and available conversion value of 60, under the same currency and reporting definition, has ROAS of 60 / 120 = 0.5. Both conditions are satisfied.
If spend remains 120 but conversion value is unavailable, the second condition cannot be established from the current evidence. Do not force a ROAS calculation when spend is zero either. Preserve the numerator, denominator and comparison operators when reviewing a decision.
Verify evaluation, submission and platform state separately
A completed evaluation can mean that no objects met the conditions. When an object does qualify, check whether an action was submitted, whether the platform accepted it and whether the corresponding state has been read back. Each step requires its own evidence.
Observing a paused object later does not by itself prove that this rule caused the change. Match object identifiers, action timestamps, operation records and readback times, and check for intervening manual actions or other rules.
- Evaluation: which inputs were used, and which objects qualified or were skipped?
- Operation: which action was submitted for which object, and what result was returned?
- Readback: which state was observed, when was it refreshed, and does it belong to the intended object?
Recover only the work that remains unresolved
When only part of a batch has confirmed results, list confirmed, failed and unresolved objects separately. A timeout or delayed readback does not necessarily mean the action did not happen. Check existing platform state and operation records before repeating work.
Record the issue, checks already performed, next action and responsible person. After data or access is restored, reevaluate the applicable conditions. An earlier trigger does not establish that the same action is still appropriate now.
Frequently asked questions
Does a successful rule run prove that an ad was paused?
No. Check qualifying objects, submitted action results and the corresponding platform readback, retaining timestamps for each step.
Can missing order value be treated as zero ROAS?
Do not replace unavailable conversion value with an observed zero. Establish coverage and reporting definitions before evaluating conditions that depend on the metric.
Should the whole batch be repeated after a timeout?
Inspect submitted actions and current platform state first. Separate confirmed, failed and unresolved objects, then recover work that remains incomplete.