CAC reporting automation

CAC is the metric most likely to be silently wrong, because it has the most moving parts: spend from four platforms, a customer definition that isn't 'install', and a denominator that must be deduplicated. Automating it means automating the *inputs and the definition*, not just a formula cell.

Why manual CAC drifts

Spend lives in four ad managers; customers live in the MMP. Stitch them weekly by hand and you get boundary mismatches, platform-claimed conversions double-counted against MMP events, and — the classic — CAC quietly computed on installs because that column was easier to find than purchase accounts.

Your definition, enforced

Opera stores the definition once and applies it every run: CAC = spend ÷ new customers, where 'new customer' is the event you count — a first purchase, a purchase, a First Subscription commerce Succeeded — pulled event-level from the AppsFlyer Raw Data Pull API and deduplicated per user. Channel CAC and blended CAC come from the same pass, so the blend can't flatter a channel that's off.

"Refresh blended and channel-level CAC for last week and flag anything above target."

What lands in the report

Safety and rollout

Same guarantees as every Opera report: schema re-validated, previewed append-only writes, duplicate periods refused, audit-logged. Start by locking the customer definition in writing, run one cycle in parallel with your manual number, then schedule it with a target threshold so breaches get flagged in the summary.