GA4 Ultimate Stack

Roll out one channel group taxonomy to every GA4 property

See every property's channel groups in one coverage matrix, save an agreed taxonomy as a template, and apply it across properties with a per-property diff before anything is written.

One taxonomy, many properties

Channel groups decide how GA4 sorts traffic into Paid Search, Paid Social, Email and the rest. When brands use different groups, or the same group with different rules, "Paid Social is up 20%" means something different on every property.

Channel Groups Vault reads every channel group on the properties you select into one coverage matrix: rows are group names, columns are properties. A group missing on one brand, or carrying a different number of channels, is visible without opening anything.

Rows are channel groups, columns are properties. The gaps and mismatches stand out.

A coverage grid with the read-only Default channel group, a Portfolio Channels group missing or different on two brands, and a second group on only two brands.

Save the agreed taxonomy as a template

Pick the property whose group is right, agree it with the client, and save its channels as a template. A template is the channels and their order, nothing else: no property or account ids. You can apply it to any property your Google account can see. Free keeps one saved template.

A template keeps the channels and their order, and nothing that ties it to one property.

Brand A's five ordered channels saved as a template named Portfolio Channels v3.

Apply it to many properties

Select the target group on each property and choose Apply template. Applying replaces the target group's channels with the template's, in the template's order. The dry run shows a diff per property first. Applies then run one property at a time and stop at the first error, so a problem costs one property, not twelve. Free writes one property per action; Premium can write several in one batch.

One template, five properties: two would change, one already matches, one is refused because it's GA4's read-only default.

A template fans out to five properties marked no change, would replace, or refused.

Add, reorder, rename and delete

  • Add channel appends a channel at the bottom, the lowest priority, so it can't take traffic from existing channels until you move it up.
  • Move up / down changes which channel wins. See why channel order matters.
  • Edit conditions uses GA4's own shape: groups of OR conditions combined with AND, each of which can be negated.
  • Rename a group, or delete a group or individual channels behind a type-the-name confirmation.
Six actions, each previewed per property before it runs.

A two-column list of channel group actions: apply, add, move, edit conditions, rename and delete.

Rules GA4 enforces

Three changes are refused before anything is sent to GA4:

  • GA4's Default channel group is read-only. Use a custom group as your target.
  • A property's primary channel group can't be deleted, because GA4 reports read from it.
  • A group can't be left with no channels. Delete the group instead.
Three changes GA4 won't accept, refused before anything is sent.

A list of three locked rules: default group read-only, primary group not deletable, group not empty.

Read the diff, then confirm

For each property the diff lists every channel that would be added, moved or removed. It is exactly what will run. Confirm, and the change is written straight to GA4. Channel groups affect reporting from that point on. Before rolling out widely, apply to one property and check its reports. See GA4 change control.

Added, moved and removed channels for one property. The diff is what runs.

A review dialog for one property's channel group showing a channel added, one moved and one removed.

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.