Replies

Avatar

Avatar

frankd55973318

Avatar

frankd55973318

frankd55973318

10-05-2019

I've seen, on the Ad-Hoc product/download screen, that there is now a version that can be used with Java 11. Will this version also be killed off or will it continue you work when you end of life Ad hoc?

Thanks.

Avatar

Avatar

Locutus243

Avatar

Locutus243

Locutus243

01-07-2019

Most people replying to this thread seem to have similar ideas...that workspace is the much needed upgrade to the standard reports. Instead of trying to replicate ad-hoc analysis into workspace, Adobe should be looking to ensure all functionality available in the standard reports is available in workspace (e.g. Calendar Events). And then leave ad-hoc analysis for the analysts to be able to quickly drill down further.

It is undoubtedly much quicker than workspace and most importantly you can export 50k rows. I know this functionality is 'in the pipeline' for Adobe...but that means until then we have the limited capabilities of data warehouse or spend weeks downloading 400 rows at a time...it's just not feasible. Our solution has had to be that we set up a clickstream feed and force our business outside of the tool...which means we become supplier agnostic.

Avatar

Avatar

A_Wathen

MVP

Avatar

A_Wathen

MVP

A_Wathen
MVP

11-11-2019

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

Avatar

Avatar

A_Wathen

MVP

Avatar

A_Wathen

MVP

A_Wathen
MVP

11-11-2019

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 reports where you could have had 1 fallout report with 20 drop down options.  This feels like a very common use case that can't be properly accommodated.