GA4 attribution settings
GA4's attribution settings (Admin > Attribution settings) define the property-wide reporting attribution model and the lookback windows for acquisition and other conversions. Changing them re-attributes credit across the property's reports going forward and, for the model, retroactively in attribution reports. Understanding these settings is prerequisite to reading any GA4 attribution number correctly.
What you configure
Two things live here. First, the reporting attribution model — data-driven or a rules-based option — which determines how credit is distributed in attribution reports. Second, the lookback windows: how far back before a conversion GA4 will consider touchpoints, with separate settings for acquisition conversions and other conversions.
These choices apply property-wide, so one change moves every attribution report.
How changes propagate
Per Google's documentation, changing the reporting model can apply to both historical and future data in attribution reports, while lookback-window changes affect data going forward. That asymmetry is a common source of confusion when numbers shift after a settings edit.
Document every change with a date, because a model or window switch can explain a step-change in channel credit that has nothing to do with campaigns.
- Reporting model: data-driven or a rules-based option
- Lookback windows: acquisition vs other conversions
- Record change dates — they explain credit step-changes
How it appears in analytics and logs
If GA4 channel credit looks unexpectedly concentrated or short-pathed, the configured model or a short lookback window — not real behavior — may be the cause.
Diagnostic use case
Confirm which model and lookback windows your property uses before comparing GA4 conversion credit to ad-platform or CRM numbers.
What WebmasterID can help detect
WebmasterID's observed conversions do not depend on a configurable model, so they help you tell a settings change apart from a real shift in behavior.
Common mistakes
- Comparing GA4 to ad platforms without checking the model.
- Forgetting that lookback changes apply going forward.
- Failing to log when settings were changed.
Privacy and accuracy notes
Settings govern how aggregated credit is assigned; they store no extra personal data. Educational, not legal advice on configuration.
Related pages
- Attribution in GA4
Google Analytics 4 (GA4) implements attribution with a data-driven model as the default for its conversion reporting, plus rules-based options, configurable lookback windows, and default channel groupings. It also distinguishes attribution used in GA4 reports from the conversions Google Ads counts. This page describes GA4's attribution posture and the settings that change how credit appears.
- Lookback and conversion windows explained
A lookback (or conversion) window is the period before a conversion in which earlier touchpoints are eligible for credit. Touches outside the window are ignored entirely. Because every attribution model only sees touches inside this window, its length quietly governs which channels can ever receive credit.
- GA4 reporting identity
Reporting identity is the GA4 setting that decides how events are joined into individual users for reporting: User-ID, Google signals, device, and modeling, applied in a chosen order (Blended, Observed, or Device-based). Because attribution depends on knowing which touches belong to the same person, the identity space directly affects path lengths, deduplicated user counts, and credit distribution.
- Compare: Google Analytics
How model settings shape GA4 attribution reports.
Sources and verification notes
- Google Analytics Help — Attribution and attribution settingsDocuments reporting model and lookback window settings.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.