Fair enough... now that they seem to be working.. I've just never seen rules take that long to take effect before though.... 

Question... what is the retention period of your eVar, and when is it set?   Is it possible that the values were set before your look-back? I saw "1 month lookback" in your screenshot... I have never seen it take longer than 24 hours to see classified data; unless maybe that information was set befo...

Hmmm that is very interesting then.... it should work... I wonder if Adobe has issues with the "not in set"...   I've have a few instances (0s being one), where my test passed, but the actual data did not work....     I wonder if something like this would work better??   ([\w\d]+)[,:]([\w\d]+)[,:]([...

Interesting... the so real values are matching....    In my experience, I will sometimes use "fake values" for initial testing (or real values), but always test with "real values" during the testing phase.   So those look like they should be working... 

Ok,   Based on these samples, yes it works, but are these real values or fabricated values? There may be nuances to real values that aren't being accounted for...   Do you always have 8 items in this format? Is there a chance that only 7 or 6, etc items could be sent?Is the dimension you are using y...

Did you run a test on your ruleset with some real data to see if your rules are properly matching your content?   Unspecified usually means that content didn't match any rules, or its newer content that hasn't yet been processed (Classification rules run every 4-6 hours, after the initial backfill t...

So, because you are already dealing with "product" data, a simple Merchandising eVar using product syntax and the expiry you need (Visit? 1 Week? etc.... how long do items normally sit in your cart prior to the order being made?).   Interesting fact about s.products, is that the value set in a Merch...

It should be noted, that if there are any s.product calls without any of the standard product events, prodView will be assumed and tracked without explicitly being called... or at least that used to happen to me a few years ago when I was using s.products for non-shopping cart uses...  I just leaned...

Unfortunately, that error message doesn't provide a lot of detail. I wish Adobe's error messages were more user friendly.   Your best bet would be to contact and work with Client Care... You can share the user account with them, provide more information about the request, and even run live tests wit...

Don't shoot the messenger on this one...   But my understanding of the 2.0 version of the API, is that for each dimension row that needs a breakdown, you need another call...   So if you were getting 30 days of data:   You would need one call to get the 30 days, then you would need 30 calls (one for...