Currently, the component side bar shows custom dimensions, metrics and
segments that have not been created for the selected report suite.
Unless I missed how to adjust some settings, can this be changed for
You bet! Thanks for fostering the discussion here, this really helped us
in making our decision. We will be continuing to think about project
level settings as well, to help in cases where customers do not want
this as their default.
I think it could be interesting to have more options in the number of
items to display in a table: I sometimes would like to have options for
15 or 30 rows depending on the data or layout of the dashboard.
Hi Brandon, the breakdown by position does not seem to be the solution
to the problem that I, and I believe other people in the thread, am
observing. I do agree that this fixes the original problem of the
thread, though.In my case for example, I created a report by Tracking
codes to analyze performance of some campaigns, with two breakdowns, two
custom variables. New tracking codes are added each week, and I have to
manually break the new ones down. Breakdown by position does not help
I think what Urs was referring to was to create a separate report,
listing visitorID's by the calculated metric reloads/pageviews. That
way, you could immediately identify visitors who have an unusually high
ratio of reloads, and investigate them first.This calculated metric
definition worked pretty well for me:The reload hits segment was simply
defined as all hits where reloads exists.
I would recommend posting your insight on this previous
subsmission:Workspace Download PDF in different page formats Which
already contains some replies. If we group them together we can make it
clear that this should be a very, very high priority
We have reports that are sent to the same people or group of people that
are created in different workspaces, for data collection reason, but
that are sent at the same time. I think it could be useful to have an
option to group together the delivery of multiple workspace files in the
same email, instead of sending three, four, five emails at the same
time.In some cases, we have this issue also due to the fact that
currently it's not possible to split PDFs in multiple pages, so we
cannot combine ...
the objectID variable is used to differentiate links on the same page
that may otherwise be bucketed together. For example, if you have a link
to your homepage at both the top and the bottom, sometimes there isn't
an easy way to differentiate the two. Setting the objectID variable lets
you group your links however you'd like.Unfortunately this variable
isn't available in reporting, since it is generally used to properly
This may seem like a bit more work but what is you were to create
internal tracking IDs for the 133 links on that page?Then you could do a
site wide report show top link accessed(by ID) and then even correlate
the top five IDs to see all pages they each accessed. Now you can then
event associate events to the IDs get a more robust view of what users
are doing outside of flows.If you then do a flow report make a segment
where visit contains ID(s) and then see more specific user journeys
Currently, the .csv export from a dashboard includes only data that is
presented in tables, not data behind graphs and charts for which the
table has been hidden.I believe it is more logical and it would be more
useful if the .csv contained all the data that is used in the dashboard
(as you would have in an Excel file a tab with the graphs, and a tab
with the source tables).I would like to send a dashboard that is as
visual as possible, I find that tables tend to overload it.
Unfortunately, if I...