data-dwh-dbt-project/models/intermediate/cross/int_mtd_vs_previous_year_metrics.sql

290 lines
13 KiB
MySQL
Raw Normal View History

/*
This model pivots the data of the different mtd metrics models to get
previous year for each line & computing relative increment. --
*/
{{ config(materialized="table", unique_key="date") }}
with
int_core__mtd_booking_metrics as (
select * from {{ ref("int_core__mtd_booking_metrics") }}
),
int_core__mtd_guest_journey_metrics as (
select * from {{ ref("int_core__mtd_guest_journey_metrics") }}
),
int_core__mtd_accommodation_metrics as (
select * from {{ ref("int_core__mtd_accommodation_metrics") }}
),
int_core__mtd_deal_metrics as (
select * from {{ ref("int_core__mtd_deal_metrics") }}
),
int_core__mtd_guest_payments_metrics as (
select * from {{ ref("int_core__mtd_guest_payments_metrics") }}
),
Merged PR 2292: Propagate invoicing metrics for KPIs This PR aims to propagate the invoicing metrics through the DWH. It does not expose them to users, yet. This PR effectively computes the following metrics, for both the "global" view (MTD) and the "by deal" view (by_deal): - Invoiced Operator Revenue - Host Resolution Count of Payments - Host Resolution Amount Paid With these 3 new metrics, we're able to combine them with the existing ones to compute: - Total Revenue - Total Revenue per Booking Created - Total Revenue per Guest Journey Created - Total Revenue per Deal Booked in Month - Total Revenue per Listings Booked in Month You'll also note that I've included standalone metrics for booking fees, listing fees, verification fees and waiver payments. This will not be exposed in this batch 2, but based on the conversation with Finance, will clearly make it for batch 3. I just find it easier to add it now, since it's straight forward. Main changes: - `int_mtd_vs_previous_year_metrics` now computes all the above mentioned metrics - `int_monthly_aggregated_metrics_history_by_deal` now computes all the above mentioned metrics, except Total Revenue per Deal Booked in Month since it does not make sense for the deal view. Additionally, I took the opportunity to include the missing metrics from listings (accommodations). The goal is not necessarily to display them, but at least compute it on our side. Additional changes: - In `int_xero__mtd_invoicing_metrics` and `int_xero__monthly_invoicing_history_by_deal`, there's a very silly name change to keep the same convention for fees: from `xero_operator_net_fees` to `xero_operator_net_fees_in_gbp` - I applied additional changes in `int_monthly_aggregated_metrics_history_by_deal` with the goal to keep the same format as we have in `int_mtd_vs_previous_year_metrics`, this meaning: 1 - explicit alias naming (from `gj` to `guest_journeys`) 2 - keep a similar arrangement of metrics, and clearly separate scopes depending on the metric type 3 - Re-apply autoformatting Related work items: #18108, #18109, #18110
2024-07-15 07:33:55 +00:00
int_xero__mtd_invoicing_metrics as (
select * from {{ ref("int_xero__mtd_invoicing_metrics") }}
Merged PR 2292: Propagate invoicing metrics for KPIs This PR aims to propagate the invoicing metrics through the DWH. It does not expose them to users, yet. This PR effectively computes the following metrics, for both the "global" view (MTD) and the "by deal" view (by_deal): - Invoiced Operator Revenue - Host Resolution Count of Payments - Host Resolution Amount Paid With these 3 new metrics, we're able to combine them with the existing ones to compute: - Total Revenue - Total Revenue per Booking Created - Total Revenue per Guest Journey Created - Total Revenue per Deal Booked in Month - Total Revenue per Listings Booked in Month You'll also note that I've included standalone metrics for booking fees, listing fees, verification fees and waiver payments. This will not be exposed in this batch 2, but based on the conversation with Finance, will clearly make it for batch 3. I just find it easier to add it now, since it's straight forward. Main changes: - `int_mtd_vs_previous_year_metrics` now computes all the above mentioned metrics - `int_monthly_aggregated_metrics_history_by_deal` now computes all the above mentioned metrics, except Total Revenue per Deal Booked in Month since it does not make sense for the deal view. Additionally, I took the opportunity to include the missing metrics from listings (accommodations). The goal is not necessarily to display them, but at least compute it on our side. Additional changes: - In `int_xero__mtd_invoicing_metrics` and `int_xero__monthly_invoicing_history_by_deal`, there's a very silly name change to keep the same convention for fees: from `xero_operator_net_fees` to `xero_operator_net_fees_in_gbp` - I applied additional changes in `int_monthly_aggregated_metrics_history_by_deal` with the goal to keep the same format as we have in `int_mtd_vs_previous_year_metrics`, this meaning: 1 - explicit alias naming (from `gj` to `guest_journeys`) 2 - keep a similar arrangement of metrics, and clearly separate scopes depending on the metric type 3 - Re-apply autoformatting Related work items: #18108, #18109, #18110
2024-07-15 07:33:55 +00:00
),
int_dates_mtd as (select * from {{ ref("int_dates_mtd") }}),
plain_kpi_combination as (
Merged PR 2292: Propagate invoicing metrics for KPIs This PR aims to propagate the invoicing metrics through the DWH. It does not expose them to users, yet. This PR effectively computes the following metrics, for both the "global" view (MTD) and the "by deal" view (by_deal): - Invoiced Operator Revenue - Host Resolution Count of Payments - Host Resolution Amount Paid With these 3 new metrics, we're able to combine them with the existing ones to compute: - Total Revenue - Total Revenue per Booking Created - Total Revenue per Guest Journey Created - Total Revenue per Deal Booked in Month - Total Revenue per Listings Booked in Month You'll also note that I've included standalone metrics for booking fees, listing fees, verification fees and waiver payments. This will not be exposed in this batch 2, but based on the conversation with Finance, will clearly make it for batch 3. I just find it easier to add it now, since it's straight forward. Main changes: - `int_mtd_vs_previous_year_metrics` now computes all the above mentioned metrics - `int_monthly_aggregated_metrics_history_by_deal` now computes all the above mentioned metrics, except Total Revenue per Deal Booked in Month since it does not make sense for the deal view. Additionally, I took the opportunity to include the missing metrics from listings (accommodations). The goal is not necessarily to display them, but at least compute it on our side. Additional changes: - In `int_xero__mtd_invoicing_metrics` and `int_xero__monthly_invoicing_history_by_deal`, there's a very silly name change to keep the same convention for fees: from `xero_operator_net_fees` to `xero_operator_net_fees_in_gbp` - I applied additional changes in `int_monthly_aggregated_metrics_history_by_deal` with the goal to keep the same format as we have in `int_mtd_vs_previous_year_metrics`, this meaning: 1 - explicit alias naming (from `gj` to `guest_journeys`) 2 - keep a similar arrangement of metrics, and clearly separate scopes depending on the metric type 3 - Re-apply autoformatting Related work items: #18108, #18109, #18110
2024-07-15 07:33:55 +00:00
select
d.year,
d.month,
d.day,
d.is_end_of_month,
d.is_current_month,
d.first_day_month,
d.date,
-- BOOKINGS --
bookings.created_bookings,
bookings.check_out_bookings,
bookings.cancelled_bookings,
bookings.billable_bookings,
-- GUEST JOURNEYS --
guest_journeys.created_guest_journeys,
guest_journeys.started_guest_journeys,
guest_journeys.completed_guest_journeys,
guest_journeys.paid_guest_journeys,
guest_journeys.start_rate_guest_journey,
guest_journeys.completion_rate_guest_journey,
guest_journeys.incompletion_rate_guest_journey,
guest_journeys.payment_rate_guest_journey,
-- DEALS --
deals.new_deals,
deals.never_booked_deals,
deals.first_time_booked_deals,
deals.active_deals,
deals.churning_deals,
deals.inactive_deals,
deals.reactivated_deals,
deals.deals_booked_in_month,
deals.deals_booked_in_6_months,
deals.deals_booked_in_12_months,
-- LISTINGS (ACCOMMODATIONS) --
accommodations.new_listings,
accommodations.never_booked_listings,
accommodations.first_time_booked_listings,
accommodations.active_listings,
accommodations.churning_listings,
accommodations.inactive_listings,
accommodations.reactivated_listings,
accommodations.listings_booked_in_month,
accommodations.listings_booked_in_6_months,
accommodations.listings_booked_in_12_months,
Merged PR 2292: Propagate invoicing metrics for KPIs This PR aims to propagate the invoicing metrics through the DWH. It does not expose them to users, yet. This PR effectively computes the following metrics, for both the "global" view (MTD) and the "by deal" view (by_deal): - Invoiced Operator Revenue - Host Resolution Count of Payments - Host Resolution Amount Paid With these 3 new metrics, we're able to combine them with the existing ones to compute: - Total Revenue - Total Revenue per Booking Created - Total Revenue per Guest Journey Created - Total Revenue per Deal Booked in Month - Total Revenue per Listings Booked in Month You'll also note that I've included standalone metrics for booking fees, listing fees, verification fees and waiver payments. This will not be exposed in this batch 2, but based on the conversation with Finance, will clearly make it for batch 3. I just find it easier to add it now, since it's straight forward. Main changes: - `int_mtd_vs_previous_year_metrics` now computes all the above mentioned metrics - `int_monthly_aggregated_metrics_history_by_deal` now computes all the above mentioned metrics, except Total Revenue per Deal Booked in Month since it does not make sense for the deal view. Additionally, I took the opportunity to include the missing metrics from listings (accommodations). The goal is not necessarily to display them, but at least compute it on our side. Additional changes: - In `int_xero__mtd_invoicing_metrics` and `int_xero__monthly_invoicing_history_by_deal`, there's a very silly name change to keep the same convention for fees: from `xero_operator_net_fees` to `xero_operator_net_fees_in_gbp` - I applied additional changes in `int_monthly_aggregated_metrics_history_by_deal` with the goal to keep the same format as we have in `int_mtd_vs_previous_year_metrics`, this meaning: 1 - explicit alias naming (from `gj` to `guest_journeys`) 2 - keep a similar arrangement of metrics, and clearly separate scopes depending on the metric type 3 - Re-apply autoformatting Related work items: #18108, #18109, #18110
2024-07-15 07:33:55 +00:00
-- HOST (OPERATOR) REVENUE --
invoicing.xero_booking_net_fees_in_gbp,
invoicing.xero_listing_net_fees_in_gbp,
invoicing.xero_verification_net_fees_in_gbp,
invoicing.xero_operator_net_fees_in_gbp,
invoicing.xero_waiver_net_fees_in_gbp,
-- APIs REVENUE --
invoicing.xero_apis_net_fees_in_gbp,
invoicing.xero_e_deposit_net_fees_in_gbp,
invoicing.xero_guesty_net_fees_in_gbp,
Merged PR 2292: Propagate invoicing metrics for KPIs This PR aims to propagate the invoicing metrics through the DWH. It does not expose them to users, yet. This PR effectively computes the following metrics, for both the "global" view (MTD) and the "by deal" view (by_deal): - Invoiced Operator Revenue - Host Resolution Count of Payments - Host Resolution Amount Paid With these 3 new metrics, we're able to combine them with the existing ones to compute: - Total Revenue - Total Revenue per Booking Created - Total Revenue per Guest Journey Created - Total Revenue per Deal Booked in Month - Total Revenue per Listings Booked in Month You'll also note that I've included standalone metrics for booking fees, listing fees, verification fees and waiver payments. This will not be exposed in this batch 2, but based on the conversation with Finance, will clearly make it for batch 3. I just find it easier to add it now, since it's straight forward. Main changes: - `int_mtd_vs_previous_year_metrics` now computes all the above mentioned metrics - `int_monthly_aggregated_metrics_history_by_deal` now computes all the above mentioned metrics, except Total Revenue per Deal Booked in Month since it does not make sense for the deal view. Additionally, I took the opportunity to include the missing metrics from listings (accommodations). The goal is not necessarily to display them, but at least compute it on our side. Additional changes: - In `int_xero__mtd_invoicing_metrics` and `int_xero__monthly_invoicing_history_by_deal`, there's a very silly name change to keep the same convention for fees: from `xero_operator_net_fees` to `xero_operator_net_fees_in_gbp` - I applied additional changes in `int_monthly_aggregated_metrics_history_by_deal` with the goal to keep the same format as we have in `int_mtd_vs_previous_year_metrics`, this meaning: 1 - explicit alias naming (from `gj` to `guest_journeys`) 2 - keep a similar arrangement of metrics, and clearly separate scopes depending on the metric type 3 - Re-apply autoformatting Related work items: #18108, #18109, #18110
2024-07-15 07:33:55 +00:00
-- HOST RESOLUTIONS --
invoicing.xero_host_resolution_amount_paid_in_gbp,
invoicing.xero_host_resolution_payment_count,
-- GUEST REVENUE AND PAYMENTS --
guest_payments.deposit_fees_in_gbp,
guest_payments.waiver_payments_in_gbp,
guest_payments.checkin_cover_fees_in_gbp,
guest_payments.total_guest_payments_in_gbp,
guest_payments.total_guest_income_in_gbp,
nullif(
coalesce(guest_payments.total_guest_income_in_gbp, 0)
+ coalesce(invoicing.xero_waiver_net_fees_in_gbp, 0),
0
) as total_guest_revenue_in_gbp,
Merged PR 2292: Propagate invoicing metrics for KPIs This PR aims to propagate the invoicing metrics through the DWH. It does not expose them to users, yet. This PR effectively computes the following metrics, for both the "global" view (MTD) and the "by deal" view (by_deal): - Invoiced Operator Revenue - Host Resolution Count of Payments - Host Resolution Amount Paid With these 3 new metrics, we're able to combine them with the existing ones to compute: - Total Revenue - Total Revenue per Booking Created - Total Revenue per Guest Journey Created - Total Revenue per Deal Booked in Month - Total Revenue per Listings Booked in Month You'll also note that I've included standalone metrics for booking fees, listing fees, verification fees and waiver payments. This will not be exposed in this batch 2, but based on the conversation with Finance, will clearly make it for batch 3. I just find it easier to add it now, since it's straight forward. Main changes: - `int_mtd_vs_previous_year_metrics` now computes all the above mentioned metrics - `int_monthly_aggregated_metrics_history_by_deal` now computes all the above mentioned metrics, except Total Revenue per Deal Booked in Month since it does not make sense for the deal view. Additionally, I took the opportunity to include the missing metrics from listings (accommodations). The goal is not necessarily to display them, but at least compute it on our side. Additional changes: - In `int_xero__mtd_invoicing_metrics` and `int_xero__monthly_invoicing_history_by_deal`, there's a very silly name change to keep the same convention for fees: from `xero_operator_net_fees` to `xero_operator_net_fees_in_gbp` - I applied additional changes in `int_monthly_aggregated_metrics_history_by_deal` with the goal to keep the same format as we have in `int_mtd_vs_previous_year_metrics`, this meaning: 1 - explicit alias naming (from `gj` to `guest_journeys`) 2 - keep a similar arrangement of metrics, and clearly separate scopes depending on the metric type 3 - Re-apply autoformatting Related work items: #18108, #18109, #18110
2024-07-15 07:33:55 +00:00
-- TOTAL REVENUE --
nullif(
coalesce(guest_payments.total_guest_income_in_gbp, 0)
+ coalesce(invoicing.xero_waiver_net_fees_in_gbp, 0)
+ coalesce(invoicing.xero_operator_net_fees_in_gbp, 0)
+ coalesce(invoicing.xero_apis_net_fees_in_gbp, 0),
0
) as total_revenue_in_gbp,
Merged PR 2292: Propagate invoicing metrics for KPIs This PR aims to propagate the invoicing metrics through the DWH. It does not expose them to users, yet. This PR effectively computes the following metrics, for both the "global" view (MTD) and the "by deal" view (by_deal): - Invoiced Operator Revenue - Host Resolution Count of Payments - Host Resolution Amount Paid With these 3 new metrics, we're able to combine them with the existing ones to compute: - Total Revenue - Total Revenue per Booking Created - Total Revenue per Guest Journey Created - Total Revenue per Deal Booked in Month - Total Revenue per Listings Booked in Month You'll also note that I've included standalone metrics for booking fees, listing fees, verification fees and waiver payments. This will not be exposed in this batch 2, but based on the conversation with Finance, will clearly make it for batch 3. I just find it easier to add it now, since it's straight forward. Main changes: - `int_mtd_vs_previous_year_metrics` now computes all the above mentioned metrics - `int_monthly_aggregated_metrics_history_by_deal` now computes all the above mentioned metrics, except Total Revenue per Deal Booked in Month since it does not make sense for the deal view. Additionally, I took the opportunity to include the missing metrics from listings (accommodations). The goal is not necessarily to display them, but at least compute it on our side. Additional changes: - In `int_xero__mtd_invoicing_metrics` and `int_xero__monthly_invoicing_history_by_deal`, there's a very silly name change to keep the same convention for fees: from `xero_operator_net_fees` to `xero_operator_net_fees_in_gbp` - I applied additional changes in `int_monthly_aggregated_metrics_history_by_deal` with the goal to keep the same format as we have in `int_mtd_vs_previous_year_metrics`, this meaning: 1 - explicit alias naming (from `gj` to `guest_journeys`) 2 - keep a similar arrangement of metrics, and clearly separate scopes depending on the metric type 3 - Re-apply autoformatting Related work items: #18108, #18109, #18110
2024-07-15 07:33:55 +00:00
-- GUEST REVENUE AND PAYMENTS WEIGHTED METRICS --
guest_payments.total_guest_payments_in_gbp / nullif(
guest_journeys.completed_guest_journeys, 0
) as guest_payments_per_completed_guest_journey,
guest_payments.total_guest_payments_in_gbp / nullif(
guest_journeys.paid_guest_journeys, 0
) as guest_payments_per_paid_guest_journey,
nullif(
coalesce(guest_payments.total_guest_income_in_gbp, 0)
+ coalesce(invoicing.xero_waiver_net_fees_in_gbp, 0),
0
) / nullif(
guest_journeys.completed_guest_journeys, 0
) as guest_revenue_per_completed_guest_journey,
nullif(
coalesce(guest_payments.total_guest_income_in_gbp, 0)
+ coalesce(invoicing.xero_waiver_net_fees_in_gbp, 0),
0
) / nullif(
guest_journeys.paid_guest_journeys, 0
Merged PR 2292: Propagate invoicing metrics for KPIs This PR aims to propagate the invoicing metrics through the DWH. It does not expose them to users, yet. This PR effectively computes the following metrics, for both the "global" view (MTD) and the "by deal" view (by_deal): - Invoiced Operator Revenue - Host Resolution Count of Payments - Host Resolution Amount Paid With these 3 new metrics, we're able to combine them with the existing ones to compute: - Total Revenue - Total Revenue per Booking Created - Total Revenue per Guest Journey Created - Total Revenue per Deal Booked in Month - Total Revenue per Listings Booked in Month You'll also note that I've included standalone metrics for booking fees, listing fees, verification fees and waiver payments. This will not be exposed in this batch 2, but based on the conversation with Finance, will clearly make it for batch 3. I just find it easier to add it now, since it's straight forward. Main changes: - `int_mtd_vs_previous_year_metrics` now computes all the above mentioned metrics - `int_monthly_aggregated_metrics_history_by_deal` now computes all the above mentioned metrics, except Total Revenue per Deal Booked in Month since it does not make sense for the deal view. Additionally, I took the opportunity to include the missing metrics from listings (accommodations). The goal is not necessarily to display them, but at least compute it on our side. Additional changes: - In `int_xero__mtd_invoicing_metrics` and `int_xero__monthly_invoicing_history_by_deal`, there's a very silly name change to keep the same convention for fees: from `xero_operator_net_fees` to `xero_operator_net_fees_in_gbp` - I applied additional changes in `int_monthly_aggregated_metrics_history_by_deal` with the goal to keep the same format as we have in `int_mtd_vs_previous_year_metrics`, this meaning: 1 - explicit alias naming (from `gj` to `guest_journeys`) 2 - keep a similar arrangement of metrics, and clearly separate scopes depending on the metric type 3 - Re-apply autoformatting Related work items: #18108, #18109, #18110
2024-07-15 07:33:55 +00:00
) as guest_revenue_per_paid_guest_journey,
-- TOTAL REVENUE WEIGHTED METRICS --
(
coalesce(guest_payments.total_guest_income_in_gbp, 0)
+ coalesce(invoicing.xero_waiver_net_fees_in_gbp, 0)
+ coalesce(invoicing.xero_operator_net_fees_in_gbp, 0)
+ coalesce(invoicing.xero_apis_net_fees_in_gbp, 0)
)
/ nullif(bookings.created_bookings, 0) as total_revenue_per_created_booking,
(
coalesce(guest_payments.total_guest_income_in_gbp, 0)
+ coalesce(invoicing.xero_waiver_net_fees_in_gbp, 0)
+ coalesce(invoicing.xero_operator_net_fees_in_gbp, 0)
+ coalesce(invoicing.xero_apis_net_fees_in_gbp, 0)
) / nullif(
Merged PR 2292: Propagate invoicing metrics for KPIs This PR aims to propagate the invoicing metrics through the DWH. It does not expose them to users, yet. This PR effectively computes the following metrics, for both the "global" view (MTD) and the "by deal" view (by_deal): - Invoiced Operator Revenue - Host Resolution Count of Payments - Host Resolution Amount Paid With these 3 new metrics, we're able to combine them with the existing ones to compute: - Total Revenue - Total Revenue per Booking Created - Total Revenue per Guest Journey Created - Total Revenue per Deal Booked in Month - Total Revenue per Listings Booked in Month You'll also note that I've included standalone metrics for booking fees, listing fees, verification fees and waiver payments. This will not be exposed in this batch 2, but based on the conversation with Finance, will clearly make it for batch 3. I just find it easier to add it now, since it's straight forward. Main changes: - `int_mtd_vs_previous_year_metrics` now computes all the above mentioned metrics - `int_monthly_aggregated_metrics_history_by_deal` now computes all the above mentioned metrics, except Total Revenue per Deal Booked in Month since it does not make sense for the deal view. Additionally, I took the opportunity to include the missing metrics from listings (accommodations). The goal is not necessarily to display them, but at least compute it on our side. Additional changes: - In `int_xero__mtd_invoicing_metrics` and `int_xero__monthly_invoicing_history_by_deal`, there's a very silly name change to keep the same convention for fees: from `xero_operator_net_fees` to `xero_operator_net_fees_in_gbp` - I applied additional changes in `int_monthly_aggregated_metrics_history_by_deal` with the goal to keep the same format as we have in `int_mtd_vs_previous_year_metrics`, this meaning: 1 - explicit alias naming (from `gj` to `guest_journeys`) 2 - keep a similar arrangement of metrics, and clearly separate scopes depending on the metric type 3 - Re-apply autoformatting Related work items: #18108, #18109, #18110
2024-07-15 07:33:55 +00:00
guest_journeys.created_guest_journeys, 0
) as total_revenue_per_created_guest_journey,
(
coalesce(guest_payments.total_guest_income_in_gbp, 0)
+ coalesce(invoicing.xero_waiver_net_fees_in_gbp, 0)
+ coalesce(invoicing.xero_operator_net_fees_in_gbp, 0)
+ coalesce(invoicing.xero_apis_net_fees_in_gbp, 0)
) / nullif(
Merged PR 2292: Propagate invoicing metrics for KPIs This PR aims to propagate the invoicing metrics through the DWH. It does not expose them to users, yet. This PR effectively computes the following metrics, for both the "global" view (MTD) and the "by deal" view (by_deal): - Invoiced Operator Revenue - Host Resolution Count of Payments - Host Resolution Amount Paid With these 3 new metrics, we're able to combine them with the existing ones to compute: - Total Revenue - Total Revenue per Booking Created - Total Revenue per Guest Journey Created - Total Revenue per Deal Booked in Month - Total Revenue per Listings Booked in Month You'll also note that I've included standalone metrics for booking fees, listing fees, verification fees and waiver payments. This will not be exposed in this batch 2, but based on the conversation with Finance, will clearly make it for batch 3. I just find it easier to add it now, since it's straight forward. Main changes: - `int_mtd_vs_previous_year_metrics` now computes all the above mentioned metrics - `int_monthly_aggregated_metrics_history_by_deal` now computes all the above mentioned metrics, except Total Revenue per Deal Booked in Month since it does not make sense for the deal view. Additionally, I took the opportunity to include the missing metrics from listings (accommodations). The goal is not necessarily to display them, but at least compute it on our side. Additional changes: - In `int_xero__mtd_invoicing_metrics` and `int_xero__monthly_invoicing_history_by_deal`, there's a very silly name change to keep the same convention for fees: from `xero_operator_net_fees` to `xero_operator_net_fees_in_gbp` - I applied additional changes in `int_monthly_aggregated_metrics_history_by_deal` with the goal to keep the same format as we have in `int_mtd_vs_previous_year_metrics`, this meaning: 1 - explicit alias naming (from `gj` to `guest_journeys`) 2 - keep a similar arrangement of metrics, and clearly separate scopes depending on the metric type 3 - Re-apply autoformatting Related work items: #18108, #18109, #18110
2024-07-15 07:33:55 +00:00
deals.deals_booked_in_month, 0
) as total_revenue_per_deals_booked_in_month,
(
coalesce(guest_payments.total_guest_income_in_gbp, 0)
+ coalesce(invoicing.xero_waiver_net_fees_in_gbp, 0)
+ coalesce(invoicing.xero_operator_net_fees_in_gbp, 0)
+ coalesce(invoicing.xero_apis_net_fees_in_gbp, 0)
) / nullif(
Merged PR 2292: Propagate invoicing metrics for KPIs This PR aims to propagate the invoicing metrics through the DWH. It does not expose them to users, yet. This PR effectively computes the following metrics, for both the "global" view (MTD) and the "by deal" view (by_deal): - Invoiced Operator Revenue - Host Resolution Count of Payments - Host Resolution Amount Paid With these 3 new metrics, we're able to combine them with the existing ones to compute: - Total Revenue - Total Revenue per Booking Created - Total Revenue per Guest Journey Created - Total Revenue per Deal Booked in Month - Total Revenue per Listings Booked in Month You'll also note that I've included standalone metrics for booking fees, listing fees, verification fees and waiver payments. This will not be exposed in this batch 2, but based on the conversation with Finance, will clearly make it for batch 3. I just find it easier to add it now, since it's straight forward. Main changes: - `int_mtd_vs_previous_year_metrics` now computes all the above mentioned metrics - `int_monthly_aggregated_metrics_history_by_deal` now computes all the above mentioned metrics, except Total Revenue per Deal Booked in Month since it does not make sense for the deal view. Additionally, I took the opportunity to include the missing metrics from listings (accommodations). The goal is not necessarily to display them, but at least compute it on our side. Additional changes: - In `int_xero__mtd_invoicing_metrics` and `int_xero__monthly_invoicing_history_by_deal`, there's a very silly name change to keep the same convention for fees: from `xero_operator_net_fees` to `xero_operator_net_fees_in_gbp` - I applied additional changes in `int_monthly_aggregated_metrics_history_by_deal` with the goal to keep the same format as we have in `int_mtd_vs_previous_year_metrics`, this meaning: 1 - explicit alias naming (from `gj` to `guest_journeys`) 2 - keep a similar arrangement of metrics, and clearly separate scopes depending on the metric type 3 - Re-apply autoformatting Related work items: #18108, #18109, #18110
2024-07-15 07:33:55 +00:00
accommodations.listings_booked_in_month, 0
) as total_revenue_per_listings_booked_in_month
from int_dates_mtd d
left join int_core__mtd_booking_metrics bookings on d.date = bookings.date
left join
int_core__mtd_guest_journey_metrics guest_journeys
on d.date = guest_journeys.date
left join
int_core__mtd_accommodation_metrics accommodations
on d.date = accommodations.date
left join int_core__mtd_deal_metrics deals on d.date = deals.date
left join
int_core__mtd_guest_payments_metrics guest_payments on d.date = guest_payments.date
left join int_xero__mtd_invoicing_metrics invoicing on d.date = invoicing.date
)
select
current.year,
current.month,
current.day,
current.is_end_of_month,
current.is_current_month,
current.first_day_month,
current.date,
previous_year.date as previous_year_date,
-- BOOKINGS --
{{ calculate_safe_relative_increment("created_bookings") }},
{{ calculate_safe_relative_increment("check_out_bookings") }},
{{ calculate_safe_relative_increment("cancelled_bookings") }},
{{ calculate_safe_relative_increment("billable_bookings") }},
-- GUEST JOURNEYS --
{{ calculate_safe_relative_increment("created_guest_journeys") }},
{{ calculate_safe_relative_increment("started_guest_journeys") }},
{{ calculate_safe_relative_increment("completed_guest_journeys") }},
{{ calculate_safe_relative_increment("paid_guest_journeys") }},
{{ calculate_safe_relative_increment("start_rate_guest_journey") }},
{{ calculate_safe_relative_increment("completion_rate_guest_journey") }},
{{ calculate_safe_relative_increment("incompletion_rate_guest_journey") }},
{{ calculate_safe_relative_increment("payment_rate_guest_journey") }},
-- DEALS --
{{ calculate_safe_relative_increment("new_deals") }},
{{ calculate_safe_relative_increment("never_booked_deals") }},
{{ calculate_safe_relative_increment("first_time_booked_deals") }},
{{ calculate_safe_relative_increment("active_deals") }},
{{ calculate_safe_relative_increment("churning_deals") }},
{{ calculate_safe_relative_increment("inactive_deals") }},
{{ calculate_safe_relative_increment("reactivated_deals") }},
{{ calculate_safe_relative_increment("deals_booked_in_month") }},
{{ calculate_safe_relative_increment("deals_booked_in_6_months") }},
{{ calculate_safe_relative_increment("deals_booked_in_12_months") }},
-- LISTINGS --
{{ calculate_safe_relative_increment("new_listings") }},
{{ calculate_safe_relative_increment("never_booked_listings") }},
{{ calculate_safe_relative_increment("first_time_booked_listings") }},
{{ calculate_safe_relative_increment("active_listings") }},
{{ calculate_safe_relative_increment("churning_listings") }},
{{ calculate_safe_relative_increment("inactive_listings") }},
{{ calculate_safe_relative_increment("reactivated_listings") }},
{{ calculate_safe_relative_increment("listings_booked_in_month") }},
{{ calculate_safe_relative_increment("listings_booked_in_6_months") }},
{{ calculate_safe_relative_increment("listings_booked_in_12_months") }},
Merged PR 2292: Propagate invoicing metrics for KPIs This PR aims to propagate the invoicing metrics through the DWH. It does not expose them to users, yet. This PR effectively computes the following metrics, for both the "global" view (MTD) and the "by deal" view (by_deal): - Invoiced Operator Revenue - Host Resolution Count of Payments - Host Resolution Amount Paid With these 3 new metrics, we're able to combine them with the existing ones to compute: - Total Revenue - Total Revenue per Booking Created - Total Revenue per Guest Journey Created - Total Revenue per Deal Booked in Month - Total Revenue per Listings Booked in Month You'll also note that I've included standalone metrics for booking fees, listing fees, verification fees and waiver payments. This will not be exposed in this batch 2, but based on the conversation with Finance, will clearly make it for batch 3. I just find it easier to add it now, since it's straight forward. Main changes: - `int_mtd_vs_previous_year_metrics` now computes all the above mentioned metrics - `int_monthly_aggregated_metrics_history_by_deal` now computes all the above mentioned metrics, except Total Revenue per Deal Booked in Month since it does not make sense for the deal view. Additionally, I took the opportunity to include the missing metrics from listings (accommodations). The goal is not necessarily to display them, but at least compute it on our side. Additional changes: - In `int_xero__mtd_invoicing_metrics` and `int_xero__monthly_invoicing_history_by_deal`, there's a very silly name change to keep the same convention for fees: from `xero_operator_net_fees` to `xero_operator_net_fees_in_gbp` - I applied additional changes in `int_monthly_aggregated_metrics_history_by_deal` with the goal to keep the same format as we have in `int_mtd_vs_previous_year_metrics`, this meaning: 1 - explicit alias naming (from `gj` to `guest_journeys`) 2 - keep a similar arrangement of metrics, and clearly separate scopes depending on the metric type 3 - Re-apply autoformatting Related work items: #18108, #18109, #18110
2024-07-15 07:33:55 +00:00
-- HOST (OPERATOR) REVENUE --
{{ calculate_safe_relative_increment("xero_booking_net_fees_in_gbp") }},
{{ calculate_safe_relative_increment("xero_listing_net_fees_in_gbp") }},
{{ calculate_safe_relative_increment("xero_verification_net_fees_in_gbp") }},
{{ calculate_safe_relative_increment("xero_operator_net_fees_in_gbp") }},
{{ calculate_safe_relative_increment("xero_waiver_net_fees_in_gbp") }},
-- APIs REVENUE --
{{ calculate_safe_relative_increment("xero_apis_net_fees_in_gbp") }},
{{ calculate_safe_relative_increment("xero_e_deposit_net_fees_in_gbp") }},
{{ calculate_safe_relative_increment("xero_guesty_net_fees_in_gbp") }},
Merged PR 2292: Propagate invoicing metrics for KPIs This PR aims to propagate the invoicing metrics through the DWH. It does not expose them to users, yet. This PR effectively computes the following metrics, for both the "global" view (MTD) and the "by deal" view (by_deal): - Invoiced Operator Revenue - Host Resolution Count of Payments - Host Resolution Amount Paid With these 3 new metrics, we're able to combine them with the existing ones to compute: - Total Revenue - Total Revenue per Booking Created - Total Revenue per Guest Journey Created - Total Revenue per Deal Booked in Month - Total Revenue per Listings Booked in Month You'll also note that I've included standalone metrics for booking fees, listing fees, verification fees and waiver payments. This will not be exposed in this batch 2, but based on the conversation with Finance, will clearly make it for batch 3. I just find it easier to add it now, since it's straight forward. Main changes: - `int_mtd_vs_previous_year_metrics` now computes all the above mentioned metrics - `int_monthly_aggregated_metrics_history_by_deal` now computes all the above mentioned metrics, except Total Revenue per Deal Booked in Month since it does not make sense for the deal view. Additionally, I took the opportunity to include the missing metrics from listings (accommodations). The goal is not necessarily to display them, but at least compute it on our side. Additional changes: - In `int_xero__mtd_invoicing_metrics` and `int_xero__monthly_invoicing_history_by_deal`, there's a very silly name change to keep the same convention for fees: from `xero_operator_net_fees` to `xero_operator_net_fees_in_gbp` - I applied additional changes in `int_monthly_aggregated_metrics_history_by_deal` with the goal to keep the same format as we have in `int_mtd_vs_previous_year_metrics`, this meaning: 1 - explicit alias naming (from `gj` to `guest_journeys`) 2 - keep a similar arrangement of metrics, and clearly separate scopes depending on the metric type 3 - Re-apply autoformatting Related work items: #18108, #18109, #18110
2024-07-15 07:33:55 +00:00
-- HOST RESOLUTIONS --
{{ calculate_safe_relative_increment("xero_host_resolution_amount_paid_in_gbp") }},
{{ calculate_safe_relative_increment("xero_host_resolution_payment_count") }},
-- GUEST REVENUE AND PAYMENTS --
{{ calculate_safe_relative_increment("deposit_fees_in_gbp") }},
{{ calculate_safe_relative_increment("waiver_payments_in_gbp") }},
{{ calculate_safe_relative_increment("checkin_cover_fees_in_gbp") }},
{{ calculate_safe_relative_increment("total_guest_payments_in_gbp") }},
{{ calculate_safe_relative_increment("total_guest_income_in_gbp") }},
{{ calculate_safe_relative_increment("total_guest_revenue_in_gbp") }},
Merged PR 2292: Propagate invoicing metrics for KPIs This PR aims to propagate the invoicing metrics through the DWH. It does not expose them to users, yet. This PR effectively computes the following metrics, for both the "global" view (MTD) and the "by deal" view (by_deal): - Invoiced Operator Revenue - Host Resolution Count of Payments - Host Resolution Amount Paid With these 3 new metrics, we're able to combine them with the existing ones to compute: - Total Revenue - Total Revenue per Booking Created - Total Revenue per Guest Journey Created - Total Revenue per Deal Booked in Month - Total Revenue per Listings Booked in Month You'll also note that I've included standalone metrics for booking fees, listing fees, verification fees and waiver payments. This will not be exposed in this batch 2, but based on the conversation with Finance, will clearly make it for batch 3. I just find it easier to add it now, since it's straight forward. Main changes: - `int_mtd_vs_previous_year_metrics` now computes all the above mentioned metrics - `int_monthly_aggregated_metrics_history_by_deal` now computes all the above mentioned metrics, except Total Revenue per Deal Booked in Month since it does not make sense for the deal view. Additionally, I took the opportunity to include the missing metrics from listings (accommodations). The goal is not necessarily to display them, but at least compute it on our side. Additional changes: - In `int_xero__mtd_invoicing_metrics` and `int_xero__monthly_invoicing_history_by_deal`, there's a very silly name change to keep the same convention for fees: from `xero_operator_net_fees` to `xero_operator_net_fees_in_gbp` - I applied additional changes in `int_monthly_aggregated_metrics_history_by_deal` with the goal to keep the same format as we have in `int_mtd_vs_previous_year_metrics`, this meaning: 1 - explicit alias naming (from `gj` to `guest_journeys`) 2 - keep a similar arrangement of metrics, and clearly separate scopes depending on the metric type 3 - Re-apply autoformatting Related work items: #18108, #18109, #18110
2024-07-15 07:33:55 +00:00
-- TOTAL REVENUE --
{{ calculate_safe_relative_increment("total_revenue_in_gbp") }},
-- GUEST REVENUE AND PAYMENTS WEIGHTED METRICS --
{{
calculate_safe_relative_increment(
"guest_payments_per_completed_guest_journey"
)
}},
{{ calculate_safe_relative_increment("guest_payments_per_paid_guest_journey") }},
{{ calculate_safe_relative_increment("guest_revenue_per_completed_guest_journey") }},
Merged PR 2292: Propagate invoicing metrics for KPIs This PR aims to propagate the invoicing metrics through the DWH. It does not expose them to users, yet. This PR effectively computes the following metrics, for both the "global" view (MTD) and the "by deal" view (by_deal): - Invoiced Operator Revenue - Host Resolution Count of Payments - Host Resolution Amount Paid With these 3 new metrics, we're able to combine them with the existing ones to compute: - Total Revenue - Total Revenue per Booking Created - Total Revenue per Guest Journey Created - Total Revenue per Deal Booked in Month - Total Revenue per Listings Booked in Month You'll also note that I've included standalone metrics for booking fees, listing fees, verification fees and waiver payments. This will not be exposed in this batch 2, but based on the conversation with Finance, will clearly make it for batch 3. I just find it easier to add it now, since it's straight forward. Main changes: - `int_mtd_vs_previous_year_metrics` now computes all the above mentioned metrics - `int_monthly_aggregated_metrics_history_by_deal` now computes all the above mentioned metrics, except Total Revenue per Deal Booked in Month since it does not make sense for the deal view. Additionally, I took the opportunity to include the missing metrics from listings (accommodations). The goal is not necessarily to display them, but at least compute it on our side. Additional changes: - In `int_xero__mtd_invoicing_metrics` and `int_xero__monthly_invoicing_history_by_deal`, there's a very silly name change to keep the same convention for fees: from `xero_operator_net_fees` to `xero_operator_net_fees_in_gbp` - I applied additional changes in `int_monthly_aggregated_metrics_history_by_deal` with the goal to keep the same format as we have in `int_mtd_vs_previous_year_metrics`, this meaning: 1 - explicit alias naming (from `gj` to `guest_journeys`) 2 - keep a similar arrangement of metrics, and clearly separate scopes depending on the metric type 3 - Re-apply autoformatting Related work items: #18108, #18109, #18110
2024-07-15 07:33:55 +00:00
{{ calculate_safe_relative_increment("guest_revenue_per_paid_guest_journey") }},
-- TOTAL REVENUE WEIGHTED METRICS --
{{ calculate_safe_relative_increment("total_revenue_per_created_booking") }},
{{ calculate_safe_relative_increment("total_revenue_per_created_guest_journey") }},
{{ calculate_safe_relative_increment("total_revenue_per_deals_booked_in_month") }},
{{
calculate_safe_relative_increment(
"total_revenue_per_listings_booked_in_month"
)
}}
from plain_kpi_combination current
left join
plain_kpi_combination previous_year
on current.month = previous_year.month
and current.year = previous_year.year + 1
where
(
current.is_end_of_month = 1
or (current.is_current_month = 1 and current.day = previous_year.day)
)