Qualified Future Conversions: governance for predictive signals inside a multi-signal measurement stack

Short answer: Treat Qualified Future Conversions as predictive signals, not as observed sales or experimental incrementality. Google says QFCs use Gemini-powered signals such as brand searches to connect upper-funnel spend with future sales and are intended to complement attribution, incrementality and MMM. Store QFC outputs with model/date context, keep them separate from directly observed conversions, and use causal evidence before turning a predictive relationship into a budget claim.

Why QFC needs its own evidence class

Google's 2026 measurement materials position Qualified Future Conversions as a way to capture longer purchase journeys and connect current upper-funnel investment with future sales through predictive signals.

That is different from a transaction recorded today.

It is also different from a randomized experiment that estimates incremental impact.

A measurement stack should preserve those distinctions instead of compressing all three into one conversion total.

Define the evidence classes first

Use explicit types such as:

• OBSERVED_CONVERSION;
• PLATFORM_ATTRIBUTED_CONVERSION;
• QUALIFIED_FUTURE_CONVERSION;
• EXPERIMENTAL_INCREMENTAL_CONVERSION;
• MMM_ESTIMATE;
• CRM_QUALIFIED_OUTCOME.

Each class should retain its own definition, source and uncertainty.

Record QFC context

For every QFC reporting period, preserve:

• account;
• campaign/channel scope;
• date range;
• model/report version where exposed;
• predictive signal definition;
• output metric;
• geography;
• currency/value basis;
• date extracted;
• owner.

Do not compare outputs across periods as though the underlying model is guaranteed to be static.

Separate predictor from outcome

Google gives brand searches as an example signal used to connect upper-funnel spend with future sales.

A predictive relationship does not mean every brand search becomes a sale.

Keep fields for:

• predictor/signal;
• predicted future outcome;
• observed later outcome;
• reconciliation date;
• difference/error;
• known campaign or market changes.

This makes forecast accuracy testable over time.

Reconcile with directly observed business data

Periodically compare QFC patterns with:

• CRM opportunities;
• ecommerce purchases;
• finance revenue;
• qualified leads;
• subscription activations;
• delayed offline sales.

The purpose is not to force the datasets to match exactly. It is to understand where predictive signals are directionally useful and where they diverge from realized business outcomes.

Keep attribution separate

Platform attribution answers which interactions receive credit under a defined attribution model.

QFCs add predictive information about longer-term outcomes.

Do not add QFCs to attributed conversions unless the product definition explicitly supports that aggregation and the reporting layer makes the units compatible.

A dashboard should tell the reader whether a number is observed, attributed or predicted.

Keep incrementality separate

Google's current measurement guidance explicitly discusses attribution, incrementality tests and MMM as complementary tools.

Incrementality asks a causal counterfactual question: what happened because of the marketing activity that would not otherwise have happened?

QFCs can inform planning or long-horizon interpretation, but predictive association alone does not answer the counterfactual.

For major budget claims, use experiments or another suitable causal method.

Keep MMM separate but interoperable

Google says QFC signals are expected to integrate with Meridian, its open-source marketing mix model, to improve measurement of longer-term effects.

That integration does not turn a model into ground truth.

For Meridian or another MMM, document:

• inputs;
• time range;
• priors/assumptions;
• QFC signal version;
• calibration evidence;
• model diagnostics;
• sensitivity analysis;
• final decision context.

A model update should trigger versioned comparison rather than silent replacement.

Handle conflicting signals explicitly

Google's September measurement discussion acknowledges that real-time attribution, periodic incrementality tests and MMM can disagree.

When QFC also points in a different direction, use a reconciliation table:

Do not average disagreement away.

Define decision thresholds before looking at outcomes

For material budget decisions, predefine what combination of evidence is enough.

Examples:

• QFC improvement plus stable observed qualified outcomes;
• QFC trend plus positive incrementality evidence;
• QFC signal supported by calibrated MMM;
• conflicting QFC/finance result triggers review rather than scale.

The threshold should reflect risk and spend size.

Monitor prediction error

A predictive signal becomes more useful when the organization measures how well it anticipates later outcomes.

Track:

• predicted direction;
• predicted magnitude where exposed;
• realized direction;
• realized outcome;
• forecast error;
• market/campaign changes;
• model version.

Do not claim accuracy metrics if the platform does not expose enough data to calculate them honestly.

Governance states

Use states such as:

• PREDICTIVE_SIGNAL_OBSERVED;
• BUSINESS_OUTCOME_PENDING;
• RECONCILED_WITH_OUTCOME;
• CONFLICTING_SIGNALS;
• CAUSAL_TEST_REQUIRED;
• MMM_CALIBRATION_REQUIRED;
• MODEL_VERSION_CHANGED;
• UNKNOWN.

The governance rule

Qualified Future Conversions should sit in the measurement stack as predictive evidence with its own time horizon and uncertainty.

Use QFCs to broaden visibility into longer purchase journeys, then reconcile them with observed business outcomes, causal tests and MMM. Predictive signals can improve decisions without being mislabeled as realized or incremental conversions.

Sources reviewed

• https://blog.google/products/ads-commerce/ads-decoded-podcast-measurement-stack/
• https://blog.google/products/marketingplatform/analytics/meridian-google-analytics-360/