I would like to be able to output data in a format from Discover that is
conducive to creating a PivotTable. Of course, not all metrics are
suited for a PivotTable, but many are. The inclusion of the "Total" rows
for individual line items can add a lot more time to creating a
PivotTable with Discover data.
Processing rules currently have a number of different types of
conditions that can be added to a rule. Unfortunately, there is no "Does
Not Equal" condition. One current alternative is to have a condition for
both "Does Not Start With" and "Does Not End With", but that doesn't
always work. Some rules are impossible to create due to this omission.
I had a ClientCare ticket open and through my interaction with the
agent, I found that counter eVars could not be segmented by the less
than or greater than qualifiers for a segment condition. Instead, these
qualifiers are meant to only be used with "Total (events)" as the
condition, like Total Social Shares is greater than 1. I could not do a
similar segment with Total Social Shares if I had a Total Social Share
counter eVar increment "+1" on each share. Since the values in a counter
eVar are n...
I was finding that when creating a condition off of pageURL, that my
processing rule would not work for link tracking. Despite pageURL being
sent to Adobe, it couldn't be used as a condition because it wasn't
really counted in reporting. At the least, I noted to the ClientCare
agent that this should be noted on
since it's potentially confusing.
Thanks Erik. This message typically comes up after waiting for about 1/2
an hour. The wait times aren't typically that long, so that doesn't
bother me as much as being kicked out of line when I've waited so long.
The following message is incredibly frustrated after waiting 30+ minutes
for ClientCare: "There are no agents available to chat with you right
now. Please try again later." If ClientCare truly is a 24/7 service
(Monday - Sunday: 24 Hours) then this can never be true. I tend not to
call because if I call I won't have a record of our discussion. I'm
willing to wait longer than the estimated amount, and I understand the
estimated wait time can be difficult to get to since the complexity of a
We have a wide array of users of different skill levels in our
organization. With that, we find that we get some questions that could
be easily answered with the Knowledge Base or Help Section. We recommend
Knowledge Base in training, but we find that it isn't typically used. It
would be really helpful if there were a little label on reports that
said "Need Help?" or something of that sort, and could be expanded to
show a list of the top few of the possible relevant articles given their
In ReportBuilder, I think it would be useful to create segments that
change dynamically based on the output of data requests. Currently,
ReportBuilder allows you to apply segments to data requests, but they
have to be pre-created in the SiteCatalyst 15 interface. I think it
could be incredibly useful to be able to allow segments to be based on a
given period's top reported report line-item.
Ben, Would you be able to validate that this isn't how the container is
currently working? As I mentioned in your blog post comments
I've gotten inconsistent advice in the past from Adobe on how this
container works. I've found some recent evidence that suggests that the
container is time-bound.
Instances are available on most traffic reports now in SC15, but I don't
see them as available in hierarchy reports. Adding instances would be
more consistent with how other traffic reports work when tracking
non-page view activity rather than incrementing the hierarchy views
After transitioning to SiteCatalyst 15, I noticed that Unspecified was
removed from hierarchy reporting. This wouldn't have been the biggest
deal, but I found that when you drilled down, the Total Hierarchy Views
for the hierarchies above that level is lower than the actual total
hierarchy views. For example if I have 5 hierarchy views for item 1 on
level 1, if i drill down to look at the level 2 hierarchy within item 1,
if there were 2 views of items that had specification at level 1 but
It would be extremely useful to have a visitor container that takes into
account the reporting period rather than the entirety of the visitors
affiliation with the site (like how the visitor container works now).
The visitor container is useful, but this secondary sort of visitor
container would serve a different purpose for analysis.
The ability to create segments across multiple report suites in
SiteCatalyst 15's admin console would be incredibly useful. Rather than
creating the same segment multiple times for each of our report suites,
this would allow me to make the segment creation process quicker.
I was trying to construct a dashboard that had trended data based on a
search. Unfortunately, SiteCatalyst interprets the top five trended
videos as something I've specified (where it says "Selected Items:
User-Identified"). This causes the reportlet to think that I want the
same five videos each period rather the top five videos based on the
search. It would be really helpful if the trended report would recognize
the search each time period.
I had issues with getting ReportBuilder to work with vlookups as
reference cells for data requests. ClientCare explained it as "Vlooup is
not a part of server side element, therefore, it won't be included when
it's being refreshed from our server to generate the data to deliver."
He suggested to suggest it here so it can be added into the next
ReportBuilder upgrade. Having the vlookup will help make
ReportBuilder-based files easier to manage and dynamic for scheduling.
I would like to see video metrics such as video views and video visits
enabled to be used with SiteCatalyst's targets feature. The target
feature is helpful in tracking our traffic against our goals. Another
interesting way to enhance this feature even further would be the
ability to have an adjustable % completion metric included in video view
target reports with the ability to overlay the % completion on the graph
in the style of a stacked bar chart.