ca8334f1da
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 |
||
|---|---|---|
| .. | ||
| int_daily_currency_exchange_rates.sql | ||
| int_dates.sql | ||
| int_dates_by_deal.sql | ||
| int_dates_mtd.sql | ||
| int_monthly_guest_revenue_history_by_deal.sql | ||
| int_mtd_guest_revenue_metrics.sql | ||
| int_mtd_vs_previous_year_metrics.sql | ||
| int_simple_exchange_rates.sql | ||
| schema.yml | ||