GA4 Ultimate Stack
Change a GA4 setting on many properties in one reviewed batch
Stage changes by value, from a reference property or from a baseline, preview them against live GA4, and apply them with a read-back, so a portfolio-wide settings change is one reviewed batch.
Three ways to stage a change
Every change starts as a staged change. Nothing is written while you stage. There are three ways to stage:
- Set value: tick the properties to target, pick a setting and choose the new value. Only values that property can take are offered. 26, 38 and 50 months of retention appear only for Analytics 360 properties.
- Match this property: the other loaded properties copy one reference property, one category at a time. Stream settings are copied from the reference's first web stream to every web stream of the targets.
- Match the baseline: every loaded property that differs from the selected baseline gets a change.
A four-step flow: set value, match this property, match the baseline, and the staged tray.
Check the staged tray
Staged changes collect in a tray, one row per property, stream and setting, and are marked gold in the matrix. Staging the same cell twice keeps the later change. Remove any row you don't want, or clear the tray.
A batch can hold up to 500 changes. Re-reading the settings clears the tray, because staged changes are only meaningful against the values you loaded.
A staged tray listing three changes with their old values and one change removed.
Preview against live GA4
Press Preview changes. ODDVX doesn't trust the values you loaded earlier: it reads every staged setting from GA4 again, right now, and shows the before and after for each property. Nothing is written.
If someone changed a setting in GA4 after you loaded it, that change is marked changed since loaded and blocked. Reload and review it rather than overwrite their work.
A dry-run review listing a change that will apply, one blocked because the value changed since it was loaded, and a retention change that needs typed confirmation.
| Status | What it means | What to do |
|---|---|---|
| will change | GA4 holds the old value; the new one is applied when you confirm | Check the before and after |
| no change | The property already has that value | Nothing |
| changed since loaded | GA4 now holds a third value nobody here looked at | Reload and review; it is blocked |
| needs confirmation | Shortening data retention deletes older data | Type SHORTEN to include it, or remove it |
| not supported | GA4 doesn't offer this value for this property or stream | Leave it, or change it in GA4 |
| no access | Your Google account can't change it | Ask for Editor access to the property |
Large batches run in parts
A large batch is sent to GA4 as several runs. You still review one list: each run is previewed, the preview shows them together, and they are applied in order. A property's changes stay in the same run whenever they fit.
A flow from one staged batch, split into three runs, each previewed and applied in order.
Apply and read back
Choose Apply to GA4 and confirm. The change takes effect in GA4 immediately, and there is no undo: GA4 keeps no version history for these settings. Each property is checked once more just before writing, only the fields that change are written, and each one is read back. A cell that reads back as expected shows applied; one that doesn't shows applied · not verified, so you know to look.
By default the run stops after the first failure and marks the rest not attempted, so one bad property doesn't cascade. Turn on continue on error before previewing if you'd rather it carried on. When the run finishes, the properties you changed are reloaded so the matrix shows GA4's new values.
A five-step flow from your confirmation to the change being re-checked, written, read back and the matrix reloaded.
Prove it on one property first
For a change that affects reports, such as the attribution model, apply it to one brand, check that brand's reports, then apply the rest. Keep the before values from the preview as your record: see GA4 change control.
Free applies changes to one property per run, so this is how a Free rollout works anyway. Premium applies a batch across many properties at once.
A four-step rollout: preview everything, apply to one brand, check its reports, apply the rest.
Questions about bulk changes
Can I undo a change?
Not automatically. GA4 keeps no history of these settings. Note the before value from the preview, and change it back the same way if you need to. Data deleted by shortened retention can't be recovered.
Why was a change blocked as changed since loaded?
GA4 holds a value that is neither the one you loaded nor the one you staged, so someone changed it in the meantime. Reload, review, and stage again.
Can a settings change run on a schedule?
No. Every change needs you at the screen to preview and confirm. Schedules can only read: see Schedule a drift report.
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.