Library · Traffic · How to run this
Tracker CPU is not CRM CPS
Trackers report CPU (cost per unique click). Operators bid as if that were CPS. CRM-settled sales are the real denominator. Type spend $, unique clicks, and CRM sales.
Pair: CPU vs CPS on Traffic. Three books: tracker vs CRM vs settled. Bid cap: blended CAC.
What you type
Spend $ — ad spend for the window (same days as clicks and sales).
Unique clicks — tracker unique clicks for that spend.
CRM sales — settled sales count in CRM for the same window (not pixel purchases).
CPU = spend ÷ unique clicks. CPS = spend ÷ CRM sales. Click→sale % = CRM sales ÷ unique clicks. Kill and scale on CPS — not CPU.
What not to do
Do not invent a click-to-sale chip. Do not mix pixel purchases into CRM sales. Do not bid as if CPU were CAC. Do not blend affiliate and paid into this CPU without saying so.
Related: Traffic, tracker vs CRM vs settled, blended CAC, NC ROAS refund lag.
Procedure
- Type spend and tracker unique clicks.
- Type CRM-settled sales for the same window.
- Kill and scale on CPS.
Failure modes
- Inventing a click-to-sale chip.
- Mixing pixel purchases into CRM sales.
- Bidding as if CPU were CAC.
Worked example
None on this page yet. When one lands it will be a real case: what broke, the number, and what changed. Not a composite.
Glossary
- CPU vs CPS
- Cost per unique click from the tracker versus cost per CRM-settled sale on the same spend. CPS is the bid denominator.
Work with us — We run this job on your accounts. Services
FAQ
- Is this tracker vs CRM vs settled?
- Related books. [Tracker vs CRM vs settled](/manuals/tracker-vs-crm-vs-settled) names three dollar piles. This page is CPU vs CPS on the same spend.
- Is this blended CAC?
- No. [Blended CAC](/manuals/blended-cac) is spend ÷ settled new orders. This page keeps clicks and CRM sales as separate denominators.
- What click-to-sale percent should I invent?
- None. It falls out of unique clicks and CRM sales you type.