Like Josh, I was going to ask what the expiry of ALL your eVars are... just because the segments are set to Hit, doesn't mean the data populating the values is limited to those pages.. it might persist and your segment is returning stuff that isn't in your expected context.

Products is similar to lists... each value passed has a limit, but not the entire string...   So: the Category portion has a character limit is 100 (the same as other props, as this functions the same as a prop.. no retention, no expiry)The Product Name has a character limit of 100 (also similar to ...

You're very welcome.. and yes, thankfully the mapping does not change on every pull... that would be a nightmare!   I believe the lookup table is provided each time, just in case something changes, you will have it (or you will get it on the first data pull)... for instance, let's pretend that Adobe...

Hi Nitish,   I assume you are using AppMeasurement and not WebSDK?   While I haven't implemented this myself (only using some demo code), to deal with the ECID you will have to use the Opt-In settings inside the Experience Cloud ID Service...   Depending on your needs, I believe you need to choose a...

Hi @luliu84,   The lookup file is standard, so the instance of eVar1 will always be "100", and event1 will always be "200"   Based on what you shared above, can I say 166 instance of eVar67? I'm not sure if you mean that "Instance of eVar67", or that you can map "166" to "Instance of eVar67" If the ...

@MandyGeorge is correct, the "new" rule builder for classification sets is not yet built/released... so classifications requiring regex rules must still be done in the legacy system.   Depending on how many rules you have to migrate, When you start the process will have to take effort into account, ...

Glad I was able to help on two fronts. Also, I realized I was using a virtual suite that had a HIT based segment... when I look at the main suite, I don't have the issue...    It's likely the segment causing some inconsistencies.

Lol, I was just about to start posting comments. Glad you figured it out...    Yes, engagement events that can trigger multiple times can definitely cause some headaches.   The other thing you might want to consider is engagement weights... Like a scroll event is worth 1, hitting "Read More" to load...