Advertising that can't tell a new customer from a returning one pays to acquire people you already have. Yet acquisition and retention are two completely different things with different value and goals. Here's why the distinction is hard to measure and how to keep it.
Why the distinction matters
- Different value. The first purchase is acquisition, a repeat one is retention — and often far more profitable.
- Different targeting. You want acquisition ads aimed at new customers, not wasted on existing ones.
- Different KPIs. Cost per acquisition for acquisition, customer lifetime value for retention.
Why client-side loses it
Telling a new customer from a returning one rests on recognizing them on return. But Safari ITP caps client-side cookie lifetime at 7 days — if the customer returns a month later, they look new. The mechanism is in ITP and lost conversions.
How server-side keeps it
- Longer-lived identification. Server-set first-party cookies aren't subject to the 7-day cap, so you recognize a returning customer even after a while.
- User ID for signed-in customers. A signed-in customer is identified across devices — see what client_id and user_id are.
- Reliable capture. Server-side doesn't lose a visit to an ad-blocker, so the history stays complete.
What to do in practice
- Measure acquisition and retention as separate goals with their own KPIs.
- Aim acquisition ads at new customers, retention at existing ones.
- For repeat purchases, track customer lifetime value, not just one-off revenue.
Summary
Telling new from returning customers is the basis of efficient advertising — and it rests on reliable, long-lived identification that client-side loses to ITP. Server-side keeps it, so you don't pay to acquire those you already have. More in the complete guide.