Customer Match: Membership Duration, Refreshes and Audience Size

Customer Match membership duration limits how long an addition or refresh remains eligible for a list. Google documents a maximum of 540 days for standard Customer Match lists. A shorter duration can reduce the audience, but the size does not generally shrink in direct proportion to the number of days.

The distinction matters for targeting, exclusions and customer-acquisition signals. List membership, customer activity, consent and actual ad reach are different things. A list refresh can restart a membership clock without a new purchase or a new consent decision.

What is documented, and what needs account-specific confirmation

Google’s Customer Match policy states that additions or refreshes older than 540 days cease to be eligible. The policy also requires at least 100 members added or updated within that window for list eligibility. This is not the same measurement as the active-user threshold for ad serving.

As of 24 October 2026, the official sources checked for this article do not establish a general rule that a newer matching method always has a 60-day maximum. An account-specific option needs its own documented terms. The 60-day period below is an illustrative shorter duration, not a confirmed universal product limit. A change of matching method can also change the reachable population, making a comparison based only on duration inadequate.

When the simple formula works

The formula “size = daily additions × duration” describes a deliberately simplified model: the same number of genuinely new, distinct members arrives each day, no member is refreshed or removed early, every addition matches, and the process has run long enough to fill the entire window. Under those assumptions, 1,000 new members daily produce 60,000 members over 60 days and 540,000 over 540 days.

Illustrative membership models, not Google Ads forecasts

A. 1,000 distinct new members every day; no refreshes
   60-day window: 60,000    540-day window: 540,000
   Long / short = 9

B. The same 1,000 members refreshed every day
   60-day window: 1,000     540-day window: 1,000
   Long / short = 1

C. 9,000 members last added 100 days ago; no refresh
   60-day window: 0         540-day window: 9,000
   Proportional estimate: 9,000 x 60 / 540 = 1,000
   That estimate overstates the actual shorter-window count.

Case C shows why current size divided by duration is not a measured daily inflow. Repeat uploads, seasonality, old cohorts, removals and changing match rates can all invalidate the calculation. More repeat buyers do not guarantee a particular ratio or make the proportional estimate a safe lower bound.

Membership is not recent customer activity

A technical refresh is not proof of a recent purchase, valid current contact details or renewed consent. Repeated refreshes can keep the same member eligible for much longer than one configured duration. A 60-day setting therefore does not by itself cap a person’s total exposure to remarketing at 60 days.

A business rule such as “purchased during the last 60 days” belongs in the source selection. That selection needs actual purchase timestamps and removal of records that no longer satisfy the rule. Upload success, consent status and business eligibility require separate fields and checks.

Why list size is not reachable audience size

Uploaded rows, deduplicated customer records, matched Google users and active users eligible for a particular network are different counts. Google’s help currently specifies 100 active users for current customer lists on Search, Display and YouTube, with a separate caveat for old, unrefreshed lists. The relevant account status remains essential; 100 CRM rows are not a delivery guarantee.

Location, other targeting restrictions, bids, budget and account eligibility can further limit delivery. A list used only as an observation or bidding signal does not impose the same boundary as exclusive targeting. A shrinking list therefore does not necessarily stop an entire campaign.

A practical check before changing duration

1. The intended business rule and role are recorded: targeting, exclusion or a lifecycle signal.
2. Distinct eligible customer IDs are counted by the latest successful addition or refresh, with removals included. Business activity and consent are checked separately.
3. The proposed window is evaluated on those records across several dates, including seasonal peaks and quiet periods. Counts remain source-side estimates, not predicted Google reach.
4. Upload results, match information and active-user eligibility are checked after processing. Google notes that Customer Match uploads can take up to 48 hours.
5. The rollout retains a documented recovery path and monitors exclusions as well as delivery. No unnecessary customer data is copied for the test.