While I cannot speak to the adjusting the training period more
specifically (I think it's a great idea), you can send anomaly detection
reports via report builder and excel. There's also a free training video
on how to load and visualize anomaly detection reports in Excel, here:
I just discovered the forecasting feature in SC and got really excited
and tried to read up and use the feature. I turned on the feature and
then went to see it in reports only to see no results. I contacted Adobe
support to hear the sad news that its currently a known bug and not
working and worse yet that it may be removed completely as a feature.
We've been looking for way to be more proactive with analysis through SC
and when we found this feature we were so hopeful so its disappointing
Yeah, I'm aware of that option but thanks for the tip anyhow. My issue
is not that I use the back button in the browser, my issue is more with
the navigation itself required to move between admin tools and
report/analytics tools. It's just a bery cumbersome interaction.
Adobe needs to fix their documentation for SiteCatalyst. The biggest
problem is that its not up to date & therefore not correct. there are so
many references to version 14 with no mention of version 15. This leads
to confusion & quite frankly errors because definitions/usage keeps
changing in SC. I can't tell you how many times I have had to contact
Adobe support just to clarify a definition or usage of something in SC.
Even worse, as an analyst I am either giving faulty analytics or not
I would like to recommend adding the ability to print/list all
classfications for any report suite. Currently, the only way to review
existing classifications is to go through the Report Suite Manager and
review them one by one. IT'd be useful and helpful if we could list all
classifications for a report suite as well as across report suites. This
would hopefully give us the ability to review our labeling/naming
conventions and verify how they are being created across suites.
I think it'd be helpful if there were a way to have versioning of SAINT
classifications. Particularly for imports. It's quite easy to override
what's been imported previously without any record of what has been
done. Versioning or having a history at the very least, would give
administrators at least some idea who/what has been imported and allow
them to better manage the system.