GA4 Custom Dimensions Not Working: The Complete Fix Guide

GA4 Custom Dimensions vs Universal Analytics

GA4 custom dimensions work differently from Universal Analytics. In UA, you set a custom dimension slot (cd1, cd2) in the hit and it appeared in reports. In GA4, you must explicitly register each event parameter as a custom dimension in the Admin panel before it appears in reports. Without registration, the data is sent to GA4 but not accessible in standard reports.

The Custom Dimension Registration Process

For a custom parameter to appear in GA4 reports:

1. GA4 Admin → Custom Definitions → Custom Dimensions → Create
2. Dimension Name: what you want it called in reports (e.g. "Subscription Plan")
3. Scope: Event (for event-level parameters) or User (for user properties)
4. Event Parameter: the exact parameter name as sent in the GA4 event (e.g. "subscription_plan")
5. Save

Important: GA4 only starts collecting data for custom dimensions after they are registered. Historical events sent before registration do not populate retroactively.

Common Custom Dimension Failures

1. Parameter Name Mismatch

The most common failure: the custom dimension is registered with parameter name "subscriptionPlan" (camelCase) but the event sends "subscription_plan" (snake_case). GA4 parameter matching is case-sensitive and exact.

Fix: verify the exact parameter name being sent in GA4 DebugView → click the event → see the parameters list → note the exact name → update the custom dimension registration to match exactly.

2. Cardinality Limit

GA4 reports truncate high-cardinality dimensions. If a custom dimension has thousands of unique values (like a product SKU or transaction ID), the report will show "(other)" for many values. GA4 limits distinct dimension values in reports to manage data processing load.

Workaround: for high-cardinality data, use BigQuery export and query there rather than the GA4 interface. Standard GA4 reports are not suitable for high-cardinality dimensions.

3. Custom Dimension Limit Reached

GA4 limits: 50 event-scoped custom dimensions and 25 user-scoped custom dimensions per property. If you hit the limit, you cannot add more. New parameter data will be sent but not registerable.

Fix: audit existing custom dimensions — remove any that are no longer used (archived, not deleted, to preserve historical data) before adding new ones.

4. Data Freshness Delay

Custom dimension data in standard reports has a 24-48 hour delay. If you just registered a custom dimension and check reports immediately, it will appear empty.

Fix: use GA4 DebugView to verify parameter data is being received in real-time. Wait 24-48 hours for the data to appear in standard reports.

Summary

GA4 custom dimensions require explicit registration in Admin → Custom Definitions. Data only populates from the registration date forward. Failures are most commonly caused by parameter name mismatches (case-sensitive, exact match required), cardinality limits (use BigQuery for high-cardinality data), hitting the 50-dimension limit, or not waiting for the 24-48h data processing delay. Always verify parameter names in DebugView before registering custom dimensions.

See our Conversion Tracking Fix service for GA4 configuration support.

Need GA4 custom dimensions fixed? Contact Adslytics.