Adobe Analytics

Currently Search Keyword is not available in processing rules as a variable. (probably because the processing that creates it is after the processing rules stage) However, it would be really useful if Adobe could make this available for processing rules. The only way to get at this in processing rules is to try and look for the referring URL query string parameter which is difficult because different search engines use different parameters :-(

In Discover I want to create 2x trends of visitors who meet the following conditions 1) A Visitor where visit = 3 or more per individual month. The only way I can achieve this is to run a report for each indvidual month. Which is not too bad. 2) A Visitor where visit = 3 or more per individual day. To achieve this I would have to run a report for every individual day.  So I would like some kind of construct in segment builder where I could bind a segment rule to a day, week, month or selected time period. So the rule above might look something like.  1) A Visitor Container - Where Visit = 3 or More (per month) 2) A Visitor Container - Where Visit = 3 or More (per day) The end result is a trended graph where each month or day only shows visitors who visit 3 times or more in each specific day and month on the graph.

Hi,the search engine recognition is currently missing Baidu's biggest competitor:so.360.cn (q=)www.so.com (q=)Please add.More missing search engines can be found here:http://ideas.omniture.com/t5/Adobe-Idea-Exchange-for-Omniture/Add-MS-open-search-site-engi ne-www-so-cl-to-search-reports/idi-p/7177http://ideas.omniture.com/t5/Adobe-Idea-Exchange-for-Omniture/Search-Engines-missing-as-no t-in-the-list-of-recognised-search/idi-p/2735so longnic

When the new specific v15 video reporting is configured, it is not possible to breakdown video reports by mobile nor is it possible to add video metrics to the mobile reports in SiteCatalyst. Please make this type of reporting possible. 

In discover I can create a segment based on a visitor container where visits = 3 or more. In SiteCatalyst I only have visit number which is not the same as visit. I would like to build loyality segements based off the visit metric. This allows for dashboarding of this data etc.

We need more options for reporting by week in the date presets. In addition to Last 2,3 and 4 weeks for the short time-frames and last 53 weeks for the long time-frames how about adding last 12 and last 24 weeks?

For all those who have migrated over to SiteCatalyst 15, this message might be useful at first.  I design dashboards for a dozens of stakeholders who have no access to Omniture and won't understand this warning: "Data for this report suite is processed by a previous data platform that may not support certain". It matters to me and I know that in this particular instance this is not an issue, I wish I could remove it from Omniture as opposed to having to fiddle with it on Acrobat Pro. Please make this message optional.

What about the ability to create a "virtual" report suite by admins? This would be a segment of a real report suite and would allow admins to handle user management etc. the same way as for real suites and the user would easily access their slice of data.e.g. you have a single suite for your site but this covers 5 countries who just care about their own stats. Creating 5 virtual suites and limit the users to it should ease their work.

The only reason we use variable maps are to add context to what/where/whay for each of the variables we use. If we could add that context to the interface, it would do away with a duplication step that is often lost, outdated and unusable for future admins to use. The implications of this go far beyond admins. This would help ClientCare, for example, in their attempts to help diagnose issues. If they have context into the intended use of a variable, then they can better help to troubleshoot related issues. Future engagements would also benefit in similar fashion by giving the often newly introduced consultant some background on the implementation.

The AMA refers to the number of viewers tuned in to the average minute of a video. Average minute audience (AMA) – part of BBM’s television ratings system, this provides information on the average number of viewers in this time period.

Making a default report that will show Geo Segmentation Countries' performances (visits, orders, bounce rate, time spent metrics...) would be perfect. I want to see how many visitors come from, how many orders are done, what are the bounce rates for each country etc... in the same report.

KB articles should list Date Created and Related Product(s).  Currently, there is no date and no list of relevant products in the KB articles.  So we don't know if an article is 7 days old or 7 years old.  And some articles don't mention any product, so it's difficult to know which products are relevant. With the addition of these fields, we could then filter on the product of interest and/or on a date range when searching for KB articles. In fact, it would also be useful to have a version field.  Then we could tell if an article was written, for example, for SiteCatalyst 14 or 15.

VISTA rules currently only have access to adjust pageview level items based on Adobe variables.Wouldn't it be great if they could access visit-level data?For example, if a user has called event1 and event2 in the session, then set eVar3.Wouldn't it be great if they could access parameters OTHER than Adobe variable? For example, if we've accidentally put values in the image request that are not recognized by Adobe, we should be able to use a VISTA rule to fix them. The image request may have eVar1=hello instead of v1=hello as the processing engine expects. Unfortunately, VISTA rules can't see this.

A newer feature of events (although not documented in the help section or KB) is that you can give a counter event a value greater than one really easy without having to use the products variable.  For example, s.events="event1=5".  The only problem is that it cannot have a decimal value, and setting s.products with it just seems silly (although I guess it does work).  We should be able to set a decimal value for any event.  So s.events="1.564".  This would be great for many reasons: 1. For a retail site, capture the shipping and tax for the entire order and not have to create an empty product or a "tax" or "shipping" product and set the value there.2. For videos, we want to capture the GB delivered.  This value is always a decimal value less than 1 (.0056 for example).  Setting it with the products variable is just ugly and messy. It can be easier to set these variables, and it should.  And they should support decimal values, although I'm not sure how many decimal values current numer

Hi, Id like a feature that somehow allows you to see which sites have been added recently.Say for example you run a campaign or a A/B Testing and add some new pages to your website.For me as an analyst it would be very conveniant to quickly see which sites have been added and if they are mapped correctly. Regards IronMan

Here are some things that don't copy currently :-1) Custom Menu Structure2) Custom Reports3) Custom Bot Rules4) Admin Report Suite Level Segmentation5) Video Reporting SettingsBetter still perhaps you could provide a bunch of check boxes so we can choose what get's copied over from the original report suite

Standard metrics such as "revenue" and "orders" contain a convenient [?] icon in reports that displays the metric definition as shown in the example below...  ...it would be great if we could add our own metric definitions to calculated metrics and custom events like events 33, 34, and 39 shown above.

My favorite feature of Numeric 2 SAINT classifications is that they can have different values for different time periods and multiple rows per key. It would be great if that functionality could be used for text, date-enabled classifications too since data-enabled only gets you as far as a yes/no type classification.

Microsoft launched an open search site www.so.clwhile there are some social elements to it, it is mainly a search engine, with keywords in the query string parametercurrently traffic from www.so.cl appears as external sites.Is it possible to instead list this instead as a search engine along with the keywords searched

With V15, you launched Page Views available on conversion metrics.  I want this same metric available on conversion metrios in report builder.

Currently, there is a limitation of 100-characters in SAINT's ability to classify SiteCatalyst data. Whaterver exceeds 100 characters cannot be classified and, thus, makes the classification feature unuseful at all, as lots of data are missed.Since there are a lot of products in different industries with names longer than 100-characters, I think it would be useful for Sitecatalyst usage to extend the limit to at least 150-200 characters.Thank you!

In this day and age it's perfectly possible to replicate Discover interface in to a web application. It would be great to see Discover functionality sit along side normal SiteCatalyst functionality in a single web interface. Adobe could still offer the products seperately but maybe a standard SiteCatalyst interface and a SiteCatalyst + Discover Interface with the following benefits :-Some advantages features that this would enable :- Ability to include discover reports and data point in standard SiteCatalyst dashboards. I think one of the biggest pain points today is the differeniation of tools and locations that provide data to the business. The lack of dashboarding support in Discover is a real issue.Ability to trend and compare more than one segment on a graph. This feature works really well in Google Analytics and is one of the most powerful analysis features of Discover but it's a real shame we can't do this in SiteCatalyst and dashboard the resultsSegment's would be by default in

When using the search filter to find an exact value that starts with a hyphen, i.e. "- MySite.com", SiteCatalyst interprets the hyphen as an operator and returns no results. Since the quotations are supposed to denote an exact phrase, it should not be interpreted as "-/minus 'MySite.com'". This also happens when trying to specify the value for a segment as a workaround.

I love the ability to perform in depth analysis in Discover however I frequently finding myself trying to switch back and forth between projects.  It would be very helpful to be able to open multiple "windows" to view projects simultaneously (similar to having multiple workspaces open)

Use Saints to upload our own naming convention or allow for a more friendly naming convention for the timezone report. EDT , PDT, PST, etc, is more friendly than GMT+0500