Add date and time dimensions in Data Warehouse reports

[#1]

Description - Add date and time dimensions in Data Warehouse reports

Why is this feature important to you - Because most of the exported reports related to user interactions within digital channels, or even data from Adobe Target generally need a Date and Time for data analysis to be more complete.

How would you like the feature to work - Date and Time dimensions appear in the "Items" > "Breakdowns" > "Standard" section to add to reports.

Current Behaviour - These dimensions don't exist.

[#2]

Granularity should do this... unless you need down-to-the-second time stamps?

[#3]

Right now we can get down the most is by 'hourly'. Yes, if we have date and time in the breakdown that would help some of the analysis reports.

[#4]

Since you are doing a CSV export... I know this isn't ideal, but you could always track a timestamp into an eVar... while this will be text in Worksace, once it's exported to CSV you could process the value as a time stamp?

At least until (or if) this idea is considered...

Raw Data Feeds DO already contain the timestamp data, but you do have to do a lot processing to ensure that excluded hits and other rules are run to match the data you pull in Adobe... 

[#5]

@Jennifer_Dungan : Do we have Seconds as Dimensions, I can see only Hour and Minute. Also Can you share how to export data as RAW Data Feeds, I can only see dimensions value not metrics? 

[#6]

Unfortunately, Adobe only processes down to minutes in their dimensions... if you need to get the exact second you will need to pull it from the Raw Data exports (which have the actual hit timestamp).

Raw Data Feeds can be set up by going to Admin > Data Feeds... and they work quite differently than other places.

The available column data isn't just dimension, that is all the possible exportable fields...

ALL metrics are actually provided as a comma separated list of "metric ids".... along with Raw Data, an events.tsv file will be provided showing the mapping. This is in the event_list / post_event_list column.

Event1 is actually id 200.

1 Purchase
2 Product View
10 Cart Open
11 Checkout
12 Cart Add
13 Cart Remove
14 Cart View
20 Campaign View
100 Instance of eVar1
...

199 Instance of eVar100
10000 Instance of eVar101

...

10149 Instance of eVar250
200 Custom Event 1

...

299 Custom Event 100
20100 Custom Event 101

...

20999 Custom Event 1000
500 Instance of clickmappage

...

---

If you are using Raw Data Feeds, you should be deferring to the "post" version of values wherever possible, this is the value you see in Adobe... the value that is used after all the post processing (and make sure you have sufficient delay in the feed to allow the processing to complete).

For more information on the fields, this resource is invaluable...

https://experienceleague.adobe.com/en/docs/analytics/export/analytics-data-feed/data-feed-contents/d...

Also, you will have to manually identify your Users using visid_high and visid_low, and you also need to make sure you are taking the exclude_hit logic into account (as the raw data includes everything)

[#7]

@Jennifer_Dungan : Thanks for sharing the info. I'll follow the same.