Skip to content

Guide 90 · Admin · GA4 + Tag Manager

Event-scoped custom dimensions in GA4: register the parameter so it shows in reports

Checked 11 November 2026 · Verification: figures recomputed in Python 3, shown in the downloadable file · Steps traced to Google help and developer pages, opened 11 November 2026 · 6-minute read

A custom event parameter is collected but not shown in standard reports until you register it as an event-scoped custom dimension. Register it in Custom definitions.

Expected signal

After the trace, Custom definitions lists an event-scoped custom dimension with the exact event parameter name, and the dimension is usable in reports after 24 to 48 hours.

Download the reference: the event scoped custom dimensions reference (JSON) (462 bytes, MD5 168ebecec664e5df2c67c28c8a1c58d0). It holds the worked example from this guide with every figure recomputed. The file was built for this guide and checked the same day; it was not exported from a live property.

What you need

  • A custom event parameter already being sent, confirmed in the Realtime report.
  • Editor access at property level.
  • The exact event parameter name, copied from the event.

The trace

  1. Confirm the parameter is being collected. Select the event in the Event count by Event name card in the Realtime report. If the event is not there, the parameter is not being sent, and registering a dimension will not fix that.
  2. Open Admin, then under Data display click Custom definitions, then the Custom dimensions tab, then Create custom dimensions. You need Editor access or above at property level.
  3. Enter the dimension name. Google's example registers the payment_type parameter as Payment type, with the description The chosen method of payment. Hyphens are not allowed in the name; underscores and spaces are.
  4. Set Scope to Event. The scope cannot be changed after you save. An event-scoped dimension reports on a custom event parameter, which measures details about a user action captured through an event.
  5. Enter the Event parameter name exactly as the code sends it, for example payment_type. This field cannot be changed after you save. Case matters, and a parameter that already has a predefined dimension should not be recreated.
  6. Click Save, then wait 24 to 48 hours. You can add the custom dimension to any report after 24 to 48 hours from when the custom data was sent and the custom dimension was created. The worked example in the download counts the window from 11 November to between 12 and 13 November.

Dead ends

DEAD END — REGISTERING A PARAMETER THAT IS NOT SENT. The dimension will stay empty. DebugView and the Realtime report prove the parameter arrives; the registration only makes it appear in reports.

DEAD END — A NUMBER AS A DIMENSION VALUE. Google recommends alphanumeric values for event-scoped custom dimensions in apps, because integer values from event parameters are not parsed the same way. Use text values where you can.

DEAD END — EXPECTING THE DIMENSION IN STANDARD REPORTS AT ONCE. The 24 to 48 hour wait is real. A dimension checked an hour after creation will not appear, and that is not a fault.

End state

The dimension is Payment type, event-scoped, tied to the payment_type parameter, and usable between 12 and 13 November for data sent on 11 November. The parameter was confirmed in Realtime before registration.

Sources

Checked 11 November 2026. The click paths above are the ones in Google's help and developer pages, opened 11 November 2026. No step in this guide was run inside a live Analytics property or a live Tag Manager container, because both need a Google sign-in and this site does not sign in as anyone. The figures on this page were recomputed in Python 3 and are shown in the downloadable file, which was checked the same day. Google moves menu items without warning; if a path on this page no longer matches, the linked help page is the current map.