Build a Branch-Level Customer Acquisition Cost Report That Survives Repeat Visits and Transfers

A branch can acquire the customer while another branch serves them

A customer may discover a chain through one branch's campaign, enquire centrally, book at a second location and return to a third for a later purchase. If the report credits every touchpoint with a full new customer, the chain overstates acquisition. If it credits only the final branch, it may hide which campaign created demand.

Decide what “acquired” means

Finance and marketing should agree on the entity and event: first-ever customer, first purchase in a category, new customer to a branch, or reactivated customer after a defined period. These definitions answer different questions. A repeat purchase is revenue, but not necessarily a new customer acquisition.

Keep four fields distinct

• Acquisition source: the campaign or channel associated under the agreed attribution model.
• Acquisition branch/context: the location page or branch that initiated the enquiry, if known.
• Fulfilment branch: the location that completed the sale or service.
• Customer cohort: first purchase period or another finance-approved cohort key.

Do not overwrite source fields when a lead transfers between branches. Record transfer events and preserve the original touchpoint. For journeys across booking or payment domains, check whether analytics measurement is configured appropriately; Google's cross-domain guidance explains how domain transitions can split user/session measurement if misconfigured.

Choose a CAC formula that matches the question

A simple paid-media CAC can be calculated as eligible acquisition spend divided by newly acquired customers under the chosen definition. A broader blended CAC may include agency fees, creative and other approved acquisition costs. State what is included. Do not compare a media-only CAC in one region with a fully loaded CAC in another.

For a chain, report both acquisition-source economics and fulfilment-branch economics when the data supports it. The first helps evaluate demand generation; the second helps understand service delivery. Do not add the two reports together as if they represented different customers.

Handle edge cases explicitly

• A lead contacts two branches before buying: one customer, multiple interactions.
• A customer switches branch after a move: repeat customer or new branch customer depending on the stated metric.
• A household shares a phone number: identity matching may be uncertain.
• A sale closes months after the click: conversion windows and imported outcomes affect reporting.
• A customer is acquired organically but later sees an ad: attribution policy determines the assigned source; it is not proof of causality.

Reconcile monthly

Match CRM/customer records to completed transactions using approved identifiers and access rules. Report unmatched records, duplicates, branch transfers and late-arriving sales. Google Ads supports offline conversion measurement for eligible setups, but imports require a consistent event definition and should not be treated as a complete financial ledger. See the offline conversion FAQ.

Dashboard specification

Every CAC tile should state the customer definition, spend components, attribution model, reporting window, source system, branch assignment rule and data freshness. If identity resolution is incomplete, label the result “measured CAC for matched records” and disclose the coverage gap.

Decision use

Use CAC alongside contribution, repeat purchase behaviour and capacity—not as a standalone ranking of branches. A high CAC may be acceptable for a high-value service; a low CAC may hide poor retention or unprofitable fulfilment.

Sources

• Offline conversion imports FAQs — Offline conversion measurement, lead stages and common import issues.
• Set up cross-domain measurement — Cross-domain measurement and session continuity.