Description -Currently, the segments and metrics available in the
Annotation Builder are only those that are created by the organization.
They do not include segments and metrics that are managed by Adobe (e.g.
the 'All Visits' segment, or the 'Weighted Bounce Rate' metric). Why is
this feature important to you -Organizations that use Adobe's segment
and metric definitions will not be able to have Annotations applied to
them, as these segments and metrics are not available in the Annotation
Description -Within the Report Suite Manager, we're given an option to
add a Description to Traffic Variables, Conversion Variables, and
Success Events. These descriptions can help users understand what a
variable is tracking.Unlike with s.eVars and s.events, s.props have
Entry and Exit versions. For example, if s.prop1 is capturing the URL,
users may see Page URL (s.prop1), Entry Page URL (s.prop1), and Exit
Page URL (s.prop1) when they are looking at dimensions in Workspace. Why
is this featur...
I'm resurrecting this from the dead. Was this ever considered as a
potential improvement to Analysis Workspace? This is something that
would make my life a lot easier when it comes to managing projects.
I've noticed a substantial increase in traffic from Ashburn, Virginia
starting November 2020. This particular city is well known for data
centers, which leads me to believe that this traffic is bot-related. I
have IAB bot filtering rules enabled, though it's possible that those
rules aren't being updated by the IAB like they used to. Anyone else
experiencing something similar?
I think that leaving them on is a benefit for new users more so than
power users. If these are turned off by default, someone who is a novice
may not realize that these options are even available. Additionally,
having percentages turned off by default would mean using metrics that
are percentages, such as bounce rates, would show blank cells.
Alternatively, Adobe could allow users to set default settings for the
projects that they create. This would allow you, for example, to have
options like b...
I've been using the "Average Time Spent on Site (seconds)" metric to see
how long visitors are spending on a particular page, but am unsure how
to compare the metric from one page to the amount of time visitors spend
on any given page on average. In short, I need to recreate the "Average
Time Spent on Page" that was deprecated. Here's a sample question that I
should be able to answer: "My website has 100 pages. How long do people
typically spend on one of these pages? How does this compare to ho...
Description -Allow users to easily expand and collapse all containers
when using the segment editor.Why is this feature important to you
-Complex segments may require the use of multiple containers, including
containers within containers. The segment editor allows us to collapse
each container, making it easier to see how the segment is set up. It
would be helpful to provide an option to collapse all containers or to
have all containers collapsed by default when the segment editor is
opened, as ...
I've only taken AD0-E202, as AD0-E208 is new. Unless they changed the
AD0-E202 exam in the last year, a number of the questions were very in
the weeds with how Adobe Analytics worked and the whole thing felt a bit
dated. Reading through what someone should be familiar with in order to
pass AD0-E208, the description sounds like the exam deals with the way
that you'd interact with Adobe Analytics today rather than 5 years ago.
I'd consider AD0-E208.
Do you capture the timestamp in a dimension? If you do, and that
timestamp contains the date, then you may be able to create a calculated
metric using approximate count distinct. Note that you can use
approximate count distinct with a classification of the timestamp
dimension, which you'd likely need to do in order to isolate the "day"
component. For example, create a "Day Number" classification to extract
"05" from "2021.05.26".This won't give you an average outright, but you
can use it on a ta...