Adobe captures a session timestamp.
That timestamp, at present, is not surfaceable in processing rules. Understandable becauuse processing rules do not have regex or parsing capabilities.
However, the atoms of that session timestamp, and associated metadata, are very valuable to a researcher.
"As a researcher, I want to cross the HH:MM with a video name so that I can calculate an AMA."
"As a researcher, I want to cross the day of the week with a pagename so that I can compare Monday traffic patterns to Sunday traffic patterns in aggregate."
"As a researcher, I want to cross HH:MM with timezone with a video so that I can understand how timeparting and timezones affects AMA."
If specific components of the timestamp could be surfaced in processing rules, multiple timeparting features could be enabled. (The implementor would assign that data to specific variables to taste).
A concrete example:
a.hour : expected value 00, 01, 02, 03 ... 22, 23
a.minute: expected value 00...59
a.second: expected value 00...59
a.twentyfourhourtime: expected value 0000....2359
a.dayofweek: expected value monday, tuesday, wednesday, thursday, friday, saturday, sunday
a.weekdayorweekend: expected value weekday, weekend
a.timezoneoffsetgmt: expected value -12.....0.....+16
a.timezoneoffsetutc: expected value -12.....0....+16
IF such technical debt is undesirable, the most straight forward three features:
1. Enable read-only priveledges to the session timestamp.
2. Enable read-only priveledges to the timezone.
3. Enable regex in processing rules.