It would be helpful to be able to apply a slightly different color
scheme when switching among report suites in SiteCatalyst. When a
company is dealing with multiple report suites for brand and/or wired vs
mobile experiences, it would provide one addiitional reminder of which
data is being views.
Since St Bernard is going away and some of those capabilities are being
pulled into SiteCatalyst. Please note that I find it VERY helpful to be
able to pull up records, edit elements of the classification and upload
immediately. No rules, no spreadsheet downloads / uploads. Just correct
In St Bernard - set the default width of the St Bernard grid to fill the
whole screen. That way when my key has many characters, I at least have
a chance to see the whole value AND update the classificatios.
I would like to see movement from page to page within a group of pages
within my website. Ideally, I'd use the Paths --> Pages --> Full Paths
report but limit it to a group of pages by building a segment to only
show me movement among them (ignore extraneous pages) . Alternatively,
starting my full path report with some specific page within a visit, not
at the entry page, would allow me to zero in to user behavior around a
difficult process step. Need more info ??? - I'm happy to give specific
We are getting started with processing rules and can already see that
auditing what has been programmed will not be trivial. It would be
helpful to have a tool or two. Off the top of my head - an export
function that would spit out the text of the active processing rules
within a report suite. AND/OR a compare function that would highlight
the differences between 2 report suites - example between ABC
Development and ABC Production. That way - we can be sure that what we
have in one environment i...
Or if using traffic as the metric - be able to compare to a day or a
week prior. Then can use % difference and not get extra alerts for night
time or weekend fluctuations. Exam[ple alert me when traffic is x%
different than this hour last week. Love the % CONVERSION ALERT!
An alternative if we have to see them all, is to allow them to be
collapsed based on author or folder. If I have 5 for project "TowTruck"
and 5 for a request that I've set up in folder "JoeSmith", the drop down
should default to the folder names and allow me top open only the folder
that holds the one I want to find. Should not have to scroll through the
hundreds that have been created since the beginning of time in DW and/or
I have a workspace with several reports - all sharing the same
segments.When I spot a problem with a segment, and update it in one of
the reports, I would like to have all of the reports using that segment
to be updated automatically. As it stands now, I could have multiple
reports with the same segment name - but with different segment
definitions all active within a workspace. Leads to much confusion.
It would be WONDERFUL if in the email that I receive when an ftp'd data
warehouse report is ready to be picked up - that the number of rows that
have been returned in the report request would be stated. I am running
reports and the data set coming back is too big to display completely in
excel. So in the Details section of the email in addition to these
items: there was also a line for "Rows returned" nn,nnn,nnnFile Delivery
File Name:Jo_Lynn_Clark_daptiv_458.csvFile Format:Comma-separated Value...
The admin role here is shared by a small group of individuals. We are
setting up alerts for high/low volumes of pages, and certain custom
variables.However, the only person who can see the alerts that are
emailed to the whole group is the individual who created each specific
one.Not only can others not see what alerts are set up, but only the
author can make modifications - we need to have shared access to allow
for modifications as we cover for each other.
Two approaches - doesn't matter to me which you do - but we need to
recognize both URL parameters as representing paid searches: ECID=SEM
and ecid=sem. Either make the string case insensitive - or allow
duplicate rules that are case changes of one another. From Omniture
Client Care: Paid Search detection appears to be case sensitive and the
admin console prohibits adding two rules that are essentially different
capitializations of one another.As for setting up duplicate rules that
are case chang...