This is good to have. Dealing with users and their password isssues has
been a hassle. The workaround I've used is to always use the same
generic password when setting up the user account, always use the same
Welcome Email message that includes that generic password, and force all
new accounts to change password on next login. But you're right, that
should automatically be handled without me having to do that.
When setting up processing rules you are not always sure youwill get the
desired outcome, especially with suites that contain many rules. It
would be great if there was some functionality to run the processing
rules against a test string to see if the desired outcome is what I was
expecting. For example, I would be able to enter my value somewhere, and
see what it would look like after all of my processing rules ran.
Currently it is way too difficult to do any real testing to ensure the
Couldn't agree more. The current bot report is a great idea, but I would
prefer it was done in two stages. First enabling the report would just
let you identify all of the bot traffic, then we should have the option
to filter out that traffic. Identifying if we want it filtered after it
gets filtered is a little bit of a backwards approach. The ability to
identify our bot traffic and know before hand the impact of filtering it
out before we take that step would be a great addition to have.
In processing rules, I woud like to see an option when setting up a
condition to preform the action if the value of a variable has changed
since the last time it was recorded. So for example only copy the value
of prop1 to eVar1 if the value of prop 1 has changed since the last time
it was recorded during that visit. I understand that processing rules
cannot read cookies, so it would need to go back and look at the
previous hits in that visit to check for the value. This basically will
give us t...
I would like there to be a way to force variables to lower case from the
admin console. There are a couple ways to make it happen. When setting
up a prop or an eVar there could be the option to "force all to
lowercase" so I wouldn't see ford, Ford and FORD in the report. This
could also be handled by a change to the processing rules as well. There
could be the "force to lowercase", "force to uppercase", or "force to
propercase" options for any variable. I prefer the processing rules
method, but ...
I would like to ability to purge all of the values from a prop when I
want to repurpose it. For example, if I capture time of day in prop1,
but later decide that prop1should be current url, It would be nice if
all data that prop has captured could be purged so there are no problems
when viewing that prop overtime. I understand that this could be vary
powerful so it should be something that I would have to call client care
When uploading a SAINT file we have the ability to use FTP or a upload
the file right from the browser. When uploading a Data Sources file
there is no browser import option, there is only FTP. A browser import
option would be nice. I mean like really really nice.
The EnterpriseTV videos should be free. This would only help customer
understanding of the product, and would lead to an increased usage and
less frustration from users.Omniture can still charge for one on one
personalized training through Omniture University, but the videos should
It would be nice to be able to change the chart type in a dashboard
reportlet after it has been added. If you want to change the chart type
you need to remove the reportlet and re-add it to the dashboard with the
chart you want.
Can the note section on each report be moved to the top of the report?
It is buried at the bottom and it is not easily seen when reports are
opened. It can easily be put right inline with the report configure
Whenever there is a s_code update the users need to change the code
version number that appears in the page code to remain consistent and
that is not needed. In fact the code version number is not needed in the
page code at all. It is in the s_code file and can be seen in the
debugger so having it in the page code is redundant. I have many sites
that use v21 or better s_Code files, but the page code still says v15.
Can you please remove the version number from the page code comments?
When a user gets their account locked out from entering too many
incorrect passwords they have the ability to unlock their own account.
The problem with that is they have no idea they can do that!! A simple
request of a new password (the forgot your password link) will reset any
locked account. I get so many emails about users asking me to reset
locked accounts, that it is really becoming very time consuming. Please
please please add some language to the 'you are locked out' message that
In the Admin console it would be nice to have an online version of a
Solution Design document, or somewhere in the Traffic
Variables/Conversion Variables/Success Events sections to add specific
notes to where each variable is set and any notes applicable to that
Right now if I want to see metrics trended over a multiple year period,
the chart that is displayed starts at the first date and extends to the
last date, with only a single line on the chart. What I would like to
see is a chart that is a single year in length, but with multiple years
shown on top of one another.This is what the chart looks like now when
spanning multiple years. One single line.This is the option I would like
to have, one line per year. This makes it easier to see the year over
Even though SiteCatalyst is the more powerful, preferred web analytics
solution, the HBX tool is still a decent tool. There is no reason to
completely pull the plug on it. Maybe strip out a few of the features to
make it a bit simpler of a tool and then release it as a free web
analytics product so it will compete with Google Analytics and the other
free offerings out there. This may help Omniture gain some of the
overall analytics market share. If a user is using a free product from
In Data Warehouse the variable names should be next to each breakdown
item. Without it you can end up with something that looks like this: In
all other dropdowns you get the actual variable name next to it, like
When a Data Warehouse report fails we are not notified. We have to check
the Request Manager at random times to try to see if it is still
processing or if it failed. And when it did fail, we are not told why. A
better error message in the UI (and sent in an email) would be useful.
Also an automatic resubmit of the report if the error was not due to
something on my end would be good. I obviously want the report, so I
should not have to resubmit it myself.
For some metrics there is a small question mark that appears next to
them that gives a description of that metric. This should be an option
when creating a Calculated Metric. We should be able to give a
description to exactly what the new metric is. This also may be useful
to describe events when used as metrics in reports.For some metrics
there is a small question mark that appears next to them that gives a
description of that metric. This should be an option when creating a
Calculated Metric. ...
When generating a new s_code file, there should be options to add in
some custom elements. I should be able to just click a check box and
have the Media Module added to the code. This could be expanded to to
include some of the 'Omniture approved' plug-ins. For example I could
click a button saying I want the Time Parting plug-in, and then which
props/eVars I want to use with it. Then when the s_code file is
generated the plug-in is added and those variables are now enabled and
When a s_code file is generated from the admin console, the
s.linkDownloadFileTypes variable is populated
when Client Care generates the file, that line
It should be the same no matter who generates the file. There should
also be the Open Office file types included.
In every image request the time value is being passed in (t=). This
should eliminate the need for the Time Parting plug-in. There should be
a way to take this variable and parse it out a bit and get the same
information that the plug-in provided.