For the life of me, I cannot think of a use case where Date Ranges (purple) are useful in a segment. I don't mean the (orange) dimensions like Day or Month. Would love to hear any ways in which others have used them.
And if not, I suggest removing them from the Segment Creator UI, as users often get confused.
Thanks for your responses, @jeff_bloomer and @Andrey_Osadchuk . I understand how Date Ranges can by used in Segments. However, I have not encountered any real world situations where I've seen them being useful. Especially since applying a segment in one freeform table will change the whole panel's date applied date range, not to mention the ambiguous naming, their use within segments generally leads to end user confusion. To your example, I typically recommend users apply the dynamic date range directly to their table without wrapping it in a segment.
This has been my experience, however I would love to hear of any ingenious applications where people have used Date Ranges in Segments.
Consider a scenario when you want to have a metric that returns number of visits for the last 7 days. This requires a metric with a segment. The metric will work regardless of what date range is set in the panel.
A step forward would be to have a metric that returns by how much the traffic changed last week vs a prior week (MoM, YoY, etc.)
@Kanno_Kuramoto, Honestly, it really all comes down to how granular you want to have your components in your report. However, having a date range in a segment also makes it immediately handy. For instance, say you have it set to last week. Regardless of the date range set in your report, the segment you just used just applied an automatic date range along with an additional filter without you flipping any additional filters. You can think of segments as your utility belt of shortcuts. In Adobe Analytics Workspace, you don't get macros, so instead, you can use Segments and calculated metrics as your alternative. Make sense?