Adobe Analytics classification migration: test the rules before replacing them

The migration control says complete, but an important campaign code now shows “Unknown” or the new rule canvas is blank. An Experience League thread reports trouble with regex rules that write custom text values. That report does not prove every migration is faulty; it does show why a successful UI action is a weak acceptance test for reporting data.

Inventory rules and consumers

List each classification set, key dimension, subscribed report suites, rule order, regex pattern, custom output and downstream dashboard. Identify values with whitespace, alternate delimiters, empty fields and unexpected case. Preserve representative raw keys and expected labels before touching the legacy configuration.

Adobe's current classification-set rules guide offers three paths: migrate existing rules, start fresh or continue in the legacy interface. It also says rules in a set apply to every subscribed report-suite and key-dimension combination. A shared set therefore has a wider blast radius than a single suite's old rule set.

Compare outputs, not screenshots

Build an acceptance sample of common, rare and malformed keys. Run the old and candidate new rules against the same inputs, then compare classification output and downstream segment membership. Include the labels that finance or marketing leaders actually use. If a rule does not migrate, rebuild it from its documented behavior, test it, and only then switch the reporting consumer. Keep a rollback reference for the old rule configuration.

Treat “Unknown” as a diagnosis

An unknown label can mean an unmatched key, rule precedence, delayed processing or a broken mapping. Compare the raw key with the rule test result and the report-suite subscription before declaring an Adobe defect. If the UI and output still disagree, collect the set ID, key examples and test result for Adobe support; avoid changing rules repeatedly without a controlled comparison.

Adovo’s view

A classification is part of the reporting contract, not a cosmetic label. Migration is complete when a representative key still means the same thing in the decisions it feeds. A green migration message is merely a starting signal for that proof.