Stop paying above the target cost per lead
When
- Spend Today > Rp 1,500,000
- AND Leads Today < 10
Then
- Pause campaign
- Add to name Append mode · [CPL-OVER {date}]
Use case
AdOps defends a cost-per-lead target by checking spend and lead volume in the same reporting window, then pausing and tagging any campaign that breaks the agreed ratio. A second rule can start a paused campaign again once its lead volume recovers, so a temporary dip does not end the campaign permanently.
Rules that hold a cost-per-lead target by comparing spend and lead volume in the same window, then pausing or resizing the campaigns that miss it.
Situation
The problem this playbook was written against, and what the account looks like once the rules are live.
Cost per lead drifts past target for six hours before anyone notices, and a broken form or a dead pixel can burn a full day of budget while the campaign still reports healthy click volume.
Spend and lead volume are checked together on the same interval, campaigns that break the ratio are paused and tagged in the campaign name, and campaigns that recover can be started again by a second rule.
Playbook
Each card is one rule, printed the way the AdOps rule builder prints it: conditions on top, actions below the hairline.
Every threshold below is an example. Change the numbers to fit your account before you set a rule live.
When
Then
Why this rule
Rp 1,500,000 spread over fewer than 10 leads is a cost per lead above Rp 150,000, so the rule reads exactly the arithmetic the buyer does.
When
Then
Why this rule
300 link clicks with zero leads is usually a landing page or pixel problem, and the timestamp in the name says when delivery stopped converting.
When
Then
Why this rule
Rp 1,000,000 for fewer than 5 leads in the first 48 hours is a result, not a warm-up period.
When
Then
Why this rule
Under Rp 100,000 per lead across a full week is a campaign worth more money, and the 12-hour cooldown caps it at 2 raises a day.
When
Then
Why this rule
A campaign paused on one bad day should not stay off all week, and removing the tag keeps the campaign list honest.
Sample data Key facts
AdOps defends a cost-per-lead target on Meta Ads by writing the target as a rule instead of a reminder. A rule pairs a Spend condition with a Leads condition over the same reporting period, and when the pair breaks, AdOps pauses the campaign and appends a tag to its name on the interval you set, as often as every 15 minutes.
Lead volume and spend move at different speeds. Spend is continuous and lead delivery is lumpy, so a campaign can look fine at 10:00 and be 40 percent over target by 16:00 without a single alarming number appearing on any one screen. The gap is not knowledge, it is attention.
The second failure is quieter. A form that stops submitting, a pixel that stops firing, or a landing page that returns an error will not slow Meta down. Delivery continues, clicks keep arriving, and the only visible symptom is that leads stopped.
Write it as the arithmetic, not as the ratio. Spend today greater than Rp 1,500,000 combined with Leads today less than 10 is a cost per lead above Rp 150,000, and both halves are metrics the engine reads straight out of a batched Meta Insights call.
Writing it this way has a practical advantage: you choose the spend floor that makes the test meaningful. A campaign that has spent Rp 200,000 today has not earned a verdict yet, and the spend condition is what keeps the rule quiet until it has.
The AdOps rule builder exposes 45 metrics over 11 reporting periods. For lead generation the working set is small: Spend, Leads, Leads value, Link clicks, Clicks, CTR (link clicks), CPC (link), Landing page views, Impressions and Hours since creation.
Landing page views deserve a place. Comparing Link clicks against Landing page views over the same period tells you whether people are arriving at all, which is a different failure from arriving and not converting.
| Symptom | Condition pair | Action |
|---|---|---|
| Cost per lead over target | Spend today, Leads today | Pause campaign and tag the name |
| Form or pixel broken | Link clicks today, Leads today | Pause campaign and tag the name |
| New campaign never started | Hours since creation, Spend lifetime, Leads lifetime | Pause campaign |
| Beating target on volume | Leads last 7 days, Spend last 7 days | Increase budget by 15 percent |
Three controls. The check interval sets how often the rule is evaluated, chosen from 10 values between 15 minutes and 72 hours. The action frequency sets a cooldown on the action itself, with 11 values from 15 minutes to once in a lifetime, available on Increase budget, Decrease budget, Set budget, Duplicate and Notify. The pre-filter sets which campaigns the rule may touch at all, using Campaign ID, Campaign Name or Campaign Status.
Campaign Name as a pre-filter is the one lead-gen teams underuse. If every campaign for one offer carries a shared prefix, a rule pre-filtered to campaigns whose name contains that prefix inherits the offer’s own cost-per-lead target without anyone maintaining a list of campaign IDs.
The pause is not the end of the workflow. A second rule, pre-filtered to Campaign Status is PAUSED, can look at Leads and Spend over the last 7 days and start the campaigns that came back, then use Remove from name to clear the tag the first rule wrote. The shipped template library includes a Re-enable Paused Winners recipe built on that pattern, alongside Pause + Tag Failed and Stop and Label Campaign.
Each pass leaves evidence. AdOps writes a batch record and a per-campaign, per-task result, and the Rule Log Detail screen shows the badge, the parameters the action used, the execution time in seconds and the next scheduled execution.
AdOps evaluates what Meta reports. A lead that Meta counts but your CRM rejects is still a lead to the rule, so a rule can defend cost per lead but not lead quality. If your true target lives downstream, the custom metric feature can read a number you maintain in a Google Sheet and compare a live Meta metric against it. AdOps connects to Meta Ads only today.
Questions
Yes. The dependable way to write it in AdOps is a two-part condition joined with AND, such as Spend today greater than Rp 1,500,000 and Leads today less than 10, which is the same ratio expressed with two metrics the engine reads directly from Meta Insights.
A rule can compare traffic against outcomes in the same window, for example Link clicks today greater than 300 and Leads today equal to 0. That combination separates a delivery problem from a conversion problem, because the clicks prove Meta is still spending.
Yes. Start is one of the 11 executable actions, and a rule pre-filtered to Campaign Status is PAUSED can evaluate the last 7 days of results and start the campaigns that recovered. Remove from name clears the tag the pausing rule added.
A rule holds a single group of conditions joined by one AND or one OR, evaluated against a batched Meta Insights read. Nested two-level groups are not available in AdOps, so a policy that mixes AND and OR is written as two rules.
Yes. Every run writes a batch record plus one result per campaign per task, and the Rule Log Detail screen shows an Executed, Not Executed or Skipped badge, each condition marked Pass or Fail with the value it read, and the execution time in seconds.
Related
Every rule on this page is built from conditions and actions that ship in AdOps. Point them at one ad account and watch the log before you widen the scope.
Inside the product
Nine screens from the working dashboard — the rule builder, the metric picker, the dayparting grid and the log that records what happened. Scroll the strip.
Every figure is rebuilt from the product’s own interface and filled with invented data — no customer name, ad account or spend figure appears anywhere on this site. See how a run works