Classification values suddenly reported as "Unspecified" although source values are still available | Adobe Experience League Community
Skip to main content
Level 1
August 24, 2026
Question

Classification values suddenly reported as "Unspecified" although source values are still available

  • August 24, 2026
  • 1 reply
  • 17 views

Hello,

We have identified an issue impacting one of our Adobe Analytics classifications.

Since mid august, some values that are correctly collected and available in the source dimension (Component Inventory) are no longer being mapped to their expected classification values. Instead, they are being reported as "Unspecified".

What we have already verified:

  • The source values are still being collected correctly.
  • The classification configuration has not been modified.
  • The classification rules still appear to match the incoming values.
  • Only a portion of the hits associated with this code are being classified correctly, while another portion is being reported as "Unspecified" despite sharing the same source value.

Could you help us understand:

  • Why values present in the source dimension would stop being classified despite the rules remaining unchanged?
  • Whether any remediation or reprocessing action is available?

Thank you for your support.

    1 reply

    Jennifer_Dungan
    Adobe Champion and Community Advisor
    Adobe Champion and Community Advisor
    August 24, 2026

    Hi, how are your classifications being set?

    • Regex Rules?
    • Other “built” classification logic?
    • Imported Mappings?


    Since Classification Sets are relatively new, and a lot of people are in the process of migrating their rules from the older Classifications, people are reporting bugs to Adobe about things that aren’t quite working… it’s entirely possible that in fixing a reported bug, your rules have inadvertently been broken.

    Sharing details about your rules, so that we can try to replicate, or share our own learnings would be helpful… Ultimately, this may end up being a bug to client care, but at least having other people confirm the same issue helps give weight to your bug, but we also might be able to suggest work arounds.