You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In specific cases, dashboard developers may want to add an alias to the time dimension being used in a dashboard and include this information as a header in the dashboard. For example, in the case of cohort analysis, a different time field may be used (e.g. date_first_order) but the dashboard developer may want to convey to consumers that the charts / time series represents different cohorts and that revenue metrics (such as Total Revenue or Total Customers) are not necessarily dropping drastically (instead representing more recent cohorts). In this case, they may want to add a header to the dashboard, such as "First Purchase Date", so the analysts under what the different time ranges represents.
For example, something like the following may be sufficient:
In this particular case, the customer would want to label it this way because all our reports use a different order_date as the time value (but this cohort analysis dashboard would use date_first_order). Therefore, the dashboard developer would want to make it clear to consumers / analysts that this represents the customer's first purchase date.
The text was updated successfully, but these errors were encountered:
AndrewRTsao
changed the title
Ability to add an alias or label to available_time_range
Ability to add a header in the dashboard for the time dimension being used
May 9, 2024
In specific cases, dashboard developers may want to add an alias to the time dimension being used in a dashboard and include this information as a header in the dashboard. For example, in the case of cohort analysis, a different time field may be used (e.g.
date_first_order
) but the dashboard developer may want to convey to consumers that the charts / time series represents different cohorts and that revenue metrics (such asTotal Revenue
orTotal Customers
) are not necessarily dropping drastically (instead representing more recent cohorts). In this case, they may want to add a header to the dashboard, such as "First Purchase Date", so the analysts under what the different time ranges represents.For example, something like the following may be sufficient:
In this particular case, the customer would want to label it this way because all our reports use a different
order_date
as the time value (but this cohort analysis dashboard would usedate_first_order
). Therefore, the dashboard developer would want to make it clear to consumers / analysts that this represents the customer's first purchase date.The text was updated successfully, but these errors were encountered: