When a remarketing audience is not populating or shows as too small to serve, the cause is almost always one of seven things: the tag or pixel is not firing on the pages the rule watches, the rule does not match the URLs or event names your site sends, consent is withholding the personalization signal, the GA4 link or Google signals is off, the membership or retention window is too short for your traffic, the list is under the network minimum, or a policy restriction is blocking it. Check the tag first, the rule second and the account settings last, then widen the window until the list clears the threshold.
A remarketing audience is a list of people the ad platform has seen on your site. In Google Ads it is a data segment, found under Tools, Shared library, Audience manager, in Your data segments. It fills from the Google tag, from GA4 audiences shared through a linked property, or from a customer list. In Meta it is a website custom audience, built under Audiences in Ads Manager from Meta Pixel and Conversions API events, with rules on URL, event name and parameters. The flow is the same on both: an event arrives, the platform matches it to a person, checks consent and policy, and adds that person to every list whose rule they meet for the duration you set.
The seven causes we find most often.
We run this check on our own sites and on every account we take over. Ordered by how often each is the answer:
- Tag or pixel silent on the watched pages: the Google tag or Meta Pixel is missing from the template, loads after the event, or has no ID set in production
- Rule does not match reality: the URL changed in a redesign, the rule uses equals on URLs that carry query parameters, or the event name casing differs from what the site sends
- Consent withholding the signal: ad_personalization is denied by default and the banner never sends the update after the visitor accepts
- GA4 audiences not shared: no Google Ads link, personalized advertising off on the link, or Google signals not activated
- Window too short for the traffic: a 7 day window on a site with a few hundred weekly visitors hovers around the minimum forever
- Below the network minimum: the list is growing but has not reached the active user count the network needs
- Policy or region restriction: a restricted category, ads personalization disabled for the visitor's region, or a Meta audience flagged for suggesting health or financial information
How to verify where the audience breaks.
Start with what the platform says about the list, then confirm what leaves the browser. Three checks, in this order.
The audience table. In Google Ads Audience manager, read each segment's size per network and its status, then confirm the Google tag and Google Analytics sources show recent activity. In Meta Ads Manager, read the availability column under Audiences. In the Marketing API this is delivery_status: code 200 means ready, code 300 means the audience is smaller than it should be and cannot be used.
Tag Assistant and Meta Test Events. Run Google Tag Assistant on the watched page and confirm the Google tag fires with the right ID and that ad_personalization shows granted after you accept the banner. In Meta Events Manager, use Test Events and browse the exact pages and actions your rule depends on. If the event does not show there, no rule can catch it. Our Meta pixel not firing guide and tag manager troubleshooting guide cover that layer.
The GA4 link. In GA4, check Admin, Product links, Google Ads links, for a link with personalized advertising enabled, and confirm Google signals is on under Data collection. Google says GA4 and Google Ads sizes will differ, but a populated GA4 audience next to an empty Google Ads list points at the link, signals or ads personalization settings, not the tag.
Diagnose top to bottom.
Each step isolates one layer. Stop at the first real failure and fix it before moving on.
| Symptom | Likely cause | Fix |
|---|---|---|
| Google Ads segment shows 0 on every network | Google tag not firing, or the rule matches no real URL | Check the tag in Tag Assistant on the watched pages, then test the rule against real URLs |
| Segment growing but marked too small to serve | Under 100 active users in the last 30 days for that network | Raise membership duration, broaden the rule, or target a list that already clears 100 |
| GA4 audience has users, Google Ads list is empty | No Google Ads link, personalized advertising off, or Google signals off | Link the property with personalized advertising on and activate Google signals |
| List much smaller than GA4 sessions suggest | Consent leaves ad_personalization denied for most visitors | Fix the banner's consent update call; do not bypass consent |
| New segment still small after one day | Normal population time | Wait 48 to 72 hours before changing anything |
| Users from one country never appear | Ads personalization disabled for that region in GA4 | Review region settings in GA4 data collection, keeping legal requirements in place |
| Meta custom audience shows as too small or unavailable | Pixel silent on the pages or events in the rule, or retention window too short | Confirm events in Test Events, then raise retention toward 180 days |
| Meta event based audience stays empty while pixel fires | Event name or parameter in the rule does not match what the site sends | Copy the exact event name and parameter keys from Test Events into the rule |
| Meta ad set shows with issues, audience blocked | Audience flagged (operation_status 471) for suggesting health or financial information | Remove the sensitive URL or event terms from the rule, or drop remarketing for that page |
Google Ads and GA4 specifics.
Google Ads segments default to a 30 day membership duration, with a maximum of 540 days on Display and Search. A segment not used in targeting for 540 days is set to Closed: it keeps members until they expire but adds nobody new until you reopen it. Check the status column before you check the tag.
A GA4 audience accumulates users from the moment it is created, and for the Google Ads list Analytics adds users who met the criteria in the previous 30 days when that data is available. Google notes a new audience can take 24 to 48 hours to start accumulating. GA4 membership can run up to 540 days. A narrow audience created yesterday looks broken when it is just young.
Consent matters more for audiences than for conversions. With ad_personalization denied, Google states remarketing in Google Ads receives no data from that visit, and nothing models those visitors back onto a list. Customer lists reach known customers instead, and lists uploaded or refreshed after February 1, 2024 follow the same 100 active user rule. The hashing work overlaps with our enhanced conversions setup.
Meta specifics.
A Meta website custom audience retains people for 1 to 180 days. Unlike GA4, it can prefill: by default it includes website activity from before the audience was created, up to 180 days back. That makes it a strong diagnostic. Build an all visitors, 180 day audience on a site with steady traffic; if it comes back unavailable, the pixel has been silent or blocked for months. Meta only says an audience must reach a certain size before you can target it, so treat the unavailable status as the signal, not a count.
Event rules fail quietly. A Purchase rule with a value condition only catches events that carry value. A custom event rule only catches the exact name. Conversions API events feed these audiences too, so a well matched server copy keeps lists filling when browsers block the pixel. See our Conversions API setup guide and the piece on low event match quality.
What is normal and what is a red flag.
Expected: Google Ads sizes will not equal GA4 user counts, and sizes differ by network, so a list can be eligible on Display and smaller on Search or YouTube. A new Google Ads segment needs 48 to 72 hours to fully populate, a GA4 audience 24 to 48 hours to start accumulating. A site with a strict consent banner runs smaller lists than its sessions.
Red flags: a segment at zero on every network after three days of normal traffic, a Meta all visitors audience with 180 day prefill that comes back unavailable, a GA4 audience with thousands of users next to an empty Google Ads list, or a sharp drop on one date, which almost always lines up with a release, a consent tool change or a shortened duration. We log audience sizes weekly as part of our conversion tracking audit checklist so a dated drop points straight at its cause.
Why is my Google Ads remarketing list too small to serve?
Google Ads requires at least 100 active visitors or users in the last 30 days for a data segment to serve on Display, Search or YouTube. If your list is growing but under that number, raise the membership duration or broaden the rule. If it shows zero, check that the Google tag fires on the pages the rule watches.
How long does it take for a remarketing audience to populate?
Google says a new Google Ads data segment can take 48 to 72 hours to fully populate, and a new GA4 audience 24 to 48 hours to start accumulating. A Meta website custom audience with prefill includes up to 180 days of past pixel activity, so it shows members quickly if the pixel has been firing.
Why are my GA4 audiences not showing in Google Ads?
The GA4 property must be linked to the Google Ads account with personalized advertising enabled, and Google signals must be active, which Google lists as a requirement for all web remarketing. Audiences built on events, user properties or regions excluded from ads personalization in GA4 are also not exported.
Does consent mode stop remarketing lists from growing?
Yes, for visitors who deny it. When ad_personalization is denied, Google tags send no data for remarketing in Google Ads. Check that your consent banner sends an update call setting ad_personalization to granted when a visitor accepts, because a missing update keeps every visitor in the denied state.
Why does my Meta custom audience say it is too small when the pixel works?
The pixel can fire while the rule still misses. Match the URL or event name to what Test Events shows, confirm parameter conditions such as value are actually sent, and lengthen the retention window. If the ad set shows with issues, the audience may be flagged for suggesting health or financial information.