Webinar: Adobe Customer Journey Analytics Product Innovations: A Quarterly Overview. Come learn for the Adobe Analytics Product team who will be covering AJO reporting, Graph-based Stitching, guided analysis for CJA, and more!
With SiteCataylst 15 migration we noticed that error pages report disappeared. The only solution to this seems to be an additional prop = not handy at all.
I've actually been working on this problem as well. Decided a nice workaround would be to use dynamic variables in the pageName so we can not only see what URL's are being accessed, but what paths users are taking to get them there. Here's what I'm setting for pageName on my 404 error pages:
s.pageName='D="404 ERROR: "+g';
This way I can easily filter my Pages report to 404 ERROR and also get a complete list of URL's.
Wasting a prop on this doesn't really seem worthwhile to me either.