we've set "Product ID" as evar7 to capture the product info.
The product id looks like: LAPTOP002001, PC200345, the URL looks like: https://example.com/product/laptop002001
Recently, an tech implementation made the URL structure changes: https://example.com/product/laptop002001-dell-xps-13
as a result, server call fires: LAPTOP002001-DELL-XPS-13 to evar7.
Then, in Adobe, we will see 2 values, they are actually same page, same product
evar 7 | product views |
LAPTOP002003 | 1800 |
LAPTOP002003-DELL-XPS-13 | 150 |
Is there a way in Adobe Analytics process the evar and to classify to same product ID? Or it can only accept what is fired from data layer?
evar 7 | product views |
LAPTOP002003 | 1950 |
Thank you.
Solved! Go to Solution.
Views
Replies
Total Likes
If I'm reading your question right, it sounds like you are pulling the product information from the URL (or, your data layer pulls it from the URL and that's what gets passed to Adobe). There are a couple of ways to resolve this without getting your dev team immediately involved, but the "right" approach depends on whether or not you have a tag manager (ie// Launch) in place and have the ability to make changes there.
Option 1, assuming you have access to Launch
Modify the value being passed to eVar7. This could be as simple as creating a data element where you split the value on the dashes and return the first portion. Then use that data element to populate eVar7.
For example, assume your data layer property is named "productName" and is assigned the value "laptop002001-dell-xps-13". In that scenario, the following logic would return "laptop002001", which is what I think you're looking for: productName.split("-")[0];
Option 2
If you don't have access to Launch, and you need to account for both existing data and new data, I'd suggest setting up a classification report based on eVar7. Here you can either create classification rules that use regex to do a similar parsing as above, which would account for any/all new values that come in (and can account for up to 6 months of existing data). Or, you could build a lookup table and upload as a tab-delimited file using the standard classification upload.
For historical data, the processing rules won't do much. You may take advantage of an upcoming feature in Data Repair APIs which will allow updating values in variables. It will be released later this year.
For ongoing data, processing rules cannot split values. Current functionality only allows concatenation. However, you may set static values for specific URLs. Not sure if that will help you much. You can also get a VISTA rule created for this.
Views
Replies
Total Likes
From what I have see it processes what in datalayer.
From the above looks like you are using the page url to set the value in the datalayer.
In implementations I have seen there would be an attribute you allow a user to set to overwrite the url reference (so if product id analytics attribute empty use url - if populated then use populated value).
This will allow you to keep historical data if url changes do occur.
A second consideration would be making use of segment builder in Workspace to build a segment that looks like:
PageID = LAPTOP002001
OR
PagID = LAPTOP002001-DELL-XPS-13
This segment can then be used for reporting as it will return the de-duplicated values for metrics in Workspace.
Views
Replies
Total Likes
@CurtisYoung1987, If it can only be resolved in implementation stage, we have to contact IT again for litter longer processing time, and historical data will not be recovered.
On the other hand, more importantly, the purpose is to evaluate the distinct product ID and rest of metrics/analysis for SEO. As a result, the recommended way - creating segment, would not applicable for batch process for over 10K product ID (adding duplicate will be over 20K).
thanks for your reply, if there is any other recommendation, please share.
Have a safe day.
Views
Replies
Total Likes
If I'm reading your question right, it sounds like you are pulling the product information from the URL (or, your data layer pulls it from the URL and that's what gets passed to Adobe). There are a couple of ways to resolve this without getting your dev team immediately involved, but the "right" approach depends on whether or not you have a tag manager (ie// Launch) in place and have the ability to make changes there.
Option 1, assuming you have access to Launch
Modify the value being passed to eVar7. This could be as simple as creating a data element where you split the value on the dashes and return the first portion. Then use that data element to populate eVar7.
For example, assume your data layer property is named "productName" and is assigned the value "laptop002001-dell-xps-13". In that scenario, the following logic would return "laptop002001", which is what I think you're looking for: productName.split("-")[0];
Option 2
If you don't have access to Launch, and you need to account for both existing data and new data, I'd suggest setting up a classification report based on eVar7. Here you can either create classification rules that use regex to do a similar parsing as above, which would account for any/all new values that come in (and can account for up to 6 months of existing data). Or, you could build a lookup table and upload as a tab-delimited file using the standard classification upload.
Hi @Brian_Johnson_, you are exactly answered my questions. Appreciate that.
However, do you mind let me know where I can find the steps to do option 2?
Sorry I have little idea about how to setup classification report.
What I am looking for is, to change the value collected in eVar7 and make it can be freely breakdown in any of workspace project.
e.g. the server call is still firing laptop002001-dell-xps-13, but where I can find the step/user guide to guide me setting something then evar7 will only collect laptop002001.
About option1, I will try to contact our Adobe Admin.
Thank you for your inputs!
Views
Replies
Total Likes
@H_L- Start with the classifications overview at the link below to get up to speed with the whole concept. You'll find links to both the Classification Rule Builder and Classification Importer options in the left nav if you need more information. If you get stuck, post back here and I'm sure someone can lend a hand.
Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Like
Replies
Views
Like
Replies
Views
Likes
Replies