Standardise GA4 property settings across every brand

One settings screen for every property

GA4 keeps its admin settings one property at a time. Checking that every brand uses the same attribution model, the same retention and the same enhanced measurement means opening each property's Admin screens in turn, and the one that quietly differs is easy to miss.

Property Settings Manager reads those settings for many properties at once and lays them out in one matrix. It groups them into six categories:

• Attribution: the reporting attribution model, both lookback windows, and the conversion export scope for linked Google Ads.
• Data retention: event and user data retention, and whether user data resets on new activity.
• Data collection: Google signals, plus user-provided data collection (read-only).
• Data streams: enhanced measurement and data redaction, one row per web data stream.
• Identity & property: reporting identity, time zone, currency, industry and service level (read-only).
• Definitions & links: how many key events, custom dimensions and metrics, custom channel groups, Google Ads links and BigQuery links each property has (read-only).

Load the current settings first

Every change starts from what GA4 holds right now. Pick the properties (filter by property or account name to narrow a long list), tick the categories under Settings to read, and press Load settings. Nothing is changed by loading.

Loading is free for any number of properties, on Free and Premium. Seeing the whole portfolio side by side is the point, so it isn't limited.

Spot the property that differs

For every setting, the matrix works out the most common value across the loaded properties and marks each property that doesn't match it. Settings that are the same everywhere stay quiet; the odd ones out are highlighted.

Switch the view from All loaded properties to Only those that differ from most and the review shrinks to the handful of cells that need a decision. A property that differs isn't automatically wrong. A brand on Google Analytics 360 may keep data longer on purpose. Check with its owner before you make it match.

Compare against your standard with a baseline

“Most common” only tells you what the majority does. When you have an agreed standard, save it as a baseline: load a property that is set up correctly, choose Save from this property… and give it a name such as Our standard GA4 settings. A baseline keeps setting values only.

Pick the baseline in the comparison menu and every loaded property is checked against it instead of against each other. Cells that don't match are marked Differs from the baseline, and the view can be filtered to just those. Free keeps one baseline; Premium can keep up to 50, for example one per region or client type.

Stage the change

Changes are staged first. There are three ways to stage them:

• Set value: tick the properties to target, pick the setting and the new value.
• Match this property: stage changes so the other loaded properties match one reference property, for one category at a time.
• Match the baseline: stage changes so every loaded property matches the selected baseline.

Staged changes collect in a tray, one row per property and setting. Remove any you don't want. Staging writes nothing to GA4. A batch can hold up to 500 changes.

Preview: GA4 is re-read live

Press Preview changes for a dry run. 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.

This is what protects you from acting on stale information. If someone changed a setting in GA4 after you loaded it, that change is marked changed since loaded and is blocked. Reload and review it rather than overwrite their work.

Apply, and know what can't be undone

Choose Apply to GA4 and confirm. The change takes effect in GA4 immediately, and there is no undo: GA4 has no workspace or 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 afterwards. A cell that reads back as expected shows applied; one that doesn't shows applied · not verified, so you know to look.

If a write fails, the run stops there and the remaining changes are marked not attempted, so one bad property doesn't cascade. When it finishes, the properties you changed are reloaded so the matrix shows GA4's new values.

A few settings have consequences beyond the setting itself:

• Shortening data retention deletes data older than the new window. It is only applied after you type SHORTEN.
• Changing the attribution model re-credits conversions in reports, for past and future data.
• The Google Ads conversion export scope can't be switched back to Not selected once set.
• Turning on Google signals needs the Google signals terms accepted in GA4 first.
• 26, 38 or 50 months of retention needs a Google Analytics 360 property.

Settings worth standardising first

If you're building your first baseline, start with the settings that make brand reports comparable and keep data safe:

• Reporting attribution model and both lookback windows, so every brand credits conversions the same way.
• Event data retention. GA4 sets new properties to 2 months; 14 months is the longest on a standard property.
• Google signals, so cross-device reporting is the same choice everywhere.
• Enhanced measurement, especially form interactions, which is off by default.
• Redact email addresses and query parameters on every web stream, so personal data doesn't reach reports.

What it shows but doesn't change

Some columns are read-only on purpose. Reporting identity has no GA4 API to change it. Time zone and currency re-bucket future data, so they are shown but left to GA4. The counts of key events, custom definitions and channel groups are a summary; change those in the module that owns them: Events Manager, Dimensions Control Center or Channel Groups Vault.

Settings GA4 has no API for at all, such as data filters, consent settings, comparisons and segments, aren't offered. Change those in GA4.

A scheduled settings drift report

Settings drift. Someone switches a model in one property, a new brand is created with GA4's defaults. On Premium, an Automation can re-read the settings on a schedule and report the properties that differ from most, or from your baseline. A schedule only reads: changes always need you at the screen to preview and confirm. See Schedule GA4 checks.

Free and Premium

On Free you can load and compare any number of properties, apply changes to one property per run, and keep one baseline. Premium applies a batch across many properties at once, keeps up to 50 baselines, exports and emails the matrix, and schedules drift reports. Compare the plans.

Keep going

• Next: event rules and key events
• GA4 change control
• The complete GA4 Ultimate Stack guide