I think traceability of the use of shared components is really
important. What I would find really useful is a method to identify all
the workspace projects a share segment is being used in. (so that i can
verify that any changes to the shared segment won't accidently break any
of those workspace projects)
Hi Brian, thanks for the response and some interesting questions! "Would
it be reasonable for all the assets that reference that dimension to
start displaying the new data rather than the old?" I would be
absolutely OK with all the assets that reference that dimension
displaying the new data rather than the old - in fact this is the
behaviour I would have expected. (I believe this is how an eVar
attribution change works today) "What if the new data doesn't make any
sense in the context of the as...
The capability to capture a delimited list of values and have the tool
parse them out is a incredibility useful feature. The problem in Adobe
Analytics is that: 1) List props are virtually useless due to the
character limit.2) there are far to few list vars I really hope that
this gets looked at as it would take a lot of pressure off our 3 very
precious list vars. Although give this was logged back in 2013 I don't
hold out too much hope 😞 ...alternatively just give us a 100 list vars
and we'll ...
IssueDeleting data is incredibly problematic (and expensive!) in Adobe
analytics. One of the impacts is on our agility - we have several
dimensions that are tied up as they contain historic data that is no
longer relevant and we are waiting for that data to disappear through
the standard data retention deletion process before we reuse - This is
something we really struggle with. RequirementsThe requirement is to be
able to quickly re-purpose variables/dimensions, thus increasing the
flexibility/...
We are trying to use workspace to create a safe environment for our end
users to access analytics data. In order to do this we are centrally
managing a lot of "approved" segments, calculated metrics, and
workspaces. In order to keep on top of this we are having to undertake a
lot of manual documentation so that when we change things we know we are
not going to break things. Unfortunately this is proving difficult to
keep on top of. The burden could be significantly reduced if we were
able to eas...
For me this also ties into the broader question of navigation and
grouping of projects as per @michael-jet's post...
http://ideas.omniture.com/t5/Idea-Exchange-for-Adobe/Analysis-Workspace-Folders/idc-p/1601
7
Navigation of the project list is a problem for us too. It is simply
difficult for end users to find what they are looking for in a long list
of projects. I thought it was interesting that that when you introduced
a mere 14 starter projects you felt the need to group them under 4
categories to aid navigation 😉 It would be great if you could consider
introducing some customisable grouping or hierarchy for the main project
list. A note on 'tags'... I'd imagine 'tags' were seen as the solution
to ...
I logged on to the ideas exchange today to log this specific request!
The new alerting functionality is great but this is one of the biggest
gaps. As you can only set up alerts for a specific item, the problem we
now face is we have to know in advance what the item is that will have
an issue so it can be alerted on (which is obviously impossible) This
means the new alerting functionality's use is limited to high level
aggregate activities which disappointingly makes it significantly less
useful ...
To be quite frank this is less of an idea, more me posing the problem we
face... We are desiging workspace projects to be used by end business
users. We don't have the time/resources to train every individual to use
every workspace project so we are relying more and more on supplying
instructions/help within the project. However, the way in which we can
do this is pretty much limited to putting paragraphs of plain text in a
description box. It would be great if Adobe could consider the best way
...
When a project is curated the minimum number of components shown in a
project is those components used in building the project. However, often
the core building blocks of a project are not the components that we
actually want end users to be playing with/interacting with. In order to
keep the interface as clean and simple for end user, I would like the
option to hide/suppress the core components from the left hand menu For
instance, in the simple example below the only components I want the end
...
We use a number of report suites in our company. Only specific reports
suites are valided against specific workspace projects. Use of an
incorrect reports suite against a project can lead to some strange
results.If we are able to curate the dimensions/components available in
a project then it would also make sense to be able to curate the report
suites available within a project.In the spirit of preventing users from
making errors, please could you consider introducing curation of reports
suites...
Thanks Ben, to be honest the plugin might have got more sophisticated
since I last looked at it. I've never relied on it - Where ever I've
gone I've forked out on a VISTA rule as it just felt the more robust way
to acheive this. I guess even if it is trying to adjust for time zones
it's still relying on the setting being correct on the machine, I just
remember seeing some odd results from this in the past. Agree in
general, as things get aggregated up statistically it's probably not an
issue, bu...
@benjamingaines - The thing we struggle with is within a panel creating
a sense of hierarchy to the content. At the moment everything is of
equal weighting. It would be great if Adobe were to think about the
wider question of "what the best way to create a sense of hierarchy
within a panel containing lots of components?". (font sizes/colors of
titles might be one way to achieve this)
The JavaScript work around for this is pretty horrible because I believe
the value reported is based on the users system clock. Therefore if
their clock is wrong or in a different time zone you get a different
value reported for the same hour.
I totally agree with this. We've paid for a VISTA rule to allow us to
create a dimension that enables us to do this. It definitely feels like
this is funcationality that should come straight out of the box.
For me the 'other' row has to be the sum of the other rows (i.e. no
deduping between the rows not shown), otherwise you are comparing apple
and oranges. In terms of how this might work I was hoping you might find
a way to actually insert an additional row into the freeform table and
therefore any visualization would work off it - and it would be
available in the table as well I can understand why you are thinking
about this in terms of the 'donut' (probably the same reason I picked it
for my exa...
It would be great if when displaying the top "X" number of values for a
dimension it was possible to opt to display an additional row containing
an aggregated sum of all the other rows not displayed. This would be
useful for showing the complete picture. The below is an simple example
of how the "donut" percentages do not reflect the complete picture
because it is only reflect the top 5 values and does not account for the
other rows. (e.g. Internet explorer 65% of traffic according to the
table ...
Thanks Ben, appreciate the quick response I've been pondering this and I
think in some ways it's related to another idea I've recently posted...
Workspace Sort out the trending of percentages Whereas in Ad Hoc the
creation of things is often 'throw away', analysis workspace forces you
to store something before you use it - so you start to build up long
lists of segments/calculated metrics/date ranges. I'm not particularly
adverse to this approach as in some ways there are efficiency gains
(e.g. ...
As of yesterday's release, we can use rolling date ranges in segments -
hurray! However... we can only indirectly use rolling date ranges in
calculated metrics (via segments). So in order to create some really
useful calculated metrics, we have to create (and manage) segments that
duplicate the all the date ranges want to use - which seems like a waste
of time and clutters the interface e.g. we now have a date range of
'last month', and a duplicate segment of 'last month' for the sole
purpose of...
Please can you make anomaly detection take account of daylight savings
changes as per the report suite settings? Here in the UK the clocks have
recently gone back 1 hour and the anomaly detection on all our hourly
reports are now messed up (e.g. anomaly detection is displaying an
expected value for 9am against the actual value for 8am) This makes it
pretty useless at the moment - also if we'd set up a lot of hourly
alerts (as we'd been planning) I think this could have casued some chaos
Thanks, in my haste to reply I forgot a pontential 2nd reason why the %
row approach doesn't necessarily work which is to do with dynamic vs
static values. Take the scenario where the requirement is to trend the
percentages for the 'top 5' browsers for the last 90 days. The 'row %'
approach requires you to hard code the 5 items that are to be tracked as
column headers (i.e. they won't dynamically update if the 'top 5'
changes) so it can't be done. However, the dimension placed down the
left hand...
Thanks for coming back and asking me to clarify - really appreciate the
fact that you are not making assumptions. It's not a duplicate. I will
try to explain... The reason the other idea does not solve this is
because of the denominator used in the calcuation is different. (row %
vs column %) In the screen shot (figure 1) below I've tried to
illustrate the issue. I've calculated row percentages in 'red'. As you
can see the 'row' percentage is not equivalent to the 'column'
percentage calculation...
If I have a table as below I can easily and quickly trend out the
volumes [A] by right clicking and selecting "trend selection". The is no
equivalent for trending the percentages [B] This leaves creating
calculated metrics as the only way to achieve the desired outcome. As a
result, we are facing a significant proliferation in calculated metrics,
which is quickly becoming unmanageable. For instance, just to be able to
trend the above requires the creation of 6 calculated metrics… (% IE, %
Chrome...
I know I can right click and select "copy visualization". However, given
the way the rest of the interface works Ctrl + Dragging a component
seems to be the most intuitive way to make a copy It would be nice if
this was made available 🙂
The way freeform tables and visualizations link is our number 1 issue
with workspace so really hope you do something about this! 🙂From a end
user "self service" perspective, we are having terrible trouble getting
workspace to work for us because of the way visualizations (e.g. line
graphs) and freeform tables interact.Use case 1:Scenario: We give an end
user access to a freefrom table that has a visualisation attached to
it.Issue: As soon as the end user interacts with the table (e.g.clicks
or ...
