Someone marked this as "Implemented", but I can't tell who or when. Is this because of "SAINT bernard", or is there other support (and if so, could someone paste a link to that information?)

9.1K

Re: Make scheduled Data Warehouse requests editable. - Adobe Analytics

I don't think it's correct to mark this one as "Already Offered". Can it be reconsidered, or should I create a new item for this? I run into an issue quite often where a DW report that's been scheduled and running for a long time needs a column added to/deleted from it. In order to do that, I have to click "Duplicate" on the existing report, make the change and then fill in the following all over again: The filename of the report.The subject line of the email.The recipients and/or FTP informatio...

5.6K

Re: SiteCatalyst Timestamp Improvement - Adobe Analytics

I couldn't agree more! Suggestion #2 is probably more complicated to implement, but couldn't you do #1? Almost all of our report suites need to be timestamp enabled, which means that every time I create a new one, I have to contact ClientCare to turn on timestamps before I can use it.

2.9K

Re: Make scheduled Data Warehouse requests editable. - Adobe Analytics

You can change the schedule, or even the recipients, but you can't edit the report. To do that, you have to "duplicate" it, make the changes you want and then set up the recipients and scheduling all over again.

5.6K

Re: Automatic, rule-based SAINT classifications based on specific criteria - Adobe Analytics

This is considered a "Top Idea" and it's now been "Under Review" for 2 and a half years! Come on Adobe!

7.4K

Re: Update SAINT templates to latest version when exporting - Adobe Analytics

It's really amazing how long this has gone on. (And how annoying it is to deal with.) This is one of those cases where the problem should be considered a bug, not an "idea".

1.3K

Re: Automatic, rule-based SAINT classifications based on specific criteria - Adobe Analytics

This has been "under review" for a year and a half now. Is there still some chance it will happen and/or will it only happen in SiteCatalyst 15?

6.8K

Re: Allow properties to be added to correlations without losing all historically correlated data - Adobe Analytics

A lot of nice things are available in SiteCatalyst 15. Unfortunately, we use mostly Data Insertion to populate reports, and SC 15 apparently doesn't support that yet.

1.2K

Default to more logical year when only two digits provided - Adobe Analytics

In the SiteCatalyst date range window, if you type in a date in the format DD/MM/YY, it defaults to the year 1000, so 1/1/09 becomes 01/01/1009. I realize that we should all know better than to type in only 2-digits for a year, but it seems to me there are two different acceptable behaviors when we do: -- Require 4-digits for years (not my preference, but at least it would be clear what's needed)-- Use some simple logic to default to something in the realm of possible years. Most websites and to...

407

Provide dates, versions numbers, list of changes in Code Manager - Adobe Analytics

In the Code Manager, there's currently no way to tell if there are new versions of libraries short of downloading the same library again and doing a binary compare. You could make this easier for us in several ways, but at the very minimum providing the date of the most recent update of each library would be a huge help. Beyond that: -- Associate version numbers with libraries-- List the changes implemented with each version-- Allow us to sign up for notifications when a library is updated

401

Re: When filtering out data, please remove related page views from new total page views - Adobe Analytics

I couldn't agree more. I'm surprised this "idea" hasn't gotten more promotions. It really just seems like a bug to me. The subtotal in EVERY report should be the sum of visible items in that report. If items are filtered out, they shouldn't be considered in the total.

2.2K

Re: Remove unspecified's from correlation reports - Adobe Analytics

Yes, I noticed that, too. So, no filtering and I'm back to having to explain the meaning of "unspecified" to everyone.

2.7K

Allow SAINT classifications of geo-segmentation properties - Adobe Analytics

I was disappointed to find that I can't use SAINT to group geo-segmentation values. We work with clients who would like to see their metrics grouped geographically the way they group countries, by their sales regions. This sounds like a perfect use of SAINT, and yet it's not supported.

2.4K

Re: Remove unspecified's from correlation reports - Adobe Analytics

Make it an option, then. I agree with this post. I'm constantly creating custom reports that filter out the "Unspecified" values in these reports (which also messes up the totals), or having to explain to people looking at the correlated reports that 90% of the usage is "Unspecified" because that particular property isn't relevant in the case they're looking at.

2.7K

Re: Product selection on login - Adobe Experience Cloud

I agree with rindsay. I get tired of telling users/clients I support on SiteCatalyst to "click the green button at the top of the wheel". Give them the option of skipping that step, or admins the option of setting users up so they skip that step.

8.7K

Re: Add Ranked visualisation of Countries Report to Dashboards - Adobe Analytics

This used to work! In fact, I 'm pretty sure I still have some users I set up ranked country reports for on their dashboards. It stopped working several months ago.

1.2K

Re: better mobile user agent tracking - Adobe Analytics

I agree. I get the distinct impression that we're testing with more devices than Omniture is. We have usage that doesn't show up at all in the Mobile/Devices reports until Omniture finally gets mappings for those user agents in.

829

Re: Allow trended versions of correlated reports - Adobe Analytics

This post may be a duplicate of this one: http://ideas.omniture.com/t5/Omniture-Idea-Exchange/Support-Trending-Subrelation-Breakdown s/idi-p/294 I'm not sure if the term "subrelation" only refers to eVars, or if it refers to sProps/traffic vars, too. In any case, it's a similar idea. Allow data to be broken down AND trended.

2.0K

Re: Ability to remove, filter out, or change bad data - Adobe Analytics

I agree! This is probably my #1 complaint about SiteCatalyst. It's especially true if you're using Data Insertion to get data to SiteCatalyst. It can be downright scary to implement anything new, since anything sent is there forever, warts and all.

1.0K

Allow trended versions of correlated reports - Adobe Analytics

As soon as I correlate one property to another, the option of trended reports goes away. Why? It would be so useful to be able to narrow the results and still show the data over time.

2.0K

Preserve custom report names when reports are downloaded or emailed - Adobe Analytics

If I create a custom report based on, say, the Page Report and call it "My Custom Pages Report", whenever I select it in SiteCatalyst, it shows the custom name, but if I download or email that report, the resulting report will be called "Pages Report" and the default filename/subject line will be "Pages Report".

407

Use customized menu text in the reports - Adobe Analytics

If I use Customize Menus in the Admin Console, those names don't carry over to the reports, so if I rename "Pages" to "Usage Details", for instance, the report that's produced when you click the "Usage Details" menu is still called "Pages Report".

421

Allow properties to be added to correlations without losing all historically correlated data - Adobe Analytics

I often run into a situation where I'd like to add another property to an existing 5-item or 20-item data correlation. Unfortunately, doing so causes all previously correlated data to be deleted. This is a huge limitation in my opinion. Why not allow new properties to be added, and only correlate those properties to the others from that day forward, but allow previous correlation data to be preserved? Similarly, because of these arbitrary limitations of 5 and 20, I have occasionally wanted to de...

1.2K

Likes given to

User

Count

Likes from

User

Count

Guidelines

Cookie preferences