Analytics & Attribution

Yesterday’s Click Conversions Were UNKNOWN. Today the Enum Can Name Them.

Data engineer auditing click-event classification beside an editorial headline about reclassifying attribution events.

Updated: November 6, 2026

Add CLICK as an explicit attribution-event category, preserve historical UNKNOWN values, and version the semantic change in every warehouse model and dashboard. Do not backfill old UNKNOWN rows as clicks unless independent evidence proves the attribution path.

A clearer enum can create a misleading time series

Google Ads API v26 adds CLICK to ConversionAttributionEventType for conversions attributed to an ad click; those cases were previously included in UNKNOWN. That improves future classification, but it creates a semantic break. The same business behavior may appear under different labels before and after the upgrade.

If a dashboard shows UNKNOWN falling and CLICK appearing, the audience may infer a channel-quality change. The first explanation should be the taxonomy migration.

Inventory every consumer of the field

Search ingestion schemas, transformation code, semantic models, exports, alerts and downstream notebooks. Identify logic that accepts only known enum values or treats UNKNOWN as missing. Add CLICK without changing the treatment of existing rows.

Capture API version, extraction date and raw enum in the warehouse. A normalized field can support reporting, but the raw value is essential for audit and future migrations.

Operating control table

Control Evidence Failure prevented
Raw enum Unmodified source value Irreversible history rewrite
API version Value stored per extract Hidden semantic break
Dimension mapping CLICK accepted with fallback Dropped conversions
Reconciliation Totals by action and date False performance shift
Annotation Dashboard migration note Stakeholder misinterpretation

Choose a historical policy explicitly

The conservative policy is to leave historical UNKNOWN unchanged and mark the date CLICK became available in the pipeline. A derived reporting group may combine prior UNKNOWN with later CLICK only when the limitation is visible.

Do not overwrite historical raw data. If independent click identifiers allow a defensible reclassification, write a separate derived column with method, confidence and run date.

Test joins and null handling

A new enum can break strict validation, switch statements and dimension tables. Test unknown-value fallbacks, slowly changing dimensions, incremental loads and BI filters. Verify that conversions remain counted when the label is new.

Compare totals by conversion action before and after deployment. The grand total should reconcile even while category distribution changes. Investigate differences before shipping the semantic model.

Explain the break in stakeholder language

Publish an annotation on the first affected report: ‘CLICK became an explicit attribution event type in Google Ads API v26; earlier click-attributed events may be included in UNKNOWN.’ Include the pipeline deployment timestamp, not only Google’s release date.

Train analysts not to compare raw category shares across the break without adjustment. Clear release notes are part of attribution accuracy.

Put the control into the wider system

Connect this work with metric-state and suppression reporting guide. The objective is continuity: the platform setting, creative promise, measurement rule and downstream experience should describe the same operating decision.

Pre-launch checklist

  1. Write the decision and its owner in plain language.
  2. Capture the platform configuration before the change.
  3. Test one realistic customer or reporting path end to end.
  4. Verify mobile presentation and accessibility.
  5. Record the success threshold and rollback trigger.
  6. Schedule the first review before material spend or traffic accumulates.

Run a cross-functional release review

Ask the channel owner, creative lead, analyst and conversion owner to inspect the same end-to-end case. Each reviewer should be able to state what was configured, what the customer sees, which event proves the outcome and which limitation changes the interpretation. Resolve differences in the campaign brief and measurement plan before launch; otherwise a small naming disagreement can become reporting debt or a customer-facing contradiction.

Repeat the case on mobile and with one adverse condition, such as an ineligible budget, a suppressed metric, a missing disclosure, an exhausted audience or an unavailable fulfillment method. The control is useful only when it explains the exception as clearly as the happy path.

Set the review cadence before launch

Assign an owner, review frequency and threshold that triggers action. The first review should happen soon enough to catch configuration or experience defects before they accumulate meaningful spend, customer confusion or reporting debt. Later reviews can move to a normal operating cadence once the control has produced stable evidence.

Keep the decision record usable: observation, supporting evidence, owner, action, expected result and next review date. Preserve the pre-change baseline and avoid silently editing the definition after results arrive. This turns the launch into a measurable operating decision instead of a one-time interpretation of platform guidance.

Frequently asked questions

Should this be automated?

Automate repeatable validation and monitoring, but keep material policy, claim and budget decisions inside named approval limits.

What is the minimum evidence?

Preserve the source configuration, decision owner, expected outcome, observed result and any exception that changes interpretation.

When should the team roll back?

Rollback when the control is inactive, the customer experience breaks, totals do not reconcile or the agreed performance threshold is breached.

Sources

Published by Marketing That Clicks
Last reviewed November 6, 2026.