Hello Guys,
We are planning to implement a tracking which can help us to see our navigation relevancy based on some metric such as product view, cart addition etc. In the end we need data in the following format which will be used to compute relevancy score using various method e.g. Discounted Cumulative Gain etc.
Date | Navigation Category | Source Page Name | Landing Page Name | Landing Page Page Number | Clicked Position on Catalog | Product Views | Cart addition | Checkout | Orders |
---|---|---|---|---|---|---|---|---|---|
04/09/2018 | Rings : Ruby | Home page | browse : rings | 1 | 4 | 100 | 90 | 80 | 70 |
04/09/2018 | Pendants : Diamond | browse : earrings | browse : diamond pendants | 2 | 1 | 200 | 180 | 160 | 140 |
- | - | - | - | - | - | - | - | - | - |
- | - | - | - | - | - | - | - | - | - |
04/09/2018 | Earrings : Sapphire | Home Page | browse : earrings | 1 | 5 | 50 | 40 | 30 | 20 |
I understand that eVar will be needed to capture such data and its allocation should be most recent.
The major challenge for me to define the scenario when eVar should capture the details. These are the following scenario I thought which have some drawback with it,
Please let me know your input to the problem.
You can visit our site : www.angara.com?cid=onr-adobe-forum and understand how navigation work on it.
Thanks & Regards,
Hanish
Solved! Go to Solution.
Views
Replies
Total Likes
You'll want 5 eVars: one for each navigation dimension you want to track.
You can define the eVars whenever you need; landing page ones on the first page load, and navigation click ones on click. Since eVars persist server-side, you wouldn't need to do anything else to tie them to conversion metrics - just make sure their expiration in the admin console are correctly set (they default to visit).
Keep in mind that this would require an extra link tracking call in addition to the page load call that loads on each page, so be careful you don't exceed the number of server calls in your contract if you opt to do this.
Views
Replies
Total Likes
You'll want 5 eVars: one for each navigation dimension you want to track.
You can define the eVars whenever you need; landing page ones on the first page load, and navigation click ones on click. Since eVars persist server-side, you wouldn't need to do anything else to tie them to conversion metrics - just make sure their expiration in the admin console are correctly set (they default to visit).
Keep in mind that this would require an extra link tracking call in addition to the page load call that loads on each page, so be careful you don't exceed the number of server calls in your contract if you opt to do this.
Views
Replies
Total Likes