CPA vs ROAS: build agency reports that explain the business

Define the outcome before comparing the ratio

Use CPA when the reported conversion is a meaningful, reasonably comparable outcome. For lead generation, distinguish raw submissions from qualified leads and customers. Use ROAS when conversion value is available and its business meaning is clear.

Google describes fixed and transaction-specific conversion values. A platform's value may represent revenue, an estimated lead value, or another configured measure. Label it accordingly. Google also distinguishes conversion-count and conversion-value bidding objectives.

ROAS is not profit. Product costs, fulfillment, fees, refunds, and other expenses can change the business outcome without changing the advertising ratio. Likewise, a low CPA is not automatically attractive when the leads rarely qualify.

Calculate totals from the underlying amounts

The formulas are:

• CPA: spend ÷ conversions.
• ROAS: conversion value ÷ spend.

Consider two illustrative campaigns in the same currency, using the same conversion definition:

A simple average of the two campaign CPAs is €20; that is not the account CPA of €25. Averaging the two ROAS values gives 2.5×; the combined return is 1.3×. Calculate from totals, not from an unweighted average of ratios.

Keep currencies separate unless you explicitly convert them

Do not add €1,000 and US$1,000 and label the answer “2,000 spend.” Keep a separate currency group, or use a documented exchange-rate method with the rate source, date, and treatment of historical amounts.

Unknown currency is a data limitation, not permission to assume the agency's home currency. Keep unlabelled monetary figures scoped to their account until the currency is resolved. Count metrics can also need separate definitions; two platforms may report different kinds of conversion under the same label.

When a report is incomplete or truncated, state that its totals cover the returned data. A precise ratio does not make an incomplete account scope complete.

Separate platform attribution from business reconciliation

Two advertising platforms can attribute the same customer purchase to their own ads. Adding platform-reported conversions is therefore not a reliable count of unique customers. Keep the platform view for platform decisions and reconcile business outcomes against the agreed order or CRM source.

Document the reporting dates, timezone, conversion definitions, and attribution settings used. Google explains how delayed conversions affect recent reporting. A report on yesterday's clicks can still change after the client receives it.

Present an observed difference as an investigation question when you do not have enough evidence to explain it. An attribution mismatch, a tracking error, and a real demand change require different responses.

Use a report structure that ends in a decision

Keep the main report short enough to use in a decision meeting:

1. The business outcome and reporting scope.
2. The material change compared with a fair prior period.
3. The campaign or funnel evidence explaining what to investigate.
4. The decision, owner, and approval needed.
5. The verification step and next review date.

Put detailed rows and definitions within reach, rather than replacing them with a single health score. A client should be able to trace a recommendation to evidence.

Turn the report into a reviewed action

If the report supports an advertising change, request its exact preview. Review the account, campaign, values, currency, and policy effects before approving the applying call. Read back the platform state and retain the audit record after the action.

For deeper investigation, use the Google Ads audit checklist. For agency access boundaries and ownership, use the multi-client management guide. The report and the operating process should reinforce each other.