counterweight/data-dwh-dbt-project
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
data-dwh-dbt-project/models/intermediate/cross/int_mtd_aggregated_metrics.sql

260 lines
9.8 KiB
MySQL
Raw Normal View History

Merged PR 2003: Business KPIs first draft This PR aims to provide a first draft for business KPIs, at this stage **quite minimal**. It mostly contains a MTD and Monthly display approach. No dimensions are created. The models created are: - **int_dates_mtd**: mainly it reads from int_dates to retrieve those days needed for a MTD/monthly display - **int_core__mtd_booking_metrics**: it contains the booking metrics, ending in a format of date|value|value last year|increment --> here we could add, in the future, additional metrics from other sources (ex: guest journey, etc) - **int_core__mtd_aggregated_metrics**: it transforms the data coming from the different mtd intermediate sources to be easily displayed in the dashboard. This is a good candidate for macros :) - **core__mtd_aggregated_metrics**: copy-paste of the its int_core version, including a bit of model documentation The dashboard is functional but in another PR. I can show you how it looks like at the moment you are going to check the PR Related work items: #17214
2024-06-11 15:45:57 +00:00
{% set metrics = [
Merged PR 2053: Added number_format category in mtd_aggregated_metrics Added number_format category in mtd_aggregated_metrics Related work items: #17458
2024-06-17 14:59:01 +00:00
{
"order_by": 1,
"metric": "Created Bookings",
"value": "created_bookings",
"previous_year_value": "previous_year_created_bookings",
"relative_increment": "relative_increment_created_bookings",
"number_format": "integer",
},
{
"order_by": 2,
Merged PR 2068: Adding cancelled bookings metric Adding cancelled bookings metric based on the feedback of the tech team. Mainly, the date of a cancelled booking can be considered as the `updated_date_utc` for those bookings with status cancelled, as it's a terminal state and no additional steps should follow. I also took the opportunity to update: - The order on the `int_core__mtd_aggregated_metrics`, so it matches the one in the Notion page for the 1st batch, freeing already the space for the order_by numbers for missing metrics - Make acronyms of alias in the `main_kpi` subquery in `int_core__mtd_booking_metrics` slightly more clear - Remove empty line at the end of the file in `int_core__mtd_booking_metrics` Keep in mind that the cancelled bookings metric will be directly available in the dashboard once this PR is approved and DWH re-runs. Related work items: #17310
2024-06-18 14:58:55 +00:00
"metric": "Cancelled Bookings",
"value": "cancelled_bookings",
"previous_year_value": "previous_year_cancelled_bookings",
"relative_increment": "relative_increment_cancelled_bookings",
Merged PR 2053: Added number_format category in mtd_aggregated_metrics Added number_format category in mtd_aggregated_metrics Related work items: #17458
2024-06-17 14:59:01 +00:00
"number_format": "integer",
},
{
"order_by": 3,
Merged PR 2068: Adding cancelled bookings metric Adding cancelled bookings metric based on the feedback of the tech team. Mainly, the date of a cancelled booking can be considered as the `updated_date_utc` for those bookings with status cancelled, as it's a terminal state and no additional steps should follow. I also took the opportunity to update: - The order on the `int_core__mtd_aggregated_metrics`, so it matches the one in the Notion page for the 1st batch, freeing already the space for the order_by numbers for missing metrics - Make acronyms of alias in the `main_kpi` subquery in `int_core__mtd_booking_metrics` slightly more clear - Remove empty line at the end of the file in `int_core__mtd_booking_metrics` Keep in mind that the cancelled bookings metric will be directly available in the dashboard once this PR is approved and DWH re-runs. Related work items: #17310
2024-06-18 14:58:55 +00:00
"metric": "Checkout Bookings",
"value": "check_out_bookings",
"previous_year_value": "previous_year_check_out_bookings",
"relative_increment": "relative_increment_check_out_bookings",
Merged PR 2053: Added number_format category in mtd_aggregated_metrics Added number_format category in mtd_aggregated_metrics Related work items: #17458
2024-06-17 14:59:01 +00:00
"number_format": "integer",
},
Merged PR 2068: Adding cancelled bookings metric Adding cancelled bookings metric based on the feedback of the tech team. Mainly, the date of a cancelled booking can be considered as the `updated_date_utc` for those bookings with status cancelled, as it's a terminal state and no additional steps should follow. I also took the opportunity to update: - The order on the `int_core__mtd_aggregated_metrics`, so it matches the one in the Notion page for the 1st batch, freeing already the space for the order_by numbers for missing metrics - Make acronyms of alias in the `main_kpi` subquery in `int_core__mtd_booking_metrics` slightly more clear - Remove empty line at the end of the file in `int_core__mtd_booking_metrics` Keep in mind that the cancelled bookings metric will be directly available in the dashboard once this PR is approved and DWH re-runs. Related work items: #17310
2024-06-18 14:58:55 +00:00
{
Merged PR 2053: Added number_format category in mtd_aggregated_metrics Added number_format category in mtd_aggregated_metrics Related work items: #17458
2024-06-17 14:59:01 +00:00
"order_by": 4,
Merged PR 2068: Adding cancelled bookings metric Adding cancelled bookings metric based on the feedback of the tech team. Mainly, the date of a cancelled booking can be considered as the `updated_date_utc` for those bookings with status cancelled, as it's a terminal state and no additional steps should follow. I also took the opportunity to update: - The order on the `int_core__mtd_aggregated_metrics`, so it matches the one in the Notion page for the 1st batch, freeing already the space for the order_by numbers for missing metrics - Make acronyms of alias in the `main_kpi` subquery in `int_core__mtd_booking_metrics` slightly more clear - Remove empty line at the end of the file in `int_core__mtd_booking_metrics` Keep in mind that the cancelled bookings metric will be directly available in the dashboard once this PR is approved and DWH re-runs. Related work items: #17310
2024-06-18 14:58:55 +00:00
"metric": "Guest Journey Created",
"value": "created_guest_journeys",
"previous_year_value": "previous_year_created_guest_journeys",
"relative_increment": "relative_increment_created_guest_journeys",
Merged PR 2053: Added number_format category in mtd_aggregated_metrics Added number_format category in mtd_aggregated_metrics Related work items: #17458
2024-06-17 14:59:01 +00:00
"number_format": "integer",
},
{
"order_by": 5,
Merged PR 2068: Adding cancelled bookings metric Adding cancelled bookings metric based on the feedback of the tech team. Mainly, the date of a cancelled booking can be considered as the `updated_date_utc` for those bookings with status cancelled, as it's a terminal state and no additional steps should follow. I also took the opportunity to update: - The order on the `int_core__mtd_aggregated_metrics`, so it matches the one in the Notion page for the 1st batch, freeing already the space for the order_by numbers for missing metrics - Make acronyms of alias in the `main_kpi` subquery in `int_core__mtd_booking_metrics` slightly more clear - Remove empty line at the end of the file in `int_core__mtd_booking_metrics` Keep in mind that the cancelled bookings metric will be directly available in the dashboard once this PR is approved and DWH re-runs. Related work items: #17310
2024-06-18 14:58:55 +00:00
"metric": "Guest Journey Started",
"value": "started_guest_journeys",
"previous_year_value": "previous_year_started_guest_journeys",
"relative_increment": "relative_increment_started_guest_journeys",
Merged PR 2053: Added number_format category in mtd_aggregated_metrics Added number_format category in mtd_aggregated_metrics Related work items: #17458
2024-06-17 14:59:01 +00:00
"number_format": "integer",
},
{
"order_by": 6,
Merged PR 2068: Adding cancelled bookings metric Adding cancelled bookings metric based on the feedback of the tech team. Mainly, the date of a cancelled booking can be considered as the `updated_date_utc` for those bookings with status cancelled, as it's a terminal state and no additional steps should follow. I also took the opportunity to update: - The order on the `int_core__mtd_aggregated_metrics`, so it matches the one in the Notion page for the 1st batch, freeing already the space for the order_by numbers for missing metrics - Make acronyms of alias in the `main_kpi` subquery in `int_core__mtd_booking_metrics` slightly more clear - Remove empty line at the end of the file in `int_core__mtd_booking_metrics` Keep in mind that the cancelled bookings metric will be directly available in the dashboard once this PR is approved and DWH re-runs. Related work items: #17310
2024-06-18 14:58:55 +00:00
"metric": "Guest Journey Completed",
"value": "completed_guest_journeys",
"previous_year_value": "previous_year_completed_guest_journeys",
"relative_increment": "relative_increment_completed_guest_journeys",
"number_format": "integer",
},
{
Merged PR 2107: Adds host lifecycle metrics into biz kpis This PR closes the first draft of the first batch of business kpis. Host logic has changed to be applied at deal id level. It's mostly an adapted copy-paste from the accommodation counterpart, specifically: - `int_core__mtd_deal_lifecycle`: computes the historic deal lifecycle. One line for each deal and MTD date. **Important**: _Not all hosts have a deal set. This will need a data quality report for business teams to fix_ - `int_core__mtd_deal_metrics`: computes the aggregation at MTD date level of the metrics per lifecycle state and activity state Additionally, this PR changes: - `int_core__mtd_aggregated_metrics`: it includes the new 3 deal metrics and changes the source of the already existing 3 deal metrics from `mtd_booking_metrics` to the new `mtd_deal_metrics` - `int_core__mtd_booking_metrics`: removes all code needed to compute the remaining deal metrics, speeding it up considerably. After this PR, the mtd models run (locally) at the following speed: - `int_core__mtd_accommodation_lifecycle`: 47 sec - `int_core__mtd_deal_lifecycle`: 3 sec - `int_core__mtd_accommodation_metrics`: 5 sec - `int_core__mtd_deal_metrics`: < 1 sec - `int_core__mtd_booking_metrics`: 8 sec (quite a reduction) - `int_core__mtd_guest_journey_metrics`: 5 sec - `int_core__mtd_aggregated_metrics` and `core__mtd_aggregated_metrics`: < 1 sec Related work items: #17312
2024-06-25 12:20:59 +00:00
"order_by": 7,
Merged PR 2257: Expose guest revenue and guest journey payment metrics This PR aims to expose the new metrics to the business KPIs report. The new metrics exposed are, for the global and the by deal view: - Guest Revenue - Guest Revenue per Guest Journey Completed - Guest Revenue per Guest Journey with Payment - Guest Payments - Guest Payments per Guest Journey Completed - Guest Payments per Guest Journey with Payment - Guest Journey with Payment - Guest Journey Payment Rate Changes: - Silly change on the naming in the by deal view of `payment_rate_guest_journey` to be consistent with the global view. - Silly change that I miss some GJ payment metric for the view by deal id. - Added a new number format called `currency_gbp` - only for monetary metrics, available in the schema files - Usual procedure to publish metrics: for global metrics, add them in the `int_mtd_aggregated_metrics`. I also changed the order of display. - **Important**: to avoid displaying revenue figures until Xero invoicing is handled, I created a macro called `is_date_before_previous_month` that is called in the reporting equivalent models: `mtd_aggregated_metrics` in the where section and in the `monthly_aggregated_metrics_history_by_deal` as a case-when. This should allow to expose all new metrics, and enable the publishing of a new update of the business kpis! Related work items: #18107
2024-07-10 14:17:05 +00:00
"metric": "Guest Journey with Payment",
"value": "paid_guest_journeys",
"previous_year_value": "previous_year_paid_guest_journeys",
"relative_increment": "relative_increment_paid_guest_journeys",
"number_format": "integer",
},
{
"order_by": 8,
Merged PR 2107: Adds host lifecycle metrics into biz kpis This PR closes the first draft of the first batch of business kpis. Host logic has changed to be applied at deal id level. It's mostly an adapted copy-paste from the accommodation counterpart, specifically: - `int_core__mtd_deal_lifecycle`: computes the historic deal lifecycle. One line for each deal and MTD date. **Important**: _Not all hosts have a deal set. This will need a data quality report for business teams to fix_ - `int_core__mtd_deal_metrics`: computes the aggregation at MTD date level of the metrics per lifecycle state and activity state Additionally, this PR changes: - `int_core__mtd_aggregated_metrics`: it includes the new 3 deal metrics and changes the source of the already existing 3 deal metrics from `mtd_booking_metrics` to the new `mtd_deal_metrics` - `int_core__mtd_booking_metrics`: removes all code needed to compute the remaining deal metrics, speeding it up considerably. After this PR, the mtd models run (locally) at the following speed: - `int_core__mtd_accommodation_lifecycle`: 47 sec - `int_core__mtd_deal_lifecycle`: 3 sec - `int_core__mtd_accommodation_metrics`: 5 sec - `int_core__mtd_deal_metrics`: < 1 sec - `int_core__mtd_booking_metrics`: 8 sec (quite a reduction) - `int_core__mtd_guest_journey_metrics`: 5 sec - `int_core__mtd_aggregated_metrics` and `core__mtd_aggregated_metrics`: < 1 sec Related work items: #17312
2024-06-25 12:20:59 +00:00
"metric": "New Deals",
"value": "new_deals",
"previous_year_value": "previous_year_new_deals",
"relative_increment": "relative_increment_new_deals",
"number_format": "integer",
},
{
Merged PR 2257: Expose guest revenue and guest journey payment metrics This PR aims to expose the new metrics to the business KPIs report. The new metrics exposed are, for the global and the by deal view: - Guest Revenue - Guest Revenue per Guest Journey Completed - Guest Revenue per Guest Journey with Payment - Guest Payments - Guest Payments per Guest Journey Completed - Guest Payments per Guest Journey with Payment - Guest Journey with Payment - Guest Journey Payment Rate Changes: - Silly change on the naming in the by deal view of `payment_rate_guest_journey` to be consistent with the global view. - Silly change that I miss some GJ payment metric for the view by deal id. - Added a new number format called `currency_gbp` - only for monetary metrics, available in the schema files - Usual procedure to publish metrics: for global metrics, add them in the `int_mtd_aggregated_metrics`. I also changed the order of display. - **Important**: to avoid displaying revenue figures until Xero invoicing is handled, I created a macro called `is_date_before_previous_month` that is called in the reporting equivalent models: `mtd_aggregated_metrics` in the where section and in the `monthly_aggregated_metrics_history_by_deal` as a case-when. This should allow to expose all new metrics, and enable the publishing of a new update of the business kpis! Related work items: #18107
2024-07-10 14:17:05 +00:00
"order_by": 9,
Merged PR 2107: Adds host lifecycle metrics into biz kpis This PR closes the first draft of the first batch of business kpis. Host logic has changed to be applied at deal id level. It's mostly an adapted copy-paste from the accommodation counterpart, specifically: - `int_core__mtd_deal_lifecycle`: computes the historic deal lifecycle. One line for each deal and MTD date. **Important**: _Not all hosts have a deal set. This will need a data quality report for business teams to fix_ - `int_core__mtd_deal_metrics`: computes the aggregation at MTD date level of the metrics per lifecycle state and activity state Additionally, this PR changes: - `int_core__mtd_aggregated_metrics`: it includes the new 3 deal metrics and changes the source of the already existing 3 deal metrics from `mtd_booking_metrics` to the new `mtd_deal_metrics` - `int_core__mtd_booking_metrics`: removes all code needed to compute the remaining deal metrics, speeding it up considerably. After this PR, the mtd models run (locally) at the following speed: - `int_core__mtd_accommodation_lifecycle`: 47 sec - `int_core__mtd_deal_lifecycle`: 3 sec - `int_core__mtd_accommodation_metrics`: 5 sec - `int_core__mtd_deal_metrics`: < 1 sec - `int_core__mtd_booking_metrics`: 8 sec (quite a reduction) - `int_core__mtd_guest_journey_metrics`: 5 sec - `int_core__mtd_aggregated_metrics` and `core__mtd_aggregated_metrics`: < 1 sec Related work items: #17312
2024-06-25 12:20:59 +00:00
"metric": "First Time Booked Deals",
"value": "first_time_booked_deals",
"previous_year_value": "previous_year_first_time_booked_deals",
"relative_increment": "relative_increment_first_time_booked_deals",
"number_format": "integer",
},
{
Merged PR 2257: Expose guest revenue and guest journey payment metrics This PR aims to expose the new metrics to the business KPIs report. The new metrics exposed are, for the global and the by deal view: - Guest Revenue - Guest Revenue per Guest Journey Completed - Guest Revenue per Guest Journey with Payment - Guest Payments - Guest Payments per Guest Journey Completed - Guest Payments per Guest Journey with Payment - Guest Journey with Payment - Guest Journey Payment Rate Changes: - Silly change on the naming in the by deal view of `payment_rate_guest_journey` to be consistent with the global view. - Silly change that I miss some GJ payment metric for the view by deal id. - Added a new number format called `currency_gbp` - only for monetary metrics, available in the schema files - Usual procedure to publish metrics: for global metrics, add them in the `int_mtd_aggregated_metrics`. I also changed the order of display. - **Important**: to avoid displaying revenue figures until Xero invoicing is handled, I created a macro called `is_date_before_previous_month` that is called in the reporting equivalent models: `mtd_aggregated_metrics` in the where section and in the `monthly_aggregated_metrics_history_by_deal` as a case-when. This should allow to expose all new metrics, and enable the publishing of a new update of the business kpis! Related work items: #18107
2024-07-10 14:17:05 +00:00
"order_by": 10,
Merged PR 2107: Adds host lifecycle metrics into biz kpis This PR closes the first draft of the first batch of business kpis. Host logic has changed to be applied at deal id level. It's mostly an adapted copy-paste from the accommodation counterpart, specifically: - `int_core__mtd_deal_lifecycle`: computes the historic deal lifecycle. One line for each deal and MTD date. **Important**: _Not all hosts have a deal set. This will need a data quality report for business teams to fix_ - `int_core__mtd_deal_metrics`: computes the aggregation at MTD date level of the metrics per lifecycle state and activity state Additionally, this PR changes: - `int_core__mtd_aggregated_metrics`: it includes the new 3 deal metrics and changes the source of the already existing 3 deal metrics from `mtd_booking_metrics` to the new `mtd_deal_metrics` - `int_core__mtd_booking_metrics`: removes all code needed to compute the remaining deal metrics, speeding it up considerably. After this PR, the mtd models run (locally) at the following speed: - `int_core__mtd_accommodation_lifecycle`: 47 sec - `int_core__mtd_deal_lifecycle`: 3 sec - `int_core__mtd_accommodation_metrics`: 5 sec - `int_core__mtd_deal_metrics`: < 1 sec - `int_core__mtd_booking_metrics`: 8 sec (quite a reduction) - `int_core__mtd_guest_journey_metrics`: 5 sec - `int_core__mtd_aggregated_metrics` and `core__mtd_aggregated_metrics`: < 1 sec Related work items: #17312
2024-06-25 12:20:59 +00:00
"metric": "Deals Booked in Month",
"value": "deals_booked_in_month",
"previous_year_value": "previous_year_deals_booked_in_month",
"relative_increment": "relative_increment_deals_booked_in_month",
Merged PR 2053: Added number_format category in mtd_aggregated_metrics Added number_format category in mtd_aggregated_metrics Related work items: #17458
2024-06-17 14:59:01 +00:00
"number_format": "integer",
},
{
Merged PR 2257: Expose guest revenue and guest journey payment metrics This PR aims to expose the new metrics to the business KPIs report. The new metrics exposed are, for the global and the by deal view: - Guest Revenue - Guest Revenue per Guest Journey Completed - Guest Revenue per Guest Journey with Payment - Guest Payments - Guest Payments per Guest Journey Completed - Guest Payments per Guest Journey with Payment - Guest Journey with Payment - Guest Journey Payment Rate Changes: - Silly change on the naming in the by deal view of `payment_rate_guest_journey` to be consistent with the global view. - Silly change that I miss some GJ payment metric for the view by deal id. - Added a new number format called `currency_gbp` - only for monetary metrics, available in the schema files - Usual procedure to publish metrics: for global metrics, add them in the `int_mtd_aggregated_metrics`. I also changed the order of display. - **Important**: to avoid displaying revenue figures until Xero invoicing is handled, I created a macro called `is_date_before_previous_month` that is called in the reporting equivalent models: `mtd_aggregated_metrics` in the where section and in the `monthly_aggregated_metrics_history_by_deal` as a case-when. This should allow to expose all new metrics, and enable the publishing of a new update of the business kpis! Related work items: #18107
2024-07-10 14:17:05 +00:00
"order_by": 11,
Merged PR 2107: Adds host lifecycle metrics into biz kpis This PR closes the first draft of the first batch of business kpis. Host logic has changed to be applied at deal id level. It's mostly an adapted copy-paste from the accommodation counterpart, specifically: - `int_core__mtd_deal_lifecycle`: computes the historic deal lifecycle. One line for each deal and MTD date. **Important**: _Not all hosts have a deal set. This will need a data quality report for business teams to fix_ - `int_core__mtd_deal_metrics`: computes the aggregation at MTD date level of the metrics per lifecycle state and activity state Additionally, this PR changes: - `int_core__mtd_aggregated_metrics`: it includes the new 3 deal metrics and changes the source of the already existing 3 deal metrics from `mtd_booking_metrics` to the new `mtd_deal_metrics` - `int_core__mtd_booking_metrics`: removes all code needed to compute the remaining deal metrics, speeding it up considerably. After this PR, the mtd models run (locally) at the following speed: - `int_core__mtd_accommodation_lifecycle`: 47 sec - `int_core__mtd_deal_lifecycle`: 3 sec - `int_core__mtd_accommodation_metrics`: 5 sec - `int_core__mtd_deal_metrics`: < 1 sec - `int_core__mtd_booking_metrics`: 8 sec (quite a reduction) - `int_core__mtd_guest_journey_metrics`: 5 sec - `int_core__mtd_aggregated_metrics` and `core__mtd_aggregated_metrics`: < 1 sec Related work items: #17312
2024-06-25 12:20:59 +00:00
"metric": "Deals Booked in 6 Months",
"value": "deals_booked_in_6_months",
"previous_year_value": "previous_year_deals_booked_in_6_months",
"relative_increment": "relative_increment_deals_booked_in_6_months",
Merged PR 2053: Added number_format category in mtd_aggregated_metrics Added number_format category in mtd_aggregated_metrics Related work items: #17458
2024-06-17 14:59:01 +00:00
"number_format": "integer",
},
{
Merged PR 2257: Expose guest revenue and guest journey payment metrics This PR aims to expose the new metrics to the business KPIs report. The new metrics exposed are, for the global and the by deal view: - Guest Revenue - Guest Revenue per Guest Journey Completed - Guest Revenue per Guest Journey with Payment - Guest Payments - Guest Payments per Guest Journey Completed - Guest Payments per Guest Journey with Payment - Guest Journey with Payment - Guest Journey Payment Rate Changes: - Silly change on the naming in the by deal view of `payment_rate_guest_journey` to be consistent with the global view. - Silly change that I miss some GJ payment metric for the view by deal id. - Added a new number format called `currency_gbp` - only for monetary metrics, available in the schema files - Usual procedure to publish metrics: for global metrics, add them in the `int_mtd_aggregated_metrics`. I also changed the order of display. - **Important**: to avoid displaying revenue figures until Xero invoicing is handled, I created a macro called `is_date_before_previous_month` that is called in the reporting equivalent models: `mtd_aggregated_metrics` in the where section and in the `monthly_aggregated_metrics_history_by_deal` as a case-when. This should allow to expose all new metrics, and enable the publishing of a new update of the business kpis! Related work items: #18107
2024-07-10 14:17:05 +00:00
"order_by": 12,
Merged PR 2107: Adds host lifecycle metrics into biz kpis This PR closes the first draft of the first batch of business kpis. Host logic has changed to be applied at deal id level. It's mostly an adapted copy-paste from the accommodation counterpart, specifically: - `int_core__mtd_deal_lifecycle`: computes the historic deal lifecycle. One line for each deal and MTD date. **Important**: _Not all hosts have a deal set. This will need a data quality report for business teams to fix_ - `int_core__mtd_deal_metrics`: computes the aggregation at MTD date level of the metrics per lifecycle state and activity state Additionally, this PR changes: - `int_core__mtd_aggregated_metrics`: it includes the new 3 deal metrics and changes the source of the already existing 3 deal metrics from `mtd_booking_metrics` to the new `mtd_deal_metrics` - `int_core__mtd_booking_metrics`: removes all code needed to compute the remaining deal metrics, speeding it up considerably. After this PR, the mtd models run (locally) at the following speed: - `int_core__mtd_accommodation_lifecycle`: 47 sec - `int_core__mtd_deal_lifecycle`: 3 sec - `int_core__mtd_accommodation_metrics`: 5 sec - `int_core__mtd_deal_metrics`: < 1 sec - `int_core__mtd_booking_metrics`: 8 sec (quite a reduction) - `int_core__mtd_guest_journey_metrics`: 5 sec - `int_core__mtd_aggregated_metrics` and `core__mtd_aggregated_metrics`: < 1 sec Related work items: #17312
2024-06-25 12:20:59 +00:00
"metric": "Deals Booked in 12 Months",
"value": "deals_booked_in_12_months",
"previous_year_value": "previous_year_deals_booked_in_12_months",
"relative_increment": "relative_increment_deals_booked_in_12_months",
"number_format": "integer",
},
{
Merged PR 2257: Expose guest revenue and guest journey payment metrics This PR aims to expose the new metrics to the business KPIs report. The new metrics exposed are, for the global and the by deal view: - Guest Revenue - Guest Revenue per Guest Journey Completed - Guest Revenue per Guest Journey with Payment - Guest Payments - Guest Payments per Guest Journey Completed - Guest Payments per Guest Journey with Payment - Guest Journey with Payment - Guest Journey Payment Rate Changes: - Silly change on the naming in the by deal view of `payment_rate_guest_journey` to be consistent with the global view. - Silly change that I miss some GJ payment metric for the view by deal id. - Added a new number format called `currency_gbp` - only for monetary metrics, available in the schema files - Usual procedure to publish metrics: for global metrics, add them in the `int_mtd_aggregated_metrics`. I also changed the order of display. - **Important**: to avoid displaying revenue figures until Xero invoicing is handled, I created a macro called `is_date_before_previous_month` that is called in the reporting equivalent models: `mtd_aggregated_metrics` in the where section and in the `monthly_aggregated_metrics_history_by_deal` as a case-when. This should allow to expose all new metrics, and enable the publishing of a new update of the business kpis! Related work items: #18107
2024-07-10 14:17:05 +00:00
"order_by": 13,
Merged PR 2107: Adds host lifecycle metrics into biz kpis This PR closes the first draft of the first batch of business kpis. Host logic has changed to be applied at deal id level. It's mostly an adapted copy-paste from the accommodation counterpart, specifically: - `int_core__mtd_deal_lifecycle`: computes the historic deal lifecycle. One line for each deal and MTD date. **Important**: _Not all hosts have a deal set. This will need a data quality report for business teams to fix_ - `int_core__mtd_deal_metrics`: computes the aggregation at MTD date level of the metrics per lifecycle state and activity state Additionally, this PR changes: - `int_core__mtd_aggregated_metrics`: it includes the new 3 deal metrics and changes the source of the already existing 3 deal metrics from `mtd_booking_metrics` to the new `mtd_deal_metrics` - `int_core__mtd_booking_metrics`: removes all code needed to compute the remaining deal metrics, speeding it up considerably. After this PR, the mtd models run (locally) at the following speed: - `int_core__mtd_accommodation_lifecycle`: 47 sec - `int_core__mtd_deal_lifecycle`: 3 sec - `int_core__mtd_accommodation_metrics`: 5 sec - `int_core__mtd_deal_metrics`: < 1 sec - `int_core__mtd_booking_metrics`: 8 sec (quite a reduction) - `int_core__mtd_guest_journey_metrics`: 5 sec - `int_core__mtd_aggregated_metrics` and `core__mtd_aggregated_metrics`: < 1 sec Related work items: #17312
2024-06-25 12:20:59 +00:00
"metric": "Churning Deals",
"value": "churning_deals",
"previous_year_value": "previous_year_churning_deals",
"relative_increment": "relative_increment_churning_deals",
Merged PR 2053: Added number_format category in mtd_aggregated_metrics Added number_format category in mtd_aggregated_metrics Related work items: #17458
2024-06-17 14:59:01 +00:00
"number_format": "integer",
},
{
Merged PR 2257: Expose guest revenue and guest journey payment metrics This PR aims to expose the new metrics to the business KPIs report. The new metrics exposed are, for the global and the by deal view: - Guest Revenue - Guest Revenue per Guest Journey Completed - Guest Revenue per Guest Journey with Payment - Guest Payments - Guest Payments per Guest Journey Completed - Guest Payments per Guest Journey with Payment - Guest Journey with Payment - Guest Journey Payment Rate Changes: - Silly change on the naming in the by deal view of `payment_rate_guest_journey` to be consistent with the global view. - Silly change that I miss some GJ payment metric for the view by deal id. - Added a new number format called `currency_gbp` - only for monetary metrics, available in the schema files - Usual procedure to publish metrics: for global metrics, add them in the `int_mtd_aggregated_metrics`. I also changed the order of display. - **Important**: to avoid displaying revenue figures until Xero invoicing is handled, I created a macro called `is_date_before_previous_month` that is called in the reporting equivalent models: `mtd_aggregated_metrics` in the where section and in the `monthly_aggregated_metrics_history_by_deal` as a case-when. This should allow to expose all new metrics, and enable the publishing of a new update of the business kpis! Related work items: #18107
2024-07-10 14:17:05 +00:00
"order_by": 14,
Merged PR 2105: Adding listing lifecycle metrics into business KPIs This PR will compute the listing metrics in an aggregated manner to be displayed in the Main KPIs dashboard, specifically: - New Listings - First Time Booked Listings - Churning Listings - It also adapts the computation for the already existing metrics of Listings Booked in X months At code level, it contains the following: - Adds `int_core__mtd_accommodation_metrics`, which computes the aggregation of the lifecycle of listings at date level (unique), being date the corresponding date from `int_dates_mtd` - Changes `int_core__mtd_aggregated_metrics` to take the accommodation metrics from the new model. Those 3 already existing (Listings booked in X month) now read from the new model as well. - Changes `int_core__mtd_booking_metrics` to remove unused computation, making it lighter. Specifically, it removes 1) listing related metrics, since now we have a dedicated model and 2) number of guests booked, since it's not used at all. The resulting values in local are consistent with what is already reported in the staging report. Related work items: #17312
2024-06-25 08:14:23 +00:00
"metric": "New Listings",
"value": "new_listings",
"previous_year_value": "previous_year_new_listings",
"relative_increment": "relative_increment_new_listings",
"number_format": "integer",
},
{
Merged PR 2257: Expose guest revenue and guest journey payment metrics This PR aims to expose the new metrics to the business KPIs report. The new metrics exposed are, for the global and the by deal view: - Guest Revenue - Guest Revenue per Guest Journey Completed - Guest Revenue per Guest Journey with Payment - Guest Payments - Guest Payments per Guest Journey Completed - Guest Payments per Guest Journey with Payment - Guest Journey with Payment - Guest Journey Payment Rate Changes: - Silly change on the naming in the by deal view of `payment_rate_guest_journey` to be consistent with the global view. - Silly change that I miss some GJ payment metric for the view by deal id. - Added a new number format called `currency_gbp` - only for monetary metrics, available in the schema files - Usual procedure to publish metrics: for global metrics, add them in the `int_mtd_aggregated_metrics`. I also changed the order of display. - **Important**: to avoid displaying revenue figures until Xero invoicing is handled, I created a macro called `is_date_before_previous_month` that is called in the reporting equivalent models: `mtd_aggregated_metrics` in the where section and in the `monthly_aggregated_metrics_history_by_deal` as a case-when. This should allow to expose all new metrics, and enable the publishing of a new update of the business kpis! Related work items: #18107
2024-07-10 14:17:05 +00:00
"order_by": 15,
Merged PR 2105: Adding listing lifecycle metrics into business KPIs This PR will compute the listing metrics in an aggregated manner to be displayed in the Main KPIs dashboard, specifically: - New Listings - First Time Booked Listings - Churning Listings - It also adapts the computation for the already existing metrics of Listings Booked in X months At code level, it contains the following: - Adds `int_core__mtd_accommodation_metrics`, which computes the aggregation of the lifecycle of listings at date level (unique), being date the corresponding date from `int_dates_mtd` - Changes `int_core__mtd_aggregated_metrics` to take the accommodation metrics from the new model. Those 3 already existing (Listings booked in X month) now read from the new model as well. - Changes `int_core__mtd_booking_metrics` to remove unused computation, making it lighter. Specifically, it removes 1) listing related metrics, since now we have a dedicated model and 2) number of guests booked, since it's not used at all. The resulting values in local are consistent with what is already reported in the staging report. Related work items: #17312
2024-06-25 08:14:23 +00:00
"metric": "First Time Booked Listings",
"value": "first_time_booked_listings",
"previous_year_value": "previous_year_first_time_booked_listings",
"relative_increment": "relative_increment_first_time_booked_listings",
"number_format": "integer",
},
{
Merged PR 2257: Expose guest revenue and guest journey payment metrics This PR aims to expose the new metrics to the business KPIs report. The new metrics exposed are, for the global and the by deal view: - Guest Revenue - Guest Revenue per Guest Journey Completed - Guest Revenue per Guest Journey with Payment - Guest Payments - Guest Payments per Guest Journey Completed - Guest Payments per Guest Journey with Payment - Guest Journey with Payment - Guest Journey Payment Rate Changes: - Silly change on the naming in the by deal view of `payment_rate_guest_journey` to be consistent with the global view. - Silly change that I miss some GJ payment metric for the view by deal id. - Added a new number format called `currency_gbp` - only for monetary metrics, available in the schema files - Usual procedure to publish metrics: for global metrics, add them in the `int_mtd_aggregated_metrics`. I also changed the order of display. - **Important**: to avoid displaying revenue figures until Xero invoicing is handled, I created a macro called `is_date_before_previous_month` that is called in the reporting equivalent models: `mtd_aggregated_metrics` in the where section and in the `monthly_aggregated_metrics_history_by_deal` as a case-when. This should allow to expose all new metrics, and enable the publishing of a new update of the business kpis! Related work items: #18107
2024-07-10 14:17:05 +00:00
"order_by": 16,
Merged PR 2068: Adding cancelled bookings metric Adding cancelled bookings metric based on the feedback of the tech team. Mainly, the date of a cancelled booking can be considered as the `updated_date_utc` for those bookings with status cancelled, as it's a terminal state and no additional steps should follow. I also took the opportunity to update: - The order on the `int_core__mtd_aggregated_metrics`, so it matches the one in the Notion page for the 1st batch, freeing already the space for the order_by numbers for missing metrics - Make acronyms of alias in the `main_kpi` subquery in `int_core__mtd_booking_metrics` slightly more clear - Remove empty line at the end of the file in `int_core__mtd_booking_metrics` Keep in mind that the cancelled bookings metric will be directly available in the dashboard once this PR is approved and DWH re-runs. Related work items: #17310
2024-06-18 14:58:55 +00:00
"metric": "Listings Booked in Month",
"value": "listings_booked_in_month",
"previous_year_value": "previous_year_listings_booked_in_month",
"relative_increment": "relative_increment_listings_booked_in_month",
Merged PR 2053: Added number_format category in mtd_aggregated_metrics Added number_format category in mtd_aggregated_metrics Related work items: #17458
2024-06-17 14:59:01 +00:00
"number_format": "integer",
},
{
Merged PR 2257: Expose guest revenue and guest journey payment metrics This PR aims to expose the new metrics to the business KPIs report. The new metrics exposed are, for the global and the by deal view: - Guest Revenue - Guest Revenue per Guest Journey Completed - Guest Revenue per Guest Journey with Payment - Guest Payments - Guest Payments per Guest Journey Completed - Guest Payments per Guest Journey with Payment - Guest Journey with Payment - Guest Journey Payment Rate Changes: - Silly change on the naming in the by deal view of `payment_rate_guest_journey` to be consistent with the global view. - Silly change that I miss some GJ payment metric for the view by deal id. - Added a new number format called `currency_gbp` - only for monetary metrics, available in the schema files - Usual procedure to publish metrics: for global metrics, add them in the `int_mtd_aggregated_metrics`. I also changed the order of display. - **Important**: to avoid displaying revenue figures until Xero invoicing is handled, I created a macro called `is_date_before_previous_month` that is called in the reporting equivalent models: `mtd_aggregated_metrics` in the where section and in the `monthly_aggregated_metrics_history_by_deal` as a case-when. This should allow to expose all new metrics, and enable the publishing of a new update of the business kpis! Related work items: #18107
2024-07-10 14:17:05 +00:00
"order_by": 17,
Merged PR 2068: Adding cancelled bookings metric Adding cancelled bookings metric based on the feedback of the tech team. Mainly, the date of a cancelled booking can be considered as the `updated_date_utc` for those bookings with status cancelled, as it's a terminal state and no additional steps should follow. I also took the opportunity to update: - The order on the `int_core__mtd_aggregated_metrics`, so it matches the one in the Notion page for the 1st batch, freeing already the space for the order_by numbers for missing metrics - Make acronyms of alias in the `main_kpi` subquery in `int_core__mtd_booking_metrics` slightly more clear - Remove empty line at the end of the file in `int_core__mtd_booking_metrics` Keep in mind that the cancelled bookings metric will be directly available in the dashboard once this PR is approved and DWH re-runs. Related work items: #17310
2024-06-18 14:58:55 +00:00
"metric": "Listings Booked in 6 Months",
"value": "listings_booked_in_6_months",
"previous_year_value": "previous_year_listings_booked_in_6_months",
"relative_increment": "relative_increment_listings_booked_in_6_months",
Merged PR 2053: Added number_format category in mtd_aggregated_metrics Added number_format category in mtd_aggregated_metrics Related work items: #17458
2024-06-17 14:59:01 +00:00
"number_format": "integer",
},
{
Merged PR 2257: Expose guest revenue and guest journey payment metrics This PR aims to expose the new metrics to the business KPIs report. The new metrics exposed are, for the global and the by deal view: - Guest Revenue - Guest Revenue per Guest Journey Completed - Guest Revenue per Guest Journey with Payment - Guest Payments - Guest Payments per Guest Journey Completed - Guest Payments per Guest Journey with Payment - Guest Journey with Payment - Guest Journey Payment Rate Changes: - Silly change on the naming in the by deal view of `payment_rate_guest_journey` to be consistent with the global view. - Silly change that I miss some GJ payment metric for the view by deal id. - Added a new number format called `currency_gbp` - only for monetary metrics, available in the schema files - Usual procedure to publish metrics: for global metrics, add them in the `int_mtd_aggregated_metrics`. I also changed the order of display. - **Important**: to avoid displaying revenue figures until Xero invoicing is handled, I created a macro called `is_date_before_previous_month` that is called in the reporting equivalent models: `mtd_aggregated_metrics` in the where section and in the `monthly_aggregated_metrics_history_by_deal` as a case-when. This should allow to expose all new metrics, and enable the publishing of a new update of the business kpis! Related work items: #18107
2024-07-10 14:17:05 +00:00
"order_by": 18,
Merged PR 2068: Adding cancelled bookings metric Adding cancelled bookings metric based on the feedback of the tech team. Mainly, the date of a cancelled booking can be considered as the `updated_date_utc` for those bookings with status cancelled, as it's a terminal state and no additional steps should follow. I also took the opportunity to update: - The order on the `int_core__mtd_aggregated_metrics`, so it matches the one in the Notion page for the 1st batch, freeing already the space for the order_by numbers for missing metrics - Make acronyms of alias in the `main_kpi` subquery in `int_core__mtd_booking_metrics` slightly more clear - Remove empty line at the end of the file in `int_core__mtd_booking_metrics` Keep in mind that the cancelled bookings metric will be directly available in the dashboard once this PR is approved and DWH re-runs. Related work items: #17310
2024-06-18 14:58:55 +00:00
"metric": "Listings Booked in 12 Months",
"value": "listings_booked_in_12_months",
"previous_year_value": "previous_year_listings_booked_in_12_months",
"relative_increment": "relative_increment_listings_booked_in_12_months",
Merged PR 2053: Added number_format category in mtd_aggregated_metrics Added number_format category in mtd_aggregated_metrics Related work items: #17458
2024-06-17 14:59:01 +00:00
"number_format": "integer",
},
Merged PR 2105: Adding listing lifecycle metrics into business KPIs This PR will compute the listing metrics in an aggregated manner to be displayed in the Main KPIs dashboard, specifically: - New Listings - First Time Booked Listings - Churning Listings - It also adapts the computation for the already existing metrics of Listings Booked in X months At code level, it contains the following: - Adds `int_core__mtd_accommodation_metrics`, which computes the aggregation of the lifecycle of listings at date level (unique), being date the corresponding date from `int_dates_mtd` - Changes `int_core__mtd_aggregated_metrics` to take the accommodation metrics from the new model. Those 3 already existing (Listings booked in X month) now read from the new model as well. - Changes `int_core__mtd_booking_metrics` to remove unused computation, making it lighter. Specifically, it removes 1) listing related metrics, since now we have a dedicated model and 2) number of guests booked, since it's not used at all. The resulting values in local are consistent with what is already reported in the staging report. Related work items: #17312
2024-06-25 08:14:23 +00:00
{
Merged PR 2257: Expose guest revenue and guest journey payment metrics This PR aims to expose the new metrics to the business KPIs report. The new metrics exposed are, for the global and the by deal view: - Guest Revenue - Guest Revenue per Guest Journey Completed - Guest Revenue per Guest Journey with Payment - Guest Payments - Guest Payments per Guest Journey Completed - Guest Payments per Guest Journey with Payment - Guest Journey with Payment - Guest Journey Payment Rate Changes: - Silly change on the naming in the by deal view of `payment_rate_guest_journey` to be consistent with the global view. - Silly change that I miss some GJ payment metric for the view by deal id. - Added a new number format called `currency_gbp` - only for monetary metrics, available in the schema files - Usual procedure to publish metrics: for global metrics, add them in the `int_mtd_aggregated_metrics`. I also changed the order of display. - **Important**: to avoid displaying revenue figures until Xero invoicing is handled, I created a macro called `is_date_before_previous_month` that is called in the reporting equivalent models: `mtd_aggregated_metrics` in the where section and in the `monthly_aggregated_metrics_history_by_deal` as a case-when. This should allow to expose all new metrics, and enable the publishing of a new update of the business kpis! Related work items: #18107
2024-07-10 14:17:05 +00:00
"order_by": 19,
Merged PR 2105: Adding listing lifecycle metrics into business KPIs This PR will compute the listing metrics in an aggregated manner to be displayed in the Main KPIs dashboard, specifically: - New Listings - First Time Booked Listings - Churning Listings - It also adapts the computation for the already existing metrics of Listings Booked in X months At code level, it contains the following: - Adds `int_core__mtd_accommodation_metrics`, which computes the aggregation of the lifecycle of listings at date level (unique), being date the corresponding date from `int_dates_mtd` - Changes `int_core__mtd_aggregated_metrics` to take the accommodation metrics from the new model. Those 3 already existing (Listings booked in X month) now read from the new model as well. - Changes `int_core__mtd_booking_metrics` to remove unused computation, making it lighter. Specifically, it removes 1) listing related metrics, since now we have a dedicated model and 2) number of guests booked, since it's not used at all. The resulting values in local are consistent with what is already reported in the staging report. Related work items: #17312
2024-06-25 08:14:23 +00:00
"metric": "Churning Listings",
"value": "churning_listings",
"previous_year_value": "previous_year_churning_listings",
"relative_increment": "relative_increment_churning_listings",
"number_format": "integer",
},
Merged PR 2053: Added number_format category in mtd_aggregated_metrics Added number_format category in mtd_aggregated_metrics Related work items: #17458
2024-06-17 14:59:01 +00:00
{
Merged PR 2257: Expose guest revenue and guest journey payment metrics This PR aims to expose the new metrics to the business KPIs report. The new metrics exposed are, for the global and the by deal view: - Guest Revenue - Guest Revenue per Guest Journey Completed - Guest Revenue per Guest Journey with Payment - Guest Payments - Guest Payments per Guest Journey Completed - Guest Payments per Guest Journey with Payment - Guest Journey with Payment - Guest Journey Payment Rate Changes: - Silly change on the naming in the by deal view of `payment_rate_guest_journey` to be consistent with the global view. - Silly change that I miss some GJ payment metric for the view by deal id. - Added a new number format called `currency_gbp` - only for monetary metrics, available in the schema files - Usual procedure to publish metrics: for global metrics, add them in the `int_mtd_aggregated_metrics`. I also changed the order of display. - **Important**: to avoid displaying revenue figures until Xero invoicing is handled, I created a macro called `is_date_before_previous_month` that is called in the reporting equivalent models: `mtd_aggregated_metrics` in the where section and in the `monthly_aggregated_metrics_history_by_deal` as a case-when. This should allow to expose all new metrics, and enable the publishing of a new update of the business kpis! Related work items: #18107
2024-07-10 14:17:05 +00:00
"order_by": 100,
Merged PR 2053: Added number_format category in mtd_aggregated_metrics Added number_format category in mtd_aggregated_metrics Related work items: #17458
2024-06-17 14:59:01 +00:00
"metric": "Guest Journey Start Rate",
"value": "start_rate_guest_journey",
"previous_year_value": "previous_year_start_rate_guest_journey",
"relative_increment": "relative_increment_start_rate_guest_journey",
"number_format": "percentage",
},
{
Merged PR 2257: Expose guest revenue and guest journey payment metrics This PR aims to expose the new metrics to the business KPIs report. The new metrics exposed are, for the global and the by deal view: - Guest Revenue - Guest Revenue per Guest Journey Completed - Guest Revenue per Guest Journey with Payment - Guest Payments - Guest Payments per Guest Journey Completed - Guest Payments per Guest Journey with Payment - Guest Journey with Payment - Guest Journey Payment Rate Changes: - Silly change on the naming in the by deal view of `payment_rate_guest_journey` to be consistent with the global view. - Silly change that I miss some GJ payment metric for the view by deal id. - Added a new number format called `currency_gbp` - only for monetary metrics, available in the schema files - Usual procedure to publish metrics: for global metrics, add them in the `int_mtd_aggregated_metrics`. I also changed the order of display. - **Important**: to avoid displaying revenue figures until Xero invoicing is handled, I created a macro called `is_date_before_previous_month` that is called in the reporting equivalent models: `mtd_aggregated_metrics` in the where section and in the `monthly_aggregated_metrics_history_by_deal` as a case-when. This should allow to expose all new metrics, and enable the publishing of a new update of the business kpis! Related work items: #18107
2024-07-10 14:17:05 +00:00
"order_by": 101,
Merged PR 2053: Added number_format category in mtd_aggregated_metrics Added number_format category in mtd_aggregated_metrics Related work items: #17458
2024-06-17 14:59:01 +00:00
"metric": "Guest Journey Completion Rate",
"value": "completion_rate_guest_journey",
"previous_year_value": "previous_year_completion_rate_guest_journey",
"relative_increment": "relative_increment_completion_rate_guest_journey",
"number_format": "percentage",
},
{
Merged PR 2257: Expose guest revenue and guest journey payment metrics This PR aims to expose the new metrics to the business KPIs report. The new metrics exposed are, for the global and the by deal view: - Guest Revenue - Guest Revenue per Guest Journey Completed - Guest Revenue per Guest Journey with Payment - Guest Payments - Guest Payments per Guest Journey Completed - Guest Payments per Guest Journey with Payment - Guest Journey with Payment - Guest Journey Payment Rate Changes: - Silly change on the naming in the by deal view of `payment_rate_guest_journey` to be consistent with the global view. - Silly change that I miss some GJ payment metric for the view by deal id. - Added a new number format called `currency_gbp` - only for monetary metrics, available in the schema files - Usual procedure to publish metrics: for global metrics, add them in the `int_mtd_aggregated_metrics`. I also changed the order of display. - **Important**: to avoid displaying revenue figures until Xero invoicing is handled, I created a macro called `is_date_before_previous_month` that is called in the reporting equivalent models: `mtd_aggregated_metrics` in the where section and in the `monthly_aggregated_metrics_history_by_deal` as a case-when. This should allow to expose all new metrics, and enable the publishing of a new update of the business kpis! Related work items: #18107
2024-07-10 14:17:05 +00:00
"order_by": 102,
Merged PR 2053: Added number_format category in mtd_aggregated_metrics Added number_format category in mtd_aggregated_metrics Related work items: #17458
2024-06-17 14:59:01 +00:00
"metric": "Guest Journey Incompletion Rate",
"value": "incompletion_rate_guest_journey",
"previous_year_value": "previous_year_incompletion_rate_guest_journey",
"relative_increment": "relative_increment_incompletion_rate_guest_journey",
"number_format": "percentage",
},
Merged PR 2257: Expose guest revenue and guest journey payment metrics This PR aims to expose the new metrics to the business KPIs report. The new metrics exposed are, for the global and the by deal view: - Guest Revenue - Guest Revenue per Guest Journey Completed - Guest Revenue per Guest Journey with Payment - Guest Payments - Guest Payments per Guest Journey Completed - Guest Payments per Guest Journey with Payment - Guest Journey with Payment - Guest Journey Payment Rate Changes: - Silly change on the naming in the by deal view of `payment_rate_guest_journey` to be consistent with the global view. - Silly change that I miss some GJ payment metric for the view by deal id. - Added a new number format called `currency_gbp` - only for monetary metrics, available in the schema files - Usual procedure to publish metrics: for global metrics, add them in the `int_mtd_aggregated_metrics`. I also changed the order of display. - **Important**: to avoid displaying revenue figures until Xero invoicing is handled, I created a macro called `is_date_before_previous_month` that is called in the reporting equivalent models: `mtd_aggregated_metrics` in the where section and in the `monthly_aggregated_metrics_history_by_deal` as a case-when. This should allow to expose all new metrics, and enable the publishing of a new update of the business kpis! Related work items: #18107
2024-07-10 14:17:05 +00:00
{
"order_by": 103,
"metric": "Guest Journey Payment Rate",
"value": "payment_rate_guest_journey",
"previous_year_value": "previous_year_payment_rate_guest_journey",
"relative_increment": "relative_increment_payment_rate_guest_journey",
"number_format": "percentage",
},
{
"order_by": 200,
"metric": "Guest Payments (GBP)",
"value": "total_guest_payments_in_gbp",
"previous_year_value": "previous_year_total_guest_payments_in_gbp",
"relative_increment": "relative_increment_total_guest_payments_in_gbp",
"number_format": "currency_gbp",
},
{
"order_by": 201,
"metric": "Guest Payments per Guest Journey Completed (GBP)",
"value": "guest_payments_per_completed_guest_journey",
"previous_year_value": "previous_year_guest_payments_per_completed_guest_journey",
"relative_increment": "relative_increment_guest_payments_per_completed_guest_journey",
"number_format": "currency_gbp",
},
{
"order_by": 202,
"metric": "Guest Payments per Guest Journey with Payment (GBP)",
"value": "guest_payments_per_paid_guest_journey",
"previous_year_value": "previous_year_guest_payments_per_paid_guest_journey",
"relative_increment": "relative_increment_guest_payments_per_paid_guest_journey",
"number_format": "currency_gbp",
},
{
"order_by": 203,
"metric": "Guest Revenue (GBP)",
"value": "total_guest_revenue_in_gbp",
"previous_year_value": "previous_year_total_guest_revenue_in_gbp",
"relative_increment": "relative_increment_total_guest_revenue_in_gbp",
"number_format": "currency_gbp",
},
{
"order_by": 204,
"metric": "Guest Revenue per Guest Journey Completed (GBP)",
"value": "guest_revenue_per_completed_guest_journey",
"previous_year_value": "previous_year_guest_revenue_per_completed_guest_journey",
"relative_increment": "relative_increment_guest_revenue_per_completed_guest_journey",
"number_format": "currency_gbp",
},
{
"order_by": 205,
"metric": "Guest Revenue per Guest Journey with Payment (GBP)",
"value": "guest_revenue_per_paid_guest_journey",
"previous_year_value": "previous_year_guest_revenue_per_paid_guest_journey",
"relative_increment": "relative_increment_guest_revenue_per_paid_guest_journey",
"number_format": "currency_gbp",
}
Adding guest journey KPIs. Updating gitignore
2024-06-17 11:10:13 +02:00
] %}
Merged PR 2003: Business KPIs first draft This PR aims to provide a first draft for business KPIs, at this stage **quite minimal**. It mostly contains a MTD and Monthly display approach. No dimensions are created. The models created are: - **int_dates_mtd**: mainly it reads from int_dates to retrieve those days needed for a MTD/monthly display - **int_core__mtd_booking_metrics**: it contains the booking metrics, ending in a format of date|value|value last year|increment --> here we could add, in the future, additional metrics from other sources (ex: guest journey, etc) - **int_core__mtd_aggregated_metrics**: it transforms the data coming from the different mtd intermediate sources to be easily displayed in the dashboard. This is a good candidate for macros :) - **core__mtd_aggregated_metrics**: copy-paste of the its int_core version, including a bit of model documentation The dashboard is functional but in another PR. I can show you how it looks like at the moment you are going to check the PR Related work items: #17214
2024-06-11 15:45:57 +00:00
with
Merged PR 2232: KPI refactor - 1st step, bookings First step on refactor of kpis: - Remove relative incremental vs. previous year computation from the source model (`mtd_booking_metrics`, in this case) - Aggregate the source mtd global metrics models into a single model: `int_mtd_vs_previous_year_metrics` (to enable multi-source weighted metric computation) and compute previous year value and relative increment. Now this logic is encapsulated into a macro `calculate_safe_relative_increment`, easing readability and providing a bit more robustness. - End-to-end continuity to not break the existing dashboard display in `int_core__mtd_aggregated_metrics` This is a substep of the global change. All info can be found in the documentation [here](https://www.notion.so/knowyourguest-superhog/Refactoring-Business-KPIs-5deb6aadddb34884ae90339402ac16e3) Related work items: #18202
2024-07-08 15:58:36 +00:00
int_mtd_vs_previous_year_metrics as (
select * from {{ ref("int_mtd_vs_previous_year_metrics") }}
Merged PR 2003: Business KPIs first draft This PR aims to provide a first draft for business KPIs, at this stage **quite minimal**. It mostly contains a MTD and Monthly display approach. No dimensions are created. The models created are: - **int_dates_mtd**: mainly it reads from int_dates to retrieve those days needed for a MTD/monthly display - **int_core__mtd_booking_metrics**: it contains the booking metrics, ending in a format of date|value|value last year|increment --> here we could add, in the future, additional metrics from other sources (ex: guest journey, etc) - **int_core__mtd_aggregated_metrics**: it transforms the data coming from the different mtd intermediate sources to be easily displayed in the dashboard. This is a good candidate for macros :) - **core__mtd_aggregated_metrics**: copy-paste of the its int_core version, including a bit of model documentation The dashboard is functional but in another PR. I can show you how it looks like at the moment you are going to check the PR Related work items: #17214
2024-06-11 15:45:57 +00:00
)
{% for metric in metrics %}
Merged PR 2053: Added number_format category in mtd_aggregated_metrics Added number_format category in mtd_aggregated_metrics Related work items: #17458
2024-06-17 14:59:01 +00:00
select
year,
month,
day,
is_end_of_month,
is_current_month,
date,
previous_year_date,
{{ metric.order_by }} as order_by,
-- quotation marks added because text format
'{{ metric.number_format }}' as number_format,
'{{ metric.metric }}' as metric,
{{ metric.value }} as value,
{{ metric.previous_year_value }} as previous_year_value,
{{ metric.relative_increment }} as relative_increment
Merged PR 2236: Refactor of already exposed metrics: listings, deals and guest journeys Following yesterday's refactor of booking metrics, this PR provides a refactor of already exposed metrics: listings, deals and guest journeys. -> Data is consistent with values already exposed. Changes: - for `int_core__mtd_listing_metrics`, `int_core__mtd_deal_metrics` and `int_core__mtd_guest_journey_metrics`: 1. remove the computation of the previous year metric value and the relative increment (last part of the query) 2. re-apply the formatting - for `int_mtd_vs_previous_year_metrics`: 1. Reference listings, deals and GJ models 2. Include the metrics for these types in the `plain_kpi_combination` CTE 3. Add the computation of previous year and relative increment using the macro - for `int_core__mtd_aggregated_metrics` 1. Remove and "hardcode" sources since all metrics now depend exclusively of `int_mtd_vs_previous_year_metrics` This PR does not alter the exposed metrics in the production report. It does not aim to change the name of the reporting/intermediate models that expose the information, it will be done in a separated PR. Documentation: https://www.notion.so/knowyourguest-superhog/Refactoring-Business-KPIs-5deb6aadddb34884ae90339402ac16e3 Related work items: #18202
2024-07-09 13:00:43 +00:00
from int_mtd_vs_previous_year_metrics
Merged PR 2053: Added number_format category in mtd_aggregated_metrics Added number_format category in mtd_aggregated_metrics Related work items: #17458
2024-06-17 14:59:01 +00:00
{% if not loop.last %}
union all
{% endif %}
Merged PR 2003: Business KPIs first draft This PR aims to provide a first draft for business KPIs, at this stage **quite minimal**. It mostly contains a MTD and Monthly display approach. No dimensions are created. The models created are: - **int_dates_mtd**: mainly it reads from int_dates to retrieve those days needed for a MTD/monthly display - **int_core__mtd_booking_metrics**: it contains the booking metrics, ending in a format of date|value|value last year|increment --> here we could add, in the future, additional metrics from other sources (ex: guest journey, etc) - **int_core__mtd_aggregated_metrics**: it transforms the data coming from the different mtd intermediate sources to be easily displayed in the dashboard. This is a good candidate for macros :) - **core__mtd_aggregated_metrics**: copy-paste of the its int_core version, including a bit of model documentation The dashboard is functional but in another PR. I can show you how it looks like at the moment you are going to check the PR Related work items: #17214
2024-06-11 15:45:57 +00:00
{% endfor %}
Reference in a new issue Copy permalink