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

User-defined, referable constants

Avatar

Avatar
Contributor
Level 4
FrederikWerner
Level 4

Likes

61 likes

Total Posts

18 posts

Correct reply

2 solutions
Top badges earned
Contributor
Bedrock
Give Back
Springboard
Seeker
View profile

Avatar
Contributor
Level 4
FrederikWerner
Level 4

Likes

61 likes

Total Posts

18 posts

Correct reply

2 solutions
Top badges earned
Contributor
Bedrock
Give Back
Springboard
Seeker
View profile
FrederikWerner
Level 4

29-11-2021

Description -

In Analysis Workspace, users may want to define constant values (like a yearly sales goal or revenue-per-order threshold) and use them in multiple places, like multiple projects, segments, or calculated metrics. However, the only current way to achieve this is through calculated metrics, which come with a bunch of disadvantages:

  • They can't be used in segments
  • If they are used in other calculated metrics, they are copied instead of referenced. Therefore, changes to the original metric will not be reflected in other metrics where the original has been used

This makes this approach unmanageable for values that might change in the future, which can be especially true for sales goals.

Why is this feature important to you -

Avoid inconsistency in reporting and extreme maintenance overhead when working with goals or other, widely used metrics.

How would you like the feature to work -

In addition to the already available component types, introduce a "Constant" type of element. We should be able to create, edit, and delete them from within workspace, and also share them with users, groups, or the whole company. The interface for creating and editing them should be very simple and just allow us to input a number and a name. The constants would then show up in a list and be available in workspace and the editors for segments and calculated metrics. Any changes to the constant should then be reflected everywhere it has been used.

Current Behaviour -

😩

2 Comments

Avatar

Avatar
Validate 1
Moderator
jen_lasser
Moderator

Likes

119 likes

Total Posts

319 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

319 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

29-11-2021

@FrederikWerner  thanks for logging this idea! Question for you - is this just a use case for Targets, which we are investigating? Meaning if that functionality were introduced, would it solve your need? If so, I would like to link the two together. Here is the Targets thread that we are pursuing:

https://experienceleaguecommunities.adobe.com/t5/adobe-analytics-ideas/analytics-workspace-target-re...

 

Avatar

Avatar
Contributor
Level 4
FrederikWerner
Level 4

Likes

61 likes

Total Posts

18 posts

Correct reply

2 solutions
Top badges earned
Contributor
Bedrock
Give Back
Springboard
Seeker
View profile

Avatar
Contributor
Level 4
FrederikWerner
Level 4

Likes

61 likes

Total Posts

18 posts

Correct reply

2 solutions
Top badges earned
Contributor
Bedrock
Give Back
Springboard
Seeker
View profile
FrederikWerner
Level 4

29-11-2021

@jen_lasser As long as I could use them in segments and metrics, as well as share and manage them, I don't mind if they are called Targets. I feel like my approach would be a bit more universal (Targets would be a subset of Constants) but I have no preference as to what they would be called 🙂