First, confirm the size where it matters
Note three facts before changing anything. The audience's creation date, from the audiences list in admin, because a list created this week has had only this week to collect members. Its size in Google Analytics, shown in the same list. And, if it is meant for advertising, its status and size in the Google Ads audience manager, where shared lists appear among the account's data segments. Zero in the property is a definition or timing problem. Members in the property but nothing usable in Google Ads is a sharing problem.
Then test the definition. Open an exploration, build a segment with the same conditions, scope and sequence, and apply it to a free-form table for the recent past. Because segments are retroactive, this shows immediately whether anyone has done what the audience asks for. If the segment is empty too, the conditions do not match real data. If the segment is healthy and the audience is empty, the audience is young or is evaluated differently. The explorations tutorial covers the segment builder, and if the property itself is receiving nothing, the sibling page on GA4 not showing any data comes first.
Diagnosis table
Diagnosis
| Symptom | Check | Likely cause | Fix |
|---|---|---|---|
| Audience and matching segment are both empty | The condition's event and parameter names against the events report and DebugView | Conditions reference events or parameters that never arrive | Rebuild conditions on the names and values actually received |
| Segment is healthy, audience is empty or small | Creation date against the period the segment covers | Audience created recently: no backfill for the conditions used | Allow time to accumulate; create audiences ahead of campaigns |
| Segment with session or event scope matches, audience barely grows | Scope, sequence steps and time constraints in the definition | Scope or sequence conditions narrower than intended | Loosen the scope or sequence to the behaviour you meant |
| Members in the property, list missing from Google Ads | Product links, the link's personalised advertising setting and the property's data settings | Google Ads link or personalised advertising settings missing | Link the account and enable personalised advertising where policy allows |
| List in Google Ads far smaller than in the property | Advertising consent share and regional personalisation settings | Consent limiting which users can be added | Expect the gap; report reach from the Google Ads figure |
| List visible in Google Ads but marked too small to serve | The list's status per network in the audience manager | Below the minimum size for serving in Google Ads | Widen the definition or lengthen membership duration |
Fix, verify and prevent each cause
Conditions that never match
An audience built on an event that is spelled differently from what the site sends, a parameter that is not attached to that event, or a custom dimension that was never registered waits forever. Event names and values are case-sensitive, and a parameter used in a condition has to arrive on the event the condition names.
Fix: read the received names and parameter values in the events report and DebugView, register any custom dimension the condition needs, and rebuild the condition on what arrives, following the events and parameters guide; when the event itself is missing, the fix is in the Tag Manager (GTMTag management system.) container, not the audience.
Verify: the rebuilt segment returns users for recent dates.
Prevent: define audiences from the tracking plan's event names, never from memory.
Too new to have members
Audiences are evaluated as events arrive, from creation onward, and the help centre documents only limited pre-population. A list created the day a campaign launches has had no time to grow.
Fix: let it accumulate, and compare its growth with the retroactive segment to confirm it is collecting the right people, as the backfill section of the audiences guide recommends.
Verify: the size rises day by day in line with the segment's daily volume.
Prevent: create audiences well before the campaigns that need them, and keep a short list of standing audiences that are always collecting.
Definition narrower than meant
Scope decides whether conditions must hold across all sessions, within one session or on one event; sequences add order and sometimes a time limit. A within-event scope on two conditions that never share an event, a direct-follow sequence where other activity always intervenes, or a time window shorter than the real journey can leave a list nearly empty.
Fix: compare segments at each scope and sequence setting, then set the audience to the one that matches the intended behaviour, using the scope explanation in the audiences guide.
Verify: the corrected segment's size is plausible against the traffic it describes.
Prevent: write the audience's intent as a sentence first, then check the definition reads the same way.
Not shared to advertising
Audiences reach Google Ads only through a link with personalised advertising enabled, and only where the property's own data settings allow personalised advertising for the user's region.
Fix: create or repair the link and its setting, and review the property's regional settings, as the GA4 and Google Ads integration tutorial describes.
Verify: the audience appears in the Google Ads audience manager with a size.
Prevent: record the link, its settings and who changed them in the measurement change log.
Consent keeps users out
Users enter the shared list only when their consent signals permit advertising use. On sites where many visitors refuse advertising consent, the Google Ads list is much smaller than the property's count by design.
Fix: nothing to repair if the implementation is correct; confirm the consent signals are configured as the privacy, consent and measurement guide describes, and plan RemarketingAdvertising to previous visitors or engagers. reach from the Google Ads figure.
Verify: the ratio between the two sizes is stable over time.
Prevent: brief campaign owners on the expected gap before they size a campaign on the property's count.
Too small to serve
Each network applies a documented minimum list size, and a list below it is shown as too small. Short membership durations and narrow conditions on a low-traffic site are the usual reasons.
Fix: lengthen the membership duration, broaden the condition, or combine related audiences, keeping within the decision the campaign needs, as the GA4 and Google Ads integration tutorial notes under sharing audiences.
Verify: the list's status changes to eligible on the networks the campaign uses.
Prevent: estimate a new audience's likely size from the segment before creating it.
Prevention: building audiences against verified events
Audiences fail quietly because nobody looks at them until a campaign needs them. Build each one from a segment that has already returned plausible numbers, on event names copied from the tracking plan. Name it so a Google Ads user knows what it holds, and record its purpose, owner and creation date. Create standing audiences early for the journeys the business always markets to. After creation, check the size in both systems weekly until it is stable, and again after any release that touches the events it relies on, since a renamed event silently stops an audience growing. Review the list of audiences each quarter and archive the ones with no campaign attached, because each counts against the property's documented limit. When the link, consent setup or regional settings change, recheck every shared list.
A basket-abandoner list that stayed at zero
A homeware shop creates an audience of users who triggered add_to_cart without purchase within the same
session, for a reminder campaign starting in 10 days. After a week, the audience shows 0 members. A segment
with the same conditions is also empty. DebugView shows the site sends addToCart, a name left from an old
implementation, not add_to_cart. The analyst corrects the event name in the container and creates a new
audience on the correct name. Within 6 days it holds 2,300 users in the property and 1,500 in Google Ads, the
difference matching the shop's advertising consent rate, and the campaign launches 3 days late instead of
running against an empty list.
Common mistakes
Creating an audience the day a campaign starts. Building conditions from memory instead of received event names. Using within-event scope for conditions on different events. Reading the property's count as advertising reach. Editing a broken audience instead of testing a segment and starting a new one.
