GA4 Ultimate Stack

Register a GA4 custom dimension on every property at once

Make an event parameter reportable across your portfolio: choose the properties, register the dimension once with a per-property dry run, and keep names consistent.

Why register a custom dimension

GA4 collects the parameters your tags send, but you can't report on most of them until a custom dimension is registered on the property. If form_name is sent on every brand but registered on only three, the other brands' reports can't break leads down by form.

Registration isn't retroactive. Data collected before the dimension existed won't fill in later, so register before the reports need it.

A parameter is collected, registered, then reportable from that point on.

Four steps: a parameter is sent, GA4 collects it, a dimension is registered on every property, then it is reportable.

Choose the properties

Open Dimensions Control Center and select the properties. Filter by property or account name to find them quickly. Free works on one property per run; Premium can select several.

With properties selected, Manage dimensions lists every custom dimension already registered on them. Check that list first: the dimension may already exist under a slightly different name.

Select the properties, then see every dimension already registered on them.

A property list with four properties ticked and a note that 38 registered dimensions are listed.

Add the dimension

  1. Choose Add new dimension.
  2. Set the display name (for example Form Name), the scope (event or user), the event parameter (for example form_name) and an optional description.
  3. Confirm which of the selected properties it should be registered on.
  4. Run the dry run.
One form, several properties. The dry run comes before anything is registered.

An add dimension form with display name, event scope, parameter and description, and four target properties.

Read the preview for each property

Each property is an independent write, so the dry run shows the proposed dimension for each one separately. If GA4 refuses one when you confirm, for example because that parameter is already registered there, that property reports the error and the others still go ahead. Checking Manage dimensions first avoids most refusals.

The proposed dimension for each property, before anything is registered.

A review dialog with a dry-run line for each of four properties.

Keep names consistent

Cross-brand reporting is easier when the same dimension has the same display name everywhere. Use edit to fix names like form name or FormName so every property says Form Name. You can change a dimension's display name and description; its parameter and scope stay as registered.

Two properties renamed to match the others. Parameter and scope don't change.

A table of registered dimensions where two variants of Form Name are renamed to match.

Event scope or user scope

Choose the scope from what the value describes. An event-scoped dimension describes one action, such as which form was submitted, and can differ every time. A user-scoped dimension describes the person, such as their plan or tier, and the latest value applies to them. Item-scoped dimensions can be registered in GA4 itself, but this module doesn't validate them.

Event scope describes the action; user scope describes the person.

Two panels comparing event-scoped and user-scoped dimensions with examples.

After you register

A registered dimension is only useful if the parameter is actually populated. Check it with Check parameters are populated, give new data time to arrive, and record what you registered, where and when.

Validate the parameter, allow time for new data, and record the change.

A checklist of three next steps after registering a dimension.

ODDVX for Windows

Every property, one screen.

Start free on one GA4 brand per run. Premium adds every brand in one run, batch writes, exports and scheduled checks.