We are making great use of the component 'tags'. However, it would be
really useful if Adobe enhanced the 'out of the box' tags to allow some
additional granularity:#MetricsAt the moment all metrics are lumped
together but it would be great to be able to quickly filter
on:calculated metricscustom eventsdefault metrics (e.g. page views,
visitors, evar instances etc)#DimensionsAt the moment all dimensions are
lumped together but it would be great to be able to quickly filter
on:custom propscustom ...
The system for tagging components is really useful in Adobe Analytics.
However, something that would be significant enhancement for us would be
to be able to search for components that are not tagged with a specific
tag i.e. exclude from the list of components returned those containing
specific tagsPlease could this be considered?
Just wondered if this was on Adobe's radar at all?Using Ad hoc to do
this used to be my 'go to' answer for those people who'd ask the well
meaning but flawed question:'Can you tell me the top 10 journeys on the
site?'Top 10 Journeys only probably account for 0.00001% of visits (so
pretty useless), but what they were really asking was how do users get
from 'A' to 'B'.We could really do with some way to answer this in
Analysis Workspace... please
Thanks Alan, I loot at the API documentation but it didn't look like you
could get at the component curation set up of a VRS through the API
unfortunately.Anyhow, component tags have come to our rescue as we've
been able to work around this issue by tagging all the common components
that we want to include and then filtering on that tag within the VRS
component set up page. A bit of a pain having to go through and tag each
component but at least it's a one off job rather than having to do each
V...
It would be a massive time saver if it was possible to copy the set up
of one VRS to another existing VRS - particularly the component
customization settings.We have many existing Virtual Report Suites that
we are trying to align. One of my poor analyst is currently facing the
prospect of spending days of his life going through and aligning
thousands of components between these multiple VRSs. Alternatively,
we'll have to remove all the existing VRS and start again which causes
it's own problems....
Just wondered if there was a reason why you wouldn't put all you data
into one report suite and use virtual report suites to split back out?
Is it a performance thing or something else?
Our biggest problem with this behavior is the following scenario where
we have an application process that users can apply for several products
through.We wanted to have a fallout report for the different steps with
a panel level segment drop down filter for the different products over
the top of this. However, if a user applies for more than one product in
a visit data from one products shows in the fallout for the other which
is a real pain It means you potentially have to build out 20 fallout...
One thing that has tripped us up is that panel level segments are not
applied to the fallout report in the same way as Ad Hoc Analysis.To
recreate the same affect you have to add the segment to every touchpoint
which is a pain.I was wondering if Adobe might consider aligning this?
(or at least explaining why they are different)Workspace: Make Fallout
visualization respect hit level panel segments
Our biggest problem with this is the following scenario where we have an
application process that users can apply for several products through.We
wanted to have a fallout report for the different steps with a panel
level segment drop down filter for the different products. However, if a
user applies for more than one product in a visit data from one products
shows in the fallout for the other which is a real pain This feels like
a very common use case that can't be properly accommodated.
Adobe have changed the way fallout reports in Analysis Workspace apply
panel level segments verse previous tools such as Ad Hoc Analysis (As
described in this Fallout help article)Hit level segments applied at a
panel level are not applied at a hit level to each touchpoint in the
fallout visualization. Instead the fallout ignores the instruction and
applies the segment at a visit level instead. It means you get some
weird effects where data that you would not expect bleeds into the
fallout.We ha...
Is it possible you have a conflicting Adobe Analytics processing rule
which is overwriting the value with just the URL path?Can't think of any
other way data would be affected between data warehouse and the
reporting interface.
Yes, I think you've understood what I'm getting at.At the beginning of
your original post you said you "work a lot with the previous page
dimension"So I assume you've got access to both:a custom prop or an eVar
which is capturing 'previous page'and the out of the box 'page'
dimensionI'm suggesting breaking down 'previous page' by 'page', which
in affect becomes a 'next page' report(If you don't have a prop or eVar
with 'previous page' captured into it then you should get whoever looks
after your...
'Next page' in a table format:It sounds like you are capturing the
'previous page' into a prop or an eVar and using this as breakdown on
'page' to see what the previous page was.Conceptually you can just
reverse these dimensions to get a 'next page' reporti.e. when you break
'previous page' down by 'page', previous page = page, and 'page' = 'next
page'Does that make sense?
Urs also has the answer to the how to segment on the last hit. We got
into a discussion about this the other day against an idea on the forum.
You can check out his solution here: Make it possible to segment on the
hit of the exit page and entry page
To directly answer your question, you can absolutely set an event
without having to use an eVar.However, the reporting in your post should
be possible through segmentation/a calculate metric without using an
event or an eVar at all if you've got your implementation right. Whether
you are capturing the 'contactussubmitted' as a page view or as a custom
link tracking call you should be passing an identifier that you could
use to segment on to create this ('page' [name] on a page view, or
'custom l...
Hi Jen, great to hear you are still working on the export Just wondered
if you are still considering changes to the format of the export to make
it easier to work with?(as per your comment in the following thread:
https://forums.adobe.com/ideas/10152 )
I'd actually like to be able to get at time between any two hits.I'd
rather not be limited to just where we have implemented events as use
cases will come up where we don't have events set. e.g. How long did it
take to get from step 1 to step 2 of the application process?It would
also be good it the fallout report showed average time between
touchpoints.
One of the problems we've ran into in the past is where a particular
data set has some outliers (e.g. one really high value). The auto
formatting then seems to use this to set the limits for the formatting.
It then doesn't show the nuances for the majority of values which are in
a much narrower range.
That's really useful - I couldn't figure out how to do this with
segments but this works really well!I also found a work around for
isolating the first page view:Use processing rules to set an event every
time the page URL existedserialize the event to record once per
visitThis means the event only gets recorded on the first page view (all
other attempts to set are ignored due to the serialization). The event
can then be segmented on.Not sure if there was a pure segmentation way
around the first...
The centralized management/linking of segments and calculated metrics is
great for speedy maintenance, but there are some key scenarios where I
really wish I could break the connection to the master
segment/calculated metric (e.g. so changing a segment no longer updated
previously linked versions of the segment used else where).An obvious
scenario is where a panel is copied as a starting point for new panel -
In this case any changes to the calculated metrics or segments in the
new panel also af...
For most normal dimensions you can only generate dynamic columns for the
top 5 items. 5 is a very small number (I needed 8 the other day and was
stuck!) - is there any chance of increasing this? If there are
performance worries, even a small increase to 10 or 20 would be very
useful! The feature can be seen here: Dynamic Columns In Analysis
Workspace Freeform Tables | Adobe Analytics - YouTube
Being able to hold ctrl and 'drag' to copy an element is a really useful
time saving feature that works almost everywhere except the calculated
metrics builder.This is particularly bizarre given ctrl + drag does work
in the very similar segment builder It would be very useful if the
calculated metrics builder was in line with other areas - please can you
consider this?
