As indicated by ForgotPassword4, the time spent on the last
page/interaction is not counted. However, there is a way around this in
some cases. The "last page" is typically the last one the user sees
before leaving the site. So on domainA.com they click a link that goes
to, say, domainZ.com. You can create a function to generate a custom
link type call (pe=o) if the destination domain is different from yours.
This provides an "exit" call that will allow the time spent calulation
for the last (re...
I use it often to trouble shoot users (as opposed to troubleshoot tool
permissions). For example:visually look what the user might be seeing
based on some badly worded ticket to clarify the problemmake custom,
one-off segments on a users behalf, of fix segments they have
created.create custom one-off metrics on a users behalf. (Not worth
sharing).review a report they have saved or have had shared with them by
someone else and have questions about. fix a dashboard or report they
are creating and ...
I do a similar report every year based on the Analytics logs. Takes a
while, so I only do it once a year. This report goes to the management
with the checkbook. It would be nice to be able to use the data as a
reporting source in a standard report suite. So far as I can tell,
Analysis Workspace is not tracked, or at least the tracking is not
exposed to admins like SiteCatalyst usage is. As our users begin to
migrate to workspace, this annual report will begin to under report
activity. So my mana...
I have a number of report suites that use a large number of the same
segments. I created all these under one report suite. I have assigned
these segments to the appropriate user groups. However, they are hidden
under the check box that displays only the segments created under that
given report suite. For most report suites, users see no segments unless
they uncheck the box every time they open the segments list. There are
two issues. 1) Unchecking the box all the time is a rather tedious user
The plug basically buckets the time into time bands. This is also
useful. With some extra work, you can set the time to a metric and get
the average page load time for a page or group or pages. I assume the
latter is what is being requeste here.
I have also had complaints from users who are less than every day users.
I think the issue is the the fly-out version allowed users to quickly
scan the structure, to know both where they were and where they might
need to go. The new menu requires users have a stronger pre-knowlege of
the struture. The trade-off is, of course, that sometimes the fly-out
ran off the bottom of the page.
I have seen that when you log into Analytics, the alternative dashboard
defaults to the report suite that dashboard was created under,
regardless of the report suite selected when the user first logged in.
If you change report suites, then the dashboard will sync with the
report suite you are in. However, If the user does not change report
suites, the dashboard continues to display the "wrong" data. Not a good
Total Time Spent and Bounces are not calculated as I would expect when
using a Segment.Filtered out calls are not counted when calculating time
spent, inflating the time spent for the given value.Filtered our calls
are counted when calculating Bounces, deflating the bounces for a given
value.I would like the reverse; filtered pages to be counted for
calculating Time Spent and ignored for calculating Bounce. This request
is to provide at least the option to count that way. Gritty Detail:
WebMD is using the product variable to get around the serious string
length limitations of a list prop. In this case, we pass the link
impressions in a concatenated string and an event. We pass clicks for
that link in connection with another event. Thus, we can calculate CTR
of the link. Our issue is that we pass the click event with the
destination page (which gives us the links that drove to the page using
a correlation) while the impressions are passed with the origination
page. This means yo...
We have several custom insight variables that are candidates for
creating segments, alone or in combination. To get all the traffic into
the segment, these values would need to be passed in both page view and
custom link calls. In adding the value to custom link calls (previously
only passed in a PV), we could still get PV while the instances would
increase. In correlating those values, however, the correlation would
now return the higher Instances, not the previous PV. So we apparently
need to ...
Currently in the v15 Fall Out report, if you go from a traffic report
with Page Views selected, the Fall Out value select dialog will find PV
calls and the subsequent report will produce a PV based fall out report.
if you go from a traffic report with Instances selected, the Fall Out
value select dialog will find Instance calls and the subsequent report
will produce an Instance based fall out report. This is very good, as
sometimes we need to trend PV calls and sometimes we need to trend
Good to hear this is still alive. For us, this would be particularly
useful, not just for campaigns but other variables as well. (I count 10
for us at this point). As you noted, St. Bernard is lacking a scheduler
and (last time I checked) full regex. If this functionality can be
"utilitized", it would also be useful to be able to use it in the
context of processing rules.
As our implementation becomes more dynamic, the need to more carefully
manage correlations is increasing. It would be useful to have the create
date displayed and the ability to add some notes on what the correlation
was intended to be used for. This in turn would help inform the decision
about removing correlations that may longer needed (to make room for new
ones or to just reduce the overhead).
Allow Processing Rules to parse and set parsed values. Similar to what
the St. Bernard tool does, allow processing rules to parse a delimited
value and set the parsed value into another variable (regular or
context). Example 1: For xxxx_yy_zzzzz, look for the value between the
first and second underscore and set that value into prop1. Result: prop1
= yy. Example 2: For xxxx_yy_zzzzz, look for the value from the
beginning of the string until the second underscore and set that value
into prop1. Re...
Just a thought. Not very often, but on rare occasions someone suggests
something that would be bad for me if implemented. Of course, I can just
add a comment in the absence of a demote button as an alternative.
Issue:Calculated metrics for Instances and Participation are available
for props at the report suite level to be created by each user
individually for each report suite. However, they are not available for
Global Shared Calculated Metrics. This diminishes to some extend the
utility of Shared Calculated metrics. 1. Although Instances in v15 is
the equivalent of PV in v14 and the Custom Traffic (prop) default metric
in v15, v15 does not support creating any Global Shared Calculated
metrics for pro...
Building upon: by lexham on 01-26-2012 09:56 AM We'd like to see:
ability to hide and manage segment visibility across SC, Discover and
DWto ensure that segments created by users in SC15 are only visible to
those usersprovide some mechanism to share segments between users (so
someone builds a super complex segment in SC15 but wants to share with
their team - how can they do that?)Once a segment is built in the SC15
interface to have the list automatically refresh - at the moment we have
Another way of looking at this is that there will be some segments
common to all groups of users and some segments specific groups of
users. E.g.. Everyone might want to see a US only segmentation but only
some users need to see the Profession Type segment. This might also be
accomplished with categorization folders. Id access needs to be
restricted, display or hide the folder.
As a media site one of our key metrics is Page Velocity (the number of
pages seen after setting the value, titled page consumption in the image
below). Apparently participation metrics cannot be populated by channel
because it is basically a sub-relation and participation metrics are not
available in sub-relations. In the Marketing Channel reports, for
example, I can't see which traffic sources is best driving this this
most important metric.
As a media site, we want to be able to see the channels driving to
various sections of the site or for a given page. In other words, broken
down by custom traffic variables. So if I am the person responsible for
our Health Center section, I want to see the channel report for that set
of pages.In addition, as a media site one of our key metrics is Page
Velocity (the number of pages seen after setting the value). Apparently
participation metrics cannot be populated by channel because it is
Request: Word wrap column headers in dashboard reports. Current
functionality: The column headers showing the tracked value can be
truncated. Business impact: If you have multiple items in a trended
report the values being reported on can be unintelligible, making the
reportlet useless. There appears to be no work around.
When I create a new account and send the new Welcome email, the email
contains the password I set. When I update the password for an existing
account, click the require password re-set box, and send the Welcome
email, the email contains the temporary password I set. When I update
the password for an existing account, DO NOT click the require password
re-set box, and send the Welcome email, the email DOES NOT contain the
password I set. It would be useful to populate the new password for this