I am very, very pleased to report that segment management is now
available with the Adobe Analytics Spring 2014 release! I believe we got
most of the requested features into the release; if there is something
that we missed, please create a new idea and we will monitor it.
Agreed with all the comments above. We ran into the same allocation
issue trying to track the internal campaigns and their click-throughs.
And were very frustrated to findout about the full allocation of s.lists
variables. Even more frustrating - none of the Customer Care reps
pointed that out when we wondered why all list values are getting
click-event allocations. We ended up using s.products instead - which is
not the proper way of tracking internal campaigns and won't a good fit
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
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...
It would also be nice if we could have the rows returned come as an
additional file to the FTP location. This would allow me to automate the
loading process to ensure rows sent = rows loaded into the database.
This could also be implemented as a "Totals" row to the existing file
which could provide not just counts, but total for that column.
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.
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...