Create a proper Hour dimension for Web (Native already has it)

I totally agree with this.  We've paid for a VISTA rule to allow us to create a dimension that enables us to do this.

It definitely feels like this is funcationality that should come straight out of the box.

Similar for 'Month' . Adobe has added Month dimension meaning customers do not have to implement/capture however this captures  the month AND year .. which reduces functionality

eg.

1. As with above example I can't have 'Month' as the breakdown dimension and then use the 'new' compare time periods functionality to compare month traffic YOY .. this concept would apply to other Date dimensions offered out of the box.

2. Creating segments .. we capture hour of day, day of week in addition to Adobe dimensions which allows for creating segments too (as well as comparisons similar to above example) eg. visits duing hours 8 or 9 .. or visitors during weekend etc.  But would make sense if this functionality was offered 'out of the box' or without the need to duplicate recording.

Whilst it 'may' be necessary for Adobe to capre the time/date metrics as they do, so my slightly alternative suggestion would be they classify and make appropriate classifications available ;-)

We want to add rolling date ranges in segments; there are a ton of great use cases that would be solved by this. Either way, we'll keep an eye on this idea for votes and comments and make sure we're solving your need as we go. 

^^^^^^^^^^^^^^^^^^^^^^^^

THAT! Please!!!

Can you add Hour of Day (00, 01, 02, 03, 04, etc) as a dimension in Analysis Workspace (and other tools) ASAP?  Right now all you have is 'Hour' which is bound to a date.  this makes it very difficult to compare day over day by hour.

@benjamingaines, any updates on this feature enhancement? Hour is still bound by date in Workspace.

These are all great points. Some thoughts:

1. For comparing hours of day across days, there's currently a bug (or perhaps bad design) related to the existence of the date in the rows when showing hour (as you pointed out). The result is that you can't really compare a single hour across days. That should be fixed in an upcoming release. 

2. Good point about 25 items in a graph. I'll send this over to our engineering team to review and hopefully get that increased.

3. This might be coming soon. We want to add rolling date ranges in segments; there are a ton of great use cases that would be solved by this. Either way, we'll keep an eye on this idea for votes and comments and make sure we're solving your need as we go. 

also - it would be nice to be able to a comparison of 'hour to date'  So if I am comparing today vs. yesterday i would have the ability to apply a segment to yesterday that matches the data available for today.

Example:

Current Date Time: 9/23/15 10am

Current Orders per Visit:: 6%

Yesterday Orders per Visit: 2%

Yesterday Orders per Visit through 10am: 7%

Being able to compare current conversion rates by time of day would be super helpful and cause people to pay attention in realtime vs. having to wait a day. (we can obvisouly visualize in other ways but it would be nice to have something out of the box)

again - apologies if this already exists.

@benjamingaines When can we expect this to be released?

@jer @viclin: This should be available on November 10. Note that this will NOT give you hour as a dimension to be used anywhere. It will let you compare a specific hour against the same hour on another day. For hour as a dimensions, we continue to recommend a Time Parting solution using JavaScript. 

per a Ben Gaines suggestion a while back:

1. I have the standard time of day eVar (10:23|Friday) which I classify into different time dimensions.

2. I then create segments by hour of day and label them 00, 01, 02, 03...

3. I then drag these segments into an analysis workspace table to compare metrics.

4.  analysis workspace allows you sort segments.

this works well as a good hack.  however, everytime I change a metric, segement, or dimension in the report, the segments will resort highest to lowest. 

as an addon feature - it would be great to be able to lock the components in a table so they do not resort when you change a comparison component.