I agree. Offering an Analytics solution without at least some kind of
basic stitching (e.g. like Google Analytics User ID feature which at
least does session backstitching) is not up to today's reality. Having
to pay extra for CDA just to get a sensible Visitor journey is imho not
justified.
Given the focus on making AEP a sellable product, I don't expect Sub-Hit
segments to come anytime soon as it has been requested for years now
(this thread alone is from 2018), and Adobe has not given E-Commerce use
cases much consideration in their recents features which all do not
support sub-hits.But what could be a good compromise would be to take
functionality that is already there and make it a bit less tedious for
end users: make drop-zone work like dimensional value filters if you
drag a ...
Thanks, but this is now 2 1/2 years old, and being "in the backlog"
means basically nothing but that is is in some big list of potential
features for the future...
@jen_lasser In the last week alone, I have had 3 more cases where our
users are completely confused and make FALSE reports with FALSE
conclusions, and I cannot blame them.Just today I had a guy sending me
an email asking why the results are different if he removes the filter
from the table because it should be simply a duplicate of what is in the
dropzone already. When will at least this misleading colouring of the
filters be fixed (it looks like a filter in the dropzone, but it is a
hit-based s...
Not sure @AlanSc . What I mean is that the dropzone panel "filter" would
be simply the same as adding this filter on top of each table:So the
"Sport & Freizeit" filter on top would mean that it works as if it was
actually on top of the table of each of the tables in the screenshot,
just like in the example of the "Hauptmetriken..." table on the right.No
new query logic is needed for that imho.From what I have heard it was
actually even intended to work like this (because same color should mean
s...
@jen_lasser Thx for the info. I was really angry yesterday due to this.I
think at least the dropzone filters (which are actually hit-based
segments) could be easily made to work like sub-hit Filters. There is no
additional logic needed. It would be simply the same logic as if I
dragged a dimensional Value Filter on top of all tables of the
panel.That would already help save a lot of time and confusion among
users (they always wonder why both dropzone and table filters are
yellow, but work comple...
@jantzen_belliston-Adobe Archived? Just like that? Not even a comment
why!? This is a highly voted feature and imho still a must for
e-commerce.Why archive it?
@trevorpaulsen Do you think this will be implemented any time soon? It
is also a big issue in the new mobile app where we can only apply
hit-based segments. My ecommerce clients would love to use the app, but
they say it is no use when they cannot focus on sales in their
assortment categories only.
Sorry please Check the question again. It appears it wasn’t understood.
Iknow how to use the network tab. The problem is the adobe timestamp
logic.If the next page after the click loads fast both the click and the
pageviewhappen in t he same second and get the same timestamp. Adobe
then puts thepageview first and thus the flow looks reversed.asheeshp
schrieb am Fr. 29. Nov. 2019 um 19:42:Adobe
Analytics Timestamp Logic makes Fallout and Flow Reports almostunusable
created by asheeshp in Adobe
A...
Could this be moved to the Ideas Section of the forum? It is actually a
bug that needs to be fixed. I thought I posted it there, don't know how
it ended up here?
We noticed a general issue with how Adobe processes its data. If 2 Hits
happen in the same second - e.g. a tracked click on a Teaser link and
the Pageview of the next page, Adobe Analytics seems to order them in
the wrong way - or in a random way. This leads to problems with Fallout
Reports and Sequential Segments because the assumption "User first
clicked link x (Link Click was tracked), then viewed Page y" will not
work!Example: We want to create a fallout report where a user clicked on
a trac...
This is something most Adobe users do not know nor expect nor does it
make much sense: Marketing channels have a rolling 30-day expiration,
whether a channel was touched or not. Tracking codes have an expiration
based on when the variable was defined.
https://helpx.adobe.com/in/analytics/kb/comparing-tracking-codes-and-marketing-channels.html
"Expiration differences: Marketing channels have a rolling 30-day
expiration, whether a channel was touched or not. Tracking codes have an
expiration based...
This is an absolute must-have for any ecommerce client, and Adobe boasts
itself with E-Commerce.Why?1. It totally confuses people that dragging
the Product Category "Sports" onto a table is not the same as having it
on top for the whole panel in the Segment bar.2. It makes a looot of
flexible reporting very tedious. People have multiple products,
categories, brands etc. in their basket. Example: This is an example of
a category Level 1/ Level 2 / Brand Dashboard where people can quickly
switch t...
Flows and Segments right now are not recommended to be used together.
But Flows in general also have issues even without segments in that the
Entries often do not show if the number of Entries is low.Moreover Flows
do not match what I get for the exact same dimension and time range in R
& A and Ad hoc. Ad hoc and R & A look like they are working, Analysis
Workspace seems to be buggy (yes, I am using the Visit Container to be
comparable to R&A and Ad hoc).I would want to apply segments like "only...
I think the general issue here as with many features is that Adobe
product management & QA seem to test with basic metrics only a lot, and
on huge wide screens. This is why such things don't bother Adobe as much
as they do clients. My recommendation: Force everyone on a laptop and
work with real customer setups for testing & qa.Of course "Visits" and
"Revenue" are short, but you don't buy Adobe Analytics to keep stuck at
such basic metrics. We are using 80% Calculated Metrics, and it is
mostly i...
i have this a loooot, it is not edge case, 90% of my workspaces are
affected by truncation.And it gets worse when we are splitting columns
into many subcolumn, then even the short values like "Page View" become
unreadable, especially when wowrking on a laptop with a smaller screen
That reduces the problem slightly, but still does not work: See e.g.
this Pathing Report. I have a segment on it to count only Pageview Hits
and exclude Reloads, but we still have a lot of movements from /search
to /search.
We are heavy Alert Users.The challenge: We want *relevant alerts*.
Adobe's Anomaly detection system is ok, but 95% of the *Hourly Alerts*
it spits out are completely irrelevant as traffic simply oscillates too
much from one hour to the next, AND because Adobe seems to take only the
last 24 hours into account when looking for Anomalies. So we had to
deactivate all our Hourly Alerts.1. However, Daily Alerts are too late
for something really critical, so Adobe needs to either improve the
Hourly Ale...
there must be something really deep down in the architecture of Adobe
analytics Preventing regexp in Filters. It is so common in other Tools
and so god-damn useful that I don’t see that any other reason would
justify its absence to this day.at least the advanced filters from
reports and analytics should be allowed in workspace again
When you share a Short link to a Workspace or R&A Report or when users
get an Alert email with a link to "Analyze Further", these links contain
their own session IDs which almost always requires users to log in
again. After logging in, they most of the time do not land on the report
they clicked on, but on the normal landing page. After then clicking on
the link again, they usually get to the report they wanted to see.
However then soon often follows a log out of the other tabs a user is
using t...
Just note everyone that the "Repeat Instances" Checkbox has no effect on
Flow Reports in Analysis Workspace. As for Dave1, just use "Single Page
Visits" and create a metric "% of Single Page Visits" on the fly. Single
Page Visits makes way more sense than Bounce Rate where every little
Event Hit causes a non-bounce.
It is time that something happens with truncation, the number one
readability issue with Analysis Workspace.My colleagues keep complaining
about unreadable Workspace exports. Whenever using more than just a
couple of columns in a table, the truncation of text that Adobe
designers seem to love (but I hate) becomes problematic. Especially when
sending them via PDF when a recipient can't hover over a cell to see
what he is been missing.As an example, see the product report attached
some people get ...
I think that's not the question. He (and me too) wants to create quick
segments for one-time usage without bloating the number of total
segments.I am creating segments all the time, most of them I use just
once or twice, but then when I have to decide which segments are worth
sharing with the rest of my company I am standing in front of a huge
list and it is tedious to work through that. If I know that I probably
won't need this segment again, it would be cool to just create it for a
one-workspa...
