Expand my Community achievements bar.

Join us for the next Community Q&A Coffee Break on Tuesday April 23, 2024 with Eric Matisoff, Principal Evangelist, Analytics & Data Science, who will join us to discuss all the big news and announcements from Summit 2024!
SOLVED

Product Name is getting trimmed

Avatar

Level 4

Hi Team,

 

I have implemented s.product string in retail project, but product name is getting trimmed because of that multiple product ID is coming under single product. Please find the reference image below:

bindukumari1990_0-1630675552456.png

 

bindukumari1990_1-1630675578753.png

 

Any help will be appreciated, as I am new to tool.

 

 

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor
4 Replies

Avatar

Level 8

@bindukumari1990 - The issue isn't that there are multiple product names. The issue is that the values you're passing in the "Product Name" position for each product exceeds the maximum character (byte) count, which is 100 characters (bytes). Anything after the 100th character is simply dropped during processing and is not recoverable. For full details about capabilities, schemas, character limits, etc related to the product string, check the documentation.

 

Here are a couple of options to deal with the issue:

  • Instead of passing the full product name/description (eg// "IntelliFresh 292 L Frost Free...") in s.products, consider passing just the unique product SKU (eg// "12345"). To get the added detail that's lost with this approach, consider one of the following:
    • In the Analytics interface, use Classifications to provide the added detail.
    • Pass the added detail in an eVar as part of the same product string entry. The eVar will support strings of up to 255 characters/bytes. 
  • Move the uniqueness to the front of the "Product Name" value. This ensures that you'll always be able to differentiate between similar products. The downfall is that you will continue to lose any detail beyond the 100th character for each product.
  • Add the unique product SKU (eg// "12345") to the beginning of the "Product Name" value. This ensures that you'll always be able to differentiate between similar products. The downfall is that you will continue to lose any detail beyond the 100th character for each product.

There are likely other alternatives, but each of the above options will help preserve the uniqueness you're after. 

 

Finally, whichever approach you adopt, be sure to adopt it throughout your entire implementation. Any time you're tracking product interactions (prodView, scAdd, scRemove, purchase, custom events, etc), make sure you're using the same "Product Name" value. Otherwise, you'll find yourself with a different problem.

Avatar

Community Advisor

Evo great response and totally agree SIANT classification is key here.

 

Bindu one thing not method is this method also will allow you to is make retroactive corrections to the classified elements.(original key SKU it wont) but the other SAINT elements you eventually can.

 

good luck

Avatar

Level 4

Please let me know, how can I proceed with SIANT classification. Any material or video on the same will help. As I have not done SIANT classification before.

 

 

Avatar

Correct answer by
Employee Advisor