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
Bedrock Mission!

Learn more

View all

Sign in to view all badges

Classification with the same name/settings but incompatible

Avatar

Avatar
Springboard
Level 9
JarnoRossiCom
Level 9

Likes

406 likes

Total Posts

51 posts

Correct reply

0 solutions
Top badges earned
Springboard
Establish
Contributor
Shape 25
Shape 10
View profile

Avatar
Springboard
Level 9
JarnoRossiCom
Level 9

Likes

406 likes

Total Posts

51 posts

Correct reply

0 solutions
Top badges earned
Springboard
Establish
Contributor
Shape 25
Shape 10
View profile
JarnoRossiCom
Level 9

26-04-2017

I raise here again an old but frustraiting problem with classification in Adobe.

If we create the same classification in 2 different reports suite, in 2 different moment, could happen that they look the same, but in Adobe code they are not the same, because they belong to different version of "something" that stands behind Adobe Analytics.

That's huge impact on everything, because we have to create a different upload process for each code version, and both segments and calculateds which use that classification, dont work cross all report-suites, even we use the "same" classification.

The only solution we have is to delete all the classifications and create them again. An incredible work to do, with all reports that need to be updated.

Please Adobe, can you fix this architecture bug?

1 Comment

Avatar

Avatar
Validate 1
Moderator
jen_lasser
Moderator

Likes

119 likes

Total Posts

317 posts

Correct reply

8 solutions
Top badges earned
Validate 1
Give Back 25
Ignite 3
Ignite 1
Give Back 5
View profile

Avatar
Validate 1
Moderator
jen_lasser
Moderator

Likes

119 likes

Total Posts

317 posts

Correct reply

8 solutions
Top badges earned
Validate 1
Give Back 25
Ignite 3
Ignite 1
Give Back 5
View profile
jen_lasser
Moderator

27-04-2017

Thanks for the feedback, Jorno. We have a project underway to improve both the classification user experience and backend architecture, to address this exact issue. The future state we are shooting for is to have consistent backend classification IDs so that as you switch between suites, segments and calculated metrics, the classification remains valid. We are aiming to release a part of this project very soon, so stay tuned!