Hi @dineshrkumar,
I suppose the final usage of the data will help drive the solution... I have solutions that use the s.products variable, and I have solutions that use Lists.
First, in your samples, I see you have a lot of your data showing numeric values (i.e. 10 or 20)... are these values that you need a dimension (i.e. text value of "10"), or do they need to be actual numeric values, where you need to use custom events?
If these are all good as dimension values, then you can use lists... passing each row as a list item, then using "sub-delimiters" and setting up classifications.
So for instance:
s.list1 = "sub1:10:20:30:40,sub2:10:20:30:40,sub3:10:20:30:40";
Your list would be set to delimit on comma (,) so you would then end up with data in Adobe that looks like:
- sub1:10:20:30:40
- sub2:10:20:30:40
- sub3:10:20:30:40
Next, you would need to configure 5 classifications (Subject, UT1, UT2, UT3 and UT4)
Using Regex, you can then split the content into each of your classifications, something like:
/(.*):(.*):(.*):(.*):(.*)/g
And setting your Subject classification to $1, and your UT1 classification to $2, etc
This also assumes that ALL values are passed on each instance.
Unfortunately, Adobe Analytics doesn't support flat tables, so you would need to do breakdowns to get the correlation between the Subject and each UT classification.
Now, if you need those values to be numeric values, and I assume the values will change per item (they won't all be 10 or 20, etc... that was just a simple copy/paste example; then the only solution is to use s.products and numeric merchandising events, so that each item can maintain it's own counter correlation.
So, in my examples, I use Products for like 20 different things, so I like to use the Product Category to denote the usage. Products notation would look something like:
s.products = "table;sub1;;;event1=10|event2=20|event3=30|event4=40,table;sub2;;;event1=10|event2=20|event3=30|event4=40,table;sub3;;;event1=10|event2=20|event3=30|event4=40";
s.events = "event1,event2,event3,event4";
Events 1-4 need to be configured to be "numeric" instead of counter (even if you only ever passing 1, if you don't make it numeric, then the correlations get mucked up).
You don't need classifications in this scenario... all your "table" category products will have an isolated metric per product, and you can build out a table in Adobe like so:
| |
|
Event 1 |
Event 2 |
Event 3 |
Event 4 |
| Category |
|
30 |
60 |
90 |
120 |
| table |
|
30 |
60 |
90 |
120 |
| |
Products |
30 |
60 |
90 |
120 |
| |
Sub1 |
10 |
20 |
30 |
40 |
| |
Sub2 |
10 |
20 |
30 |
40 |
| |
Sub3 |
10 |
20 |
30 |
40 |