I have something similar in our apps, this is how I would instruct / create the requirements for our developers:   --------------------------------- For the array of notification data, please create a string of all the data in the following order:   {type}|{name}|{id}|{message}|{position}   Delimit ...

Ah, ok, so your final eVar is just a big string that looks like:   banner|[na]|overview-banner-top|includes unlimited Canada-U.S. calling. Available at....|account,notication|[na]|[na]|Need....   First off, you should know that this value is being truncated at 255 characters (so you are probably mis...

I am asking because in many cases, while you can collect the same information as web, in many cases you have to approach it differently....    You do not have as much control over data in Processing Rules, there are somethings (i.e. Products List) that cannot be mapped with Processing Rules, etc.   ...

How is the information being collected on Web? Your data layer might be an array, but it's not "going to Adobe" as an Array, since AA only supports text.   I assume you are using Launch to process that array into an eVar or List, or some dimension... can you share the final output?

OK, so we probably have a very similar setup.   So what are you trying to do? Are you trying to populate your s.products variable? Or maybe set up List Vars? Those are the two most likely uses I can think of... but again, I understand your needs.

Adobe Analytics won't support arrays, all dimensions are simple text.. since you mentioned processing rules, I am assuming you are not trying to do this in CJA...   However, are you using the old ACP SDK, or are you using the newer AEP SDK and XDM Streams? Or maybe you have upgrade to XDM, but are j...

Or possibly check on the Microsoft forums, since this seems to be problem with SQL Server?

Or rather those applications are only triggering page views and no actions. Therefore, page views (X) and actions (0), result in Occurrences (Page Views + Actions) = X + 0 = X.   Or your applications are also treating actions as page views (resulting in a complete match of the events).

Yep, lot's of options... personally, I try to keep rules minimized where possible... even if it means the rules are a little more complex.... for me that reduces a lot of my rule management efforts.   But even with my solution above, that Data Element can be added to "propX" or "eVarY", etc in the s...

Yep, I was just about to say that you need a condition on the original rule so that only one of the rules will trigger.. and that the "path" only looks at the path and not the full URL.     However, if I had this need, I would actually do my implementation differently....   An alternate option is to...