Metrics

CPM

Updated 20 August 2026

Cost per mille (CPM) is the cost of 1,000 ad impressions, calculated by dividing ad spend by impressions and multiplying the result by 1,000.

Key facts about CPM

Abbreviation
CPM
Also known as
Cost per mille, Cost per thousand impressions
Formula
CPM = (ad spend ÷ impressions) × 1,000
Category
Metrics
Last updated
20 August 2026

In AdOps

How does CPM work inside AdOps?

CPM (`cpm`) is one of the 45 metrics in the AdOps rule builder, mapped to Meta's own cpm insight field, readable over any of the 11 reporting periods and comparable with all six operators.

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 mille (CPM) is what 1,000 ad impressions cost: ad spend divided by impressions, multiplied by 1,000. AdOps carries CPM as one of the 45 metrics in its rule builder, mapped to Meta’s own cpm insight field, so a rule can test delivery cost over any of the 11 reporting periods.

How is CPM calculated?

Rp 6,000,000 spent for 1,200,000 impressions gives a CPM of Rp 5,000. If the same Rp 6,000,000 buys only 600,000 impressions the following week, CPM has doubled to Rp 10,000, and every cost per result doubles with it unless click-through and conversion rates improve to compensate.

What does a rising CPM actually tell you?

CPM is an auction price, not a performance metric. It moves with audience competition, creative quality and demand, so the same audience can cost more in a heavy shopping week than in a quiet one. Rising CPM with a steady CTR points at the auction; rising CPM with a falling CTR points at the creative.

How is CPM used in an AdOps rule?

CPM accepts all 6 comparison operators and any of the 11 reporting periods. Because AdOps carries no frequency metric, the usual substitute is a compare-to-metric condition that tests CPM over Last 7 days against CPM over Last 30 days, so a rule notices when reaching the same audience has become more expensive.

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