Here are the attached screenshots:
i am sharing 2 screenshots : 1 one from the console log(Data layer) and 1 from the (AA, how it looks )
example is of a variable. : notification which is similar to offers. It is an array
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 missing details that you think you are collecting, but aren't).
Secondly, because these values are being condensed into a single string, this will be harder to separate out to individual values later... You can't even really use classification rules because you could have any number of items being passed... and from a single string like this, you can't even reuse classifications to represent the type, name, id, etc... because only one value can be mapped at a time.. not multiple.
If you really want to replicate this, then you will need your developers to collapse the values to a string just like your final version... making sure that the same order of fields is used, with a pipe delimiter on your fields, and a comma delimiter for each item...
Basically, you will need to tell your devs to create a context variable string that contains "banner|[na]|overview-banner-top|includes unlimited Canada-U.S. calling. Available at....|account,notication|[na]|[na]|Need...." and pass that... then you just map that single context variable into your eVar27.
Or, you might want to consider changing your approach to using a list variable, using a similar structure, but allowing each item to be recorded separately. Lists act like eVars, except that each item in the list is limited to 255 characters, and you can pass as many items as you want.
You can send the information the exact same way into your list:
s.list1 = "banner|[na]|overview-banner-top|includes unlimited Canada-U.S. calling. Available at....|account,notication|[na]|[na]|Need....";
But, the difference is that you will set up "," as your delimiter. This will result in each item coming through on a separate row in your table:
- banner|[na]|overview-banner-top|includes unlimited Canada-U.S. calling. Available at....|account
- notication|[na]|[na]|Need....
You can then create classifications on your list for "type", "name", "id", "message" and "position"
But since each line will be processed individually, you can get all the data from all notifications processed.
So if you look at Classification "Type", you will get:
- banner
- notification
For you mobile app, you will still need your developers to make the entire thing a string that follows the exact pattern.. but instead of passing it to an eVar, you would pass it to a List dimension....
Anyway, the mobile app solution is the same.. you cannot pass an array, or map that array in processing rules... you will need to instruct your developers to build out the entire string, setting all the proper order of values and delimiters.
