User Profile

@admoseremic 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.

Any update here? This is still an absolute Must-Have. 

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?

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.

Most wanted by me too. Still going to reports and analytics for sensible pathing reports (numbers-wise).

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

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.

RegExp in Segments AND in Report Filters. One of the major things I miss in Adobe Analytics!