Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Processing data after receiving from data layer

Avatar

Avatar
Validate 25
Level 5
H_L
Level 5

Likes

78 likes

Total Posts

249 posts

Correct Reply

8 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Contributor
Shape 1
View profile

Avatar
Validate 25
Level 5
H_L
Level 5

Likes

78 likes

Total Posts

249 posts

Correct Reply

8 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Contributor
Shape 1
View profile
H_L
Level 5

04-02-2021

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 7product views
LAPTOP0020031800
LAPTOP002003-DELL-XPS-13150

 

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 7product views
LAPTOP0020031950

 

Thank you.

View Entire Topic

Avatar

Avatar
Establish
Level 1
CurtisYoung1987
Level 1

Likes

3 likes

Total Posts

10 posts

Correct Reply

0 solutions
Top badges earned
Establish
Contributor
Shape 1
Boost 3
Boost 1
View profile

Avatar
Establish
Level 1
CurtisYoung1987
Level 1

Likes

3 likes

Total Posts

10 posts

Correct Reply

0 solutions
Top badges earned
Establish
Contributor
Shape 1
Boost 3
Boost 1
View profile
CurtisYoung1987
Level 1

04-02-2021

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.