You create a GA4 audience, sync it to Google Ads, and then try to filter your Looker Studio dashboard by that audience. The filter appears but shows no data or incorrect data. This stems from how Looker Studio and GA4 handle audience filtering. Audiences are defined in GA4 but not always available or queryable in Looker Studio dashboards.

Why GA4 Audiences Don’t Always Work in Looker Studio

• Audiences update in GA4 in real-time as users meet conditions
• Audiences don’t export to BigQuery automatically unless you configure custom event tracking
• Looker Studio can see audiences only if GA4 explicitly exposes them – not all audiences are available
• Synced audiences to Google Ads are separate from GA4 reporting audiences

The Root Cause: No Audience Membership in Events Data

GA4’s events table (exported to BigQuery) doesn’t include audience membership information. It has event-level data: what the user did, when, from where. GA4 doesn’t add a field like audience_membership. This means even with BigQuery access, you can’t filter events by audience membership without reconstructing the audience logic in SQL.

Solution 1: Create Audience Logic Directly in Looker Studio

Instead of relying on GA4 audiences, create filtering logic in Looker Studio. Instead of audience filter “High-Value Customers,” create a filter using Event: purchase with Count >= 2 for repeat customers, or Event parameter: value with Sum >= $500 for high lifetime value customers.

Solution 2: Use User Properties for Audience Logic

Create GA4 custom dimensions from user properties, set the property value in your tracking code based on your business logic, then filter Looker Studio by that dimension value.

// Set user property for audience segmentation
gtag('set', {
  'user_properties': {
    'customer_segment': 'high_value',
    'engagement_level': 'active'
  }
});

// In Looker Studio: Add filter -> Customer Segment = "high_value"

Solution 3: Reconstruct Audience Logic in BigQuery

If you have BigQuery access, reconstruct audience membership by duplicating the audience logic in SQL, create a table of qualifying users, then join that table to events for filtering.

-- Recreate High-Value Customers audience in BigQuery
CREATE OR REPLACE TABLE `project.dataset.ga4_high_value_customers` AS
SELECT DISTINCT user_id, user_pseudo_id
FROM `project.dataset.events_*`
WHERE _TABLE_SUFFIX >= FORMAT_DATE('%Y%m%d', DATE_SUB(CURRENT_DATE(), INTERVAL 90 DAYS))
GROUP BY user_id, user_pseudo_id
HAVING
  COUNTIF(event_name = 'purchase') >= 2
  AND SUM(CASE WHEN event_name = 'purchase' THEN CAST(
    (SELECT value.float_value FROM UNNEST(event_params) WHERE key = 'value') AS FLOAT64
  ) ELSE 0 END) >= 500;

Why Audience Filters Often Show Zero Data

• Audience filter not supported: Not all GA4 audiences are queryable via the Looker Studio connector
• Audience has zero members: The audience definition isn’t matching any users
• Audience delay: GA4 audiences update with 24-48 hour delay; new audiences may be empty
• Filter too restrictive: Combined filters may result in empty data set

Best Practice: Custom Dimensions Instead of Audience Filters

For reliable Looker Studio filtering, use custom user properties and dimensions instead of GA4 audiences. Create user-scoped custom dimensions for segments you care about, set the dimension value in your tracking code based on backend business logic, and filter Looker Studio by that dimension value. This approach is deterministic and always works.

Looker Studio’s audience filter limitations are a known constraint of the GA4 connector. Custom dimensions and properties give you more control and reliability for dashboard filtering.

Related guides: GA4 Reporting Identity, Looker Studio GA4 Data Freshness, GA4 Remarketing Audiences.