Predicted LTV bucket dimension
The predicted LTV bucket dimension groups users by GA4's modelled estimate of their future revenue, banding a continuous prediction into segments for audience building. GA4 generates predictive metrics like predicted revenue only when the property meets minimum data thresholds and has the required purchase events. These are model outputs, not observed facts, so they carry uncertainty and should never be reported as actual lifetime value.
What this means
A predicted-LTV bucket bands GA4's predicted-revenue metric — a machine-learning estimate of a user's likely future spend — into segments such as high, medium, and low. The bands let you target predictive audiences without exposing raw scores.
The underlying prediction is generated by GA4's models from each user's recent behaviour, and is recomputed as new data arrives.
Requirements and caveats
GA4 produces predictive metrics only when the property has enough qualifying users and the right events (for revenue predictions, purchase events). Below those thresholds the metric is unavailable. Because the output is a model estimate, it has error and can drift; report it as 'predicted', never as actual LTV, and avoid decisions that would be unfair if the estimate is wrong. This page is educational, not legal advice.
- Bands a modelled predicted-revenue metric
- Requires minimum data and qualifying events
- An estimate with uncertainty, not observed revenue
How it appears in analytics and logs
A bucket reflects the model's confidence that a user will generate revenue in a future window. It is a prediction with error, not measured spend.
Diagnostic use case
Use predicted-LTV buckets to build predictive audiences — for example, likely high-value users — for activation, while treating the values as estimates.
What WebmasterID can help detect
WebmasterID treats modelled value as a clearly-labelled estimate, helping you separate predicted from observed revenue rather than blending them in reporting.
Common mistakes
- Reporting predicted LTV as actual lifetime value.
- Expecting predictions below the data thresholds.
- Ignoring model error when acting on buckets.
Privacy and accuracy notes
Predictive buckets are modelled from first-party behavioural signals, not cross-site identity. Modelled outputs about individuals warrant care under your privacy and fairness policies.
Related pages
- Cohort dimension
The cohort dimension groups users by a shared starting point — typically their acquisition date — so you can follow each group's behaviour across subsequent days, weeks, or months. GA4 builds cohorts in the Cohort exploration from a first-touch criterion and a return criterion. It is the backbone of retention analysis, but small cohorts and identity loss can make later-period values unstable, so trends matter more than single cells.
- Audience membership dimension
The audience membership dimension indicates which GA4 audiences a user currently qualifies for. GA4 evaluates audience definitions against user and event data, adding or removing users as conditions are met or expire. Some audiences populate retroactively from up to a limited backfill, others only from creation forward, and membership can lapse — so counts are dynamic, and comparing them as fixed sets misreads the dimension.
- Modeled vs observed data
Modern analytics reports mix two kinds of figures: observed data measured directly, and modeled data — statistical estimates that fill gaps left by declined consent, cookie loss, and unmeasured sessions. Modeled conversions and behavioral modeling are estimates, can change as models update, and should not be treated as exact counts. This page distinguishes the two and explains how to interpret blended numbers.
- Privacy-first analytics
Modelled value labelled distinctly from observed.
Sources and verification notes
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.