How to Create a Classification of a Set of SKUs | Adobe Higher Education
Skip to main content
C
CarlyleBr
January 29, 2025
Resuelto

How to Create a Classification of a Set of SKUs

  • January 29, 2025
  • 1 respuesta
  • 577 visualizaciones

Hi all,

 

I have about 6500 products (unique SKUs) that I need to report on as a set. We did some work on these SKUs and need to be able to isolate performance reporting to just those SKUs, not the product category as a whole. It was recommended to me to make a classification with just those SKUs in it within our product SKU evar; I followed Adobe's instructions on how to make a classification. It shows up as a new dimension in the Adobe workspace, but it is not isolated to just my set of SKUs that I uploaded using the classification uploader. How do I fix this? The "top items" summary says "unspecified" and when I try to filter by the product SKU evar, it shows SKUs that are not in the list of 6500. 

Este tema ha sido cerrado para respuestas.
Mejor respuesta de Jennifer_Dungan

Any item not mapped by classifications will show as "unspecified", this is to be expected. When you are pulling that report you should use the settings to not include unspecified.

 

(Deselect this in the filter options)

 

 

Also, when you say "filter by the product SKU evar" I assume you mean that this is part of the Products Lists (s.products) or its Merchandising eVars, and I assume you are using a segment?

 

So, there's a caveat to working with Products... while each product in the list is checked individually (either by equals or contains), ALL products in the same hit will be returned.

 

One way around this is to use the Freeform table filters, or to use the breakdown logic..

 

For example, let's say I have the following SKUs and I use classifications to map them:

 

12345                special

12346                special

123876              (unclassified)

124547              (unclassified)

23646                special

 

 

I can create a table like:

        Metric
Classification       100
  special     68
    SKU   68
      12345 36
      12346 28
      23646 17

 

 

If you pull in your "special" classification, then breakdown your SKUs under that, only the classified values will show up. You cannot create a segment that pull this data back... it will always include other SKUs, or it will not include the SKUs if they have a non-included SKU (if you use an exclusion rule to avoid the non-matching values)

1 respuesta

Jennifer_Dungan
Community Advisor and Adobe Champion
Jennifer_DunganCommunity Advisor and Adobe ChampionRespuesta
Community Advisor and Adobe Champion
January 30, 2025

Any item not mapped by classifications will show as "unspecified", this is to be expected. When you are pulling that report you should use the settings to not include unspecified.

 

(Deselect this in the filter options)

 

 

Also, when you say "filter by the product SKU evar" I assume you mean that this is part of the Products Lists (s.products) or its Merchandising eVars, and I assume you are using a segment?

 

So, there's a caveat to working with Products... while each product in the list is checked individually (either by equals or contains), ALL products in the same hit will be returned.

 

One way around this is to use the Freeform table filters, or to use the breakdown logic..

 

For example, let's say I have the following SKUs and I use classifications to map them:

 

12345                special

12346                special

123876              (unclassified)

124547              (unclassified)

23646                special

 

 

I can create a table like:

        Metric
Classification       100
  special     68
    SKU   68
      12345 36
      12346 28
      23646 17

 

 

If you pull in your "special" classification, then breakdown your SKUs under that, only the classified values will show up. You cannot create a segment that pull this data back... it will always include other SKUs, or it will not include the SKUs if they have a non-included SKU (if you use an exclusion rule to avoid the non-matching values)

    Términos y condicionesAccessibility statement

    Loading footer...