Expand my Community achievements bar.

AEP Product variables - need to store both name AND SKU

Avatar

Level 1

Hi everyone,

I noticed something odd in AEP Datastream Data Prep and wanted to check if this is expected.

Issue

When I map xdm.productListItems[*].name → eVar35, the automatic mapping of productListItems[*].SKU → the Analytics products variable stops working.

What I expected

  • SKU should still flow into the products string (default behavior)

  • Name should flow into eVar35 (custom mapping)

What actually happens

  • eVar35 gets the product name

  • SKU disappears from the products variable

Sample payload

{
"event": {
"xdm": {
"eventType": "application.screen_view",
"timestamp": "2025-11-19T10:10:21.684Z",
"productListItems": [
{
"SKU": "200581",
"name": "TEST",
"priceTotal": 249.0,
"quantity": 1
}
]
}
}
}

Questions

  1. Is this expected behavior or a bug?

  2. How can I capture both SKU (products variable) and name (eVar35)? What is the recommended approach?

Thanks for any guidance!

2 Replies

Avatar

Level 2

Hi

I know of a behavior that if xdm.productListItems[].SKU and xdm.productListItems[].name is mapped that it prioritizes SKU over name, so you should see the SKU value in the "product" variable in AA. But in your case, you are mapping to an evar, an not to name and sku. What's your current mapping for the productListItems[*].SKU, is it a 1:1 mapping to productListItems[*].SKU?

Avatar

Community Advisor and Adobe Champion

As @hegi90 correctly mentioned, the xdm.productListItems[].SKU field takes precedence over xdm.productListItems[].name when data is mapped to the Adobe Analytics "products" string via Adobe Experience Platform (AEP) and the Web/Mobile SDK.

If you need both the true SKU and the name, you could pass the product name into a separate merchandising eVar within the productListItems object.

This name can then be used in Adobe Analytics reports that require the name.

Cheers from Switzerland!