Metrics

Cost per lead

Updated 20 August 2026

Cost per lead is the average advertising cost of acquiring one lead, calculated by dividing ad spend by the number of leads recorded in the same period.

Key facts about Cost per lead

Abbreviation
CPL
Also known as
Cost per lead, CPL
Formula
Cost per lead = ad spend ÷ leads
Category
Metrics
Last updated
20 August 2026

In AdOps

How does Cost per lead work inside AdOps?

Cost per lead (`cost_per_action_type.lead`) is one of the 45 AdOps rule metrics and sits beside Leads (`actions.lead`) and Leads value (`action_values.lead`), so one rule can test the volume, the cost and the value of leads in a single AND group.

The AdOps metric picker open over a condition row: a panel with Meta Ads and Custom metrics tabs, a search box, and a scrolling list of metrics with Spend selected. Sample data
Forty-five Meta metrics and your own sheet columns in the same list, each carrying a reporting period and any of six operators. Read the details

Cost per lead is what one lead costs on average: ad spend divided by the leads recorded in the same period. AdOps carries it in the rule builder as Cost per lead, one of the 15 metrics in its cost_efficiency category, and pairs it with Leads and Leads value so a rule can weigh cost against quality.

How is cost per lead calculated?

Divide spend by leads over the same window. A campaign that spent Rp 9,000,000 in the last 7 days and produced 450 leads has a cost per lead of Rp 20,000. If only 90 of those leads convert at Rp 300,000 of gross profit each, the campaign earned Rp 27,000,000 against Rp 9,000,000 of spend.

Why is cost per lead alone a weak threshold?

Cost per lead falls when lead quality falls, because a form that asks for less produces more leads at a lower price and fewer of them close. That is why AdOps also carries Leads value, so a rule can require both a cost ceiling and a value floor before it scales a lead campaign.

How do you write a cost-per-lead rule in AdOps?

Pick Cost per lead as the metric, choose a reporting period from the 11 available, pick one of the 6 comparison operators, and set the threshold. Add a second condition on Leads over the same period so a campaign with two cheap leads cannot trigger the action, then join the two with the AND group operator.

Glossary

The terms an advertiser usually reads in the same sitting.

Turn this metric into a rule that watches it.

Pick the metric, pick one of the 11 reporting periods, set the threshold, and choose what happens when it is crossed. Nothing runs on your campaigns until you set the rule live.

Contact us See pricing

14-day trial · no card

Inside the product

What the screens actually look like

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.

  • The AdOps Performance Dashboard showing a Purchase ROAS card at 2.380x and an Aggregated ROAS card at 2.088x, both badged Profitable, a Monthly Budget card at Rp 155jt, and a Spend Breakdown ranking the top five ad accounts against a budget utilisation bar at 45.5 per cent.
    Performance Dashboard. Two ROAS figures to three decimals, a budget meter, and spend ranked by ad account — over Today, Last 7 days, Last 30 days or This month.
  • The AdOps rule list showing twelve automation rules, each with an on/off toggle, the ad accounts it manages, and when it last triggered — some minutes ago, others on a dated timestamp.
    Rule List. Every rule, what it manages and when it last fired. The toggle is the only thing between draft and live.
  • The AdOps condition builder showing a task with time-of-day conditions across seven day tags, a nested AND group holding a lifetime spend condition under 400,000, and a second task with four stacked metric conditions.
    Conditions. Metric, period, operator, value — joined with AND or OR, and nestable, so a rule can say something a dropdown cannot.
  • The AdOps metric picker open over a condition row: a panel with Meta Ads and Custom metrics tabs, a search box, and a scrolling list of metrics with Spend selected.
    Metric picker. Forty-five Meta metrics and your own sheet columns in the same list, each carrying a reporting period and any of six operators.
  • The AdOps dayparting timetable: a grid of hours against the seven days of the week, with the daytime hours filled navy for every day and the night hours and weekend evenings left empty.
    Dayparting grid. Or draw the hours instead. Anything outside the shape you fill in simply does not run.
  • An AdOps execution log detail: one campaign, two action panels badged Not Executed, each listing the action parameters and every condition evaluated with its actual value, its expected value and a Pass or Fail badge.
    Rule Log detail. Why a rule did nothing is recorded as carefully as why it did something — actual against expected, condition by condition.
  • The AdOps activity log listing budget increases and campaign renames, each row naming the affected campaign by id, the rule that caused it and how long ago it happened.
    Activity Log. One row per change AdOps made in your account, naming the campaign and the rule responsible.
  • The AdOps ad account list: eighteen Meta ad accounts with on/off toggles, account ids, Active or Inactive badges and this month’s spend in rupiah.
    Ad Accounts. Accounts discovered from Meta arrive switched off. Nothing is read, and nothing is changed, until you turn one on.
  • The AdOps custom metric editor mapping a Google Spreadsheet: a spreadsheet id, a sheet name, a column to match campaigns on and a column holding the values.
    Custom metric. Point AdOps at a sheet, name the matching column and the value column, and your own number joins the metric list.

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