2024-07-08 15:58:36 +00:00
|
|
|
/*
|
|
|
|
|
This model pivots the data of the different mtd metrics models to get
|
|
|
|
|
previous year for each line & computing relative increment. --
|
|
|
|
|
*/
|
2024-08-20 15:42:27 +00:00
|
|
|
{{ config(materialized="table", unique_key=["date", "dimension", "dimension_value"]) }}
|
2024-07-08 15:58:36 +00:00
|
|
|
with
|
2024-09-16 13:02:42 +02:00
|
|
|
int_core__mtd_created_bookings_metric as (
|
|
|
|
|
select * from {{ ref("int_core__mtd_created_bookings_metric") }}
|
|
|
|
|
),
|
|
|
|
|
int_core__mtd_check_out_bookings_metric as (
|
|
|
|
|
select * from {{ ref("int_core__mtd_check_out_bookings_metric") }}
|
|
|
|
|
),
|
|
|
|
|
int_core__mtd_cancelled_bookings_metric as (
|
|
|
|
|
select * from {{ ref("int_core__mtd_cancelled_bookings_metric") }}
|
|
|
|
|
),
|
|
|
|
|
int_core__mtd_billable_bookings_metric as (
|
|
|
|
|
select * from {{ ref("int_core__mtd_billable_bookings_metric") }}
|
2024-07-08 15:58:36 +00:00
|
|
|
),
|
2024-07-09 13:00:43 +00:00
|
|
|
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") }}
|
|
|
|
|
),
|
2024-10-16 11:56:49 +00:00
|
|
|
int_mtd_deal_metrics as (select * from {{ ref("int_mtd_deal_metrics") }}),
|
2024-07-29 09:10:58 +00:00
|
|
|
int_core__mtd_guest_payments_metrics as (
|
|
|
|
|
select * from {{ ref("int_core__mtd_guest_payments_metrics") }}
|
2024-07-10 08:52:19 +00:00
|
|
|
),
|
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 (
|
2024-07-19 07:30:42 +00:00
|
|
|
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
|
|
|
),
|
2024-10-15 10:46:56 +00:00
|
|
|
int_monthly_churn_metrics as (select * from {{ ref("int_monthly_churn_metrics") }}),
|
2024-09-16 13:02:42 +02:00
|
|
|
int_dates_mtd_by_dimension as (
|
|
|
|
|
select * from {{ ref("int_dates_mtd_by_dimension") }}
|
|
|
|
|
),
|
2024-07-08 15:58:36 +00:00
|
|
|
|
|
|
|
|
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
|
|
|
|
2024-07-08 15:58:36 +00:00
|
|
|
select
|
|
|
|
|
d.year,
|
|
|
|
|
d.month,
|
|
|
|
|
d.day,
|
|
|
|
|
d.is_end_of_month,
|
|
|
|
|
d.is_current_month,
|
2024-07-16 09:14:38 +00:00
|
|
|
d.first_day_month,
|
2024-07-08 15:58:36 +00:00
|
|
|
d.date,
|
2024-08-20 15:42:27 +00:00
|
|
|
d.dimension,
|
|
|
|
|
d.dimension_value,
|
2024-07-09 13:00:43 +00:00
|
|
|
|
|
|
|
|
-- BOOKINGS --
|
2024-09-16 13:02:42 +02:00
|
|
|
created_bookings.created_bookings,
|
|
|
|
|
check_out_bookings.check_out_bookings,
|
|
|
|
|
cancelled_bookings.cancelled_bookings,
|
|
|
|
|
billable_bookings.billable_bookings,
|
2024-07-09 13:00:43 +00:00
|
|
|
|
|
|
|
|
-- 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,
|
2024-07-10 08:52:19 +00:00
|
|
|
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,
|
|
|
|
|
|
2024-07-19 07:30:42 +00:00
|
|
|
-- 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,
|
|
|
|
|
|
2024-07-10 08:52:19 +00:00
|
|
|
-- GUEST REVENUE AND PAYMENTS --
|
2024-07-29 09:10:58 +00:00
|
|
|
guest_payments.deposit_fees_in_gbp,
|
|
|
|
|
guest_payments.waiver_payments_in_gbp,
|
2024-07-29 13:16:19 +00:00
|
|
|
invoicing.xero_waiver_paid_back_to_host_in_gbp,
|
|
|
|
|
nullif(
|
|
|
|
|
coalesce(guest_payments.waiver_payments_in_gbp, 0)
|
|
|
|
|
+ coalesce(invoicing.xero_waiver_paid_back_to_host_in_gbp, 0),
|
|
|
|
|
0
|
|
|
|
|
) as waiver_net_fees_in_gbp,
|
2024-07-29 09:10:58 +00:00
|
|
|
guest_payments.checkin_cover_fees_in_gbp,
|
|
|
|
|
guest_payments.total_guest_payments_in_gbp,
|
2024-07-10 08:52:19 +00:00
|
|
|
|
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 --
|
2024-07-19 09:14:30 +00:00
|
|
|
nullif(
|
2024-07-29 15:15:09 +00:00
|
|
|
coalesce(guest_payments.total_guest_payments_in_gbp, 0)
|
2024-07-19 09:14:30 +00:00
|
|
|
+ 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 --
|
2024-07-29 09:10:58 +00:00
|
|
|
guest_payments.total_guest_payments_in_gbp / nullif(
|
2024-07-10 08:52:19 +00:00
|
|
|
guest_journeys.completed_guest_journeys, 0
|
|
|
|
|
) as guest_payments_per_completed_guest_journey,
|
2024-07-29 09:10:58 +00:00
|
|
|
guest_payments.total_guest_payments_in_gbp / nullif(
|
2024-07-10 08:52:19 +00:00
|
|
|
guest_journeys.paid_guest_journeys, 0
|
|
|
|
|
) as guest_payments_per_paid_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
|
|
|
|
|
|
|
|
-- TOTAL REVENUE WEIGHTED METRICS --
|
2024-07-19 07:30:42 +00:00
|
|
|
(
|
2024-07-29 15:15:09 +00:00
|
|
|
coalesce(guest_payments.total_guest_payments_in_gbp, 0)
|
2024-07-19 09:14:30 +00:00
|
|
|
+ coalesce(invoicing.xero_operator_net_fees_in_gbp, 0)
|
|
|
|
|
+ coalesce(invoicing.xero_apis_net_fees_in_gbp, 0)
|
2024-09-16 13:02:42 +02:00
|
|
|
) / nullif(
|
|
|
|
|
created_bookings.created_bookings, 0
|
|
|
|
|
) as total_revenue_per_created_booking,
|
2024-07-19 07:30:42 +00:00
|
|
|
(
|
2024-07-29 15:15:09 +00:00
|
|
|
coalesce(guest_payments.total_guest_payments_in_gbp, 0)
|
2024-07-19 09:14:30 +00:00
|
|
|
+ coalesce(invoicing.xero_operator_net_fees_in_gbp, 0)
|
|
|
|
|
+ coalesce(invoicing.xero_apis_net_fees_in_gbp, 0)
|
2024-07-19 07:30:42 +00:00
|
|
|
) / 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,
|
2024-07-19 07:30:42 +00:00
|
|
|
(
|
2024-07-29 15:15:09 +00:00
|
|
|
coalesce(guest_payments.total_guest_payments_in_gbp, 0)
|
2024-07-19 09:14:30 +00:00
|
|
|
+ coalesce(invoicing.xero_operator_net_fees_in_gbp, 0)
|
|
|
|
|
+ coalesce(invoicing.xero_apis_net_fees_in_gbp, 0)
|
2024-07-19 07:30:42 +00:00
|
|
|
) / 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,
|
2024-07-19 07:30:42 +00:00
|
|
|
(
|
2024-07-29 15:15:09 +00:00
|
|
|
coalesce(guest_payments.total_guest_payments_in_gbp, 0)
|
2024-07-19 09:14:30 +00:00
|
|
|
+ coalesce(invoicing.xero_operator_net_fees_in_gbp, 0)
|
|
|
|
|
+ coalesce(invoicing.xero_apis_net_fees_in_gbp, 0)
|
2024-07-19 07:30:42 +00:00
|
|
|
) / 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
|
2024-10-15 10:46:56 +00:00
|
|
|
) as total_revenue_per_listings_booked_in_month,
|
|
|
|
|
|
|
|
|
|
-- CHURN --
|
|
|
|
|
churn.total_revenue_churn_average_contribution,
|
|
|
|
|
churn.created_bookings_churn_average_contribution,
|
|
|
|
|
churn.listings_booked_in_month_churn_average_contribution
|
2024-07-09 13:00:43 +00:00
|
|
|
|
2024-08-20 15:42:27 +00:00
|
|
|
from int_dates_mtd_by_dimension d
|
2024-09-16 13:02:42 +02:00
|
|
|
left join
|
|
|
|
|
int_core__mtd_created_bookings_metric created_bookings
|
|
|
|
|
on d.date = created_bookings.date
|
|
|
|
|
and d.dimension = created_bookings.dimension
|
|
|
|
|
and d.dimension_value = created_bookings.dimension_value
|
|
|
|
|
left join
|
|
|
|
|
int_core__mtd_check_out_bookings_metric check_out_bookings
|
|
|
|
|
on d.date = check_out_bookings.date
|
|
|
|
|
and d.dimension = check_out_bookings.dimension
|
|
|
|
|
and d.dimension_value = check_out_bookings.dimension_value
|
|
|
|
|
left join
|
|
|
|
|
int_core__mtd_cancelled_bookings_metric cancelled_bookings
|
|
|
|
|
on d.date = cancelled_bookings.date
|
|
|
|
|
and d.dimension = cancelled_bookings.dimension
|
|
|
|
|
and d.dimension_value = cancelled_bookings.dimension_value
|
|
|
|
|
left join
|
|
|
|
|
int_core__mtd_billable_bookings_metric billable_bookings
|
|
|
|
|
on d.date = billable_bookings.date
|
|
|
|
|
and d.dimension = billable_bookings.dimension
|
|
|
|
|
and d.dimension_value = billable_bookings.dimension_value
|
2024-07-19 07:30:42 +00:00
|
|
|
left join
|
|
|
|
|
int_core__mtd_guest_journey_metrics guest_journeys
|
2024-07-09 13:00:43 +00:00
|
|
|
on d.date = guest_journeys.date
|
2024-08-20 15:42:27 +00:00
|
|
|
and d.dimension = guest_journeys.dimension
|
|
|
|
|
and d.dimension_value = guest_journeys.dimension_value
|
2024-07-19 07:30:42 +00:00
|
|
|
left join
|
|
|
|
|
int_core__mtd_accommodation_metrics accommodations
|
2024-07-09 13:00:43 +00:00
|
|
|
on d.date = accommodations.date
|
2024-08-20 15:42:27 +00:00
|
|
|
and d.dimension = accommodations.dimension
|
|
|
|
|
and d.dimension_value = accommodations.dimension_value
|
2024-09-16 13:02:42 +02:00
|
|
|
left join
|
2024-10-16 11:56:49 +00:00
|
|
|
int_mtd_deal_metrics deals
|
2024-08-20 15:42:27 +00:00
|
|
|
on d.date = deals.date
|
|
|
|
|
and d.dimension = deals.dimension
|
|
|
|
|
and d.dimension_value = deals.dimension_value
|
2024-07-19 07:30:42 +00:00
|
|
|
left join
|
2024-09-16 13:02:42 +02:00
|
|
|
int_core__mtd_guest_payments_metrics guest_payments
|
2024-08-20 15:42:27 +00:00
|
|
|
on d.date = guest_payments.date
|
|
|
|
|
and d.dimension = guest_payments.dimension
|
|
|
|
|
and d.dimension_value = guest_payments.dimension_value
|
2024-09-16 13:02:42 +02:00
|
|
|
left join
|
|
|
|
|
int_xero__mtd_invoicing_metrics invoicing
|
2024-08-20 15:42:27 +00:00
|
|
|
on d.date = invoicing.date
|
|
|
|
|
and d.dimension = invoicing.dimension
|
|
|
|
|
and d.dimension_value = invoicing.dimension_value
|
2024-10-15 10:46:56 +00:00
|
|
|
left join
|
|
|
|
|
int_monthly_churn_metrics churn
|
|
|
|
|
on d.date = churn.date
|
|
|
|
|
and d.dimension = churn.dimension
|
|
|
|
|
and d.dimension_value = churn.dimension_value
|
2024-07-08 15:58:36 +00:00
|
|
|
)
|
|
|
|
|
select
|
|
|
|
|
current.year,
|
|
|
|
|
current.month,
|
|
|
|
|
current.day,
|
|
|
|
|
current.is_end_of_month,
|
|
|
|
|
current.is_current_month,
|
2024-07-16 09:14:38 +00:00
|
|
|
current.first_day_month,
|
2024-07-08 15:58:36 +00:00
|
|
|
current.date,
|
2024-08-20 15:42:27 +00:00
|
|
|
current.dimension,
|
|
|
|
|
current.dimension_value,
|
2024-07-08 15:58:36 +00:00
|
|
|
previous_year.date as previous_year_date,
|
|
|
|
|
|
|
|
|
|
-- BOOKINGS --
|
2024-07-10 08:52:19 +00:00
|
|
|
{{ calculate_safe_relative_increment("created_bookings") }},
|
|
|
|
|
{{ calculate_safe_relative_increment("check_out_bookings") }},
|
|
|
|
|
{{ calculate_safe_relative_increment("cancelled_bookings") }},
|
2024-07-15 12:32:18 +00:00
|
|
|
{{ calculate_safe_relative_increment("billable_bookings") }},
|
2024-07-09 13:00:43 +00:00
|
|
|
|
|
|
|
|
-- GUEST JOURNEYS --
|
2024-07-10 08:52:19 +00:00
|
|
|
{{ 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") }},
|
2024-07-09 13:00:43 +00:00
|
|
|
|
|
|
|
|
-- DEALS --
|
2024-07-10 08:52:19 +00:00
|
|
|
{{ 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") }},
|
2024-07-09 13:00:43 +00:00
|
|
|
|
|
|
|
|
-- LISTINGS --
|
2024-07-10 08:52:19 +00:00
|
|
|
{{ 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") }},
|
|
|
|
|
|
2024-07-19 07:30:42 +00:00
|
|
|
-- 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") }},
|
|
|
|
|
|
Merged PR 3124: 1/3 - Revenue renaming Main KPIs - MTD scope
# Description
Adapts revenue figures in Main KPIs - MTD scope or global view. This includes MTD, Monthly Overview, Global Evolution over Time, Detail by Category. In essence, everything that is not by deal.
The changes are mainly 2:
* Remove the line that deducts the `Waiver Amount Paid Back to Hosts` in all metrics except the `Waiver Net Fees`. This effectively means that the previous `Guest Revenue` = `Guest Payments`, thus I dropped all 3 `Guest Payments` metrics.
* Do a renaming at metric display level, but not in the code. This means that I remove the computation of `guest_revenue_in_gbp` for instance and keep `guest_payments_in_gbp`, and apply the renaming later on, since the modelisation already accounts for defining metric names differently from those of the fields. For the rest of metrics, I revised all metrics name and did changes based on the [whiteboard](https://whiteboard.office.com/me/whiteboards/p/c3BvOmh0dHBzOi8vZ3VhcmRob2ctbXkuc2hhcmVwb2ludC5jb20vcGVyc29uYWwvcGFibG9fbWFydGluX3N1cGVyaG9nX2NvbQ%3d%3d/b!T2D3opQuBECSDnhuFZrUacFu3TxvSvdIsnI4Dxsh2IuaB1AigbciRqkqte61I4wz/01H5SI4J4L7HTPJGUT7JGYKTOSQYYWACXU). I also changed the dedicated data tests in Main KPIs to ensure it's working. I also changed the exclusion logic in reporting based on the name of the metric to not display metrics that depend on the invoicing cycle unless it's 2 months ago or before.
To keep in mind:
* Merging this will automatically display the new figures/naming in production. Might be wise to communicate to stakeholders since some key metrics (namely, Guest Revenue / Total Revenue) will change the meaning.
* We also need to do these changes in the metrics by deal part of the computation. I'd do first the removal of these fields in the PBI report (and take the opportunity to change the Data Catalogue) and then do the PR in DWH to change the logic. Before that though let's check that the names included in this PR are the correct ones :)
# Checklist
- [X] The edited models and dependants run properly with production data.
- [NA] The edited models are sufficiently documented.
- [X] The edited models contain PK tests, and I've ran and passed them.
- [NA] I have checked for DRY opportunities with other models and docs.
- [NA] I've picked the right materialization for the affected models.
# Other
- [ ] Check if a full-refresh is required after this PR is merged.
Related work items: #22688
2024-10-10 13:46:59 +00:00
|
|
|
-- GUEST REVENUE --
|
2024-07-23 13:50:03 +00:00
|
|
|
{{ calculate_safe_relative_increment("deposit_fees_in_gbp") }},
|
|
|
|
|
{{ calculate_safe_relative_increment("waiver_payments_in_gbp") }},
|
2024-07-29 13:16:19 +00:00
|
|
|
{{ calculate_safe_relative_increment("xero_waiver_paid_back_to_host_in_gbp") }},
|
|
|
|
|
{{ calculate_safe_relative_increment("waiver_net_fees_in_gbp") }},
|
2024-07-23 13:50:03 +00:00
|
|
|
{{ calculate_safe_relative_increment("checkin_cover_fees_in_gbp") }},
|
2024-07-10 08:52:19 +00:00
|
|
|
{{ calculate_safe_relative_increment("total_guest_payments_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") }},
|
|
|
|
|
|
Merged PR 3124: 1/3 - Revenue renaming Main KPIs - MTD scope
# Description
Adapts revenue figures in Main KPIs - MTD scope or global view. This includes MTD, Monthly Overview, Global Evolution over Time, Detail by Category. In essence, everything that is not by deal.
The changes are mainly 2:
* Remove the line that deducts the `Waiver Amount Paid Back to Hosts` in all metrics except the `Waiver Net Fees`. This effectively means that the previous `Guest Revenue` = `Guest Payments`, thus I dropped all 3 `Guest Payments` metrics.
* Do a renaming at metric display level, but not in the code. This means that I remove the computation of `guest_revenue_in_gbp` for instance and keep `guest_payments_in_gbp`, and apply the renaming later on, since the modelisation already accounts for defining metric names differently from those of the fields. For the rest of metrics, I revised all metrics name and did changes based on the [whiteboard](https://whiteboard.office.com/me/whiteboards/p/c3BvOmh0dHBzOi8vZ3VhcmRob2ctbXkuc2hhcmVwb2ludC5jb20vcGVyc29uYWwvcGFibG9fbWFydGluX3N1cGVyaG9nX2NvbQ%3d%3d/b!T2D3opQuBECSDnhuFZrUacFu3TxvSvdIsnI4Dxsh2IuaB1AigbciRqkqte61I4wz/01H5SI4J4L7HTPJGUT7JGYKTOSQYYWACXU). I also changed the dedicated data tests in Main KPIs to ensure it's working. I also changed the exclusion logic in reporting based on the name of the metric to not display metrics that depend on the invoicing cycle unless it's 2 months ago or before.
To keep in mind:
* Merging this will automatically display the new figures/naming in production. Might be wise to communicate to stakeholders since some key metrics (namely, Guest Revenue / Total Revenue) will change the meaning.
* We also need to do these changes in the metrics by deal part of the computation. I'd do first the removal of these fields in the PBI report (and take the opportunity to change the Data Catalogue) and then do the PR in DWH to change the logic. Before that though let's check that the names included in this PR are the correct ones :)
# Checklist
- [X] The edited models and dependants run properly with production data.
- [NA] The edited models are sufficiently documented.
- [X] The edited models contain PK tests, and I've ran and passed them.
- [NA] I have checked for DRY opportunities with other models and docs.
- [NA] I've picked the right materialization for the affected models.
# Other
- [ ] Check if a full-refresh is required after this PR is merged.
Related work items: #22688
2024-10-10 13:46:59 +00:00
|
|
|
-- GUEST REVENUE WEIGHTED METRICS --
|
2024-07-19 07:30:42 +00:00
|
|
|
{{
|
|
|
|
|
calculate_safe_relative_increment(
|
|
|
|
|
"guest_payments_per_completed_guest_journey"
|
|
|
|
|
)
|
|
|
|
|
}},
|
2024-07-10 08:52:19 +00:00
|
|
|
{{ calculate_safe_relative_increment("guest_payments_per_paid_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
|
|
|
|
|
|
|
|
-- TOTAL REVENUE WEIGHTED METRICS --
|
2024-07-19 07:30:42 +00:00
|
|
|
{{ 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"
|
|
|
|
|
)
|
2024-10-15 10:46:56 +00:00
|
|
|
}},
|
|
|
|
|
|
|
|
|
|
-- CHURN --
|
|
|
|
|
{{ calculate_safe_relative_increment("total_revenue_churn_average_contribution") }},
|
|
|
|
|
{{
|
|
|
|
|
calculate_safe_relative_increment(
|
|
|
|
|
"created_bookings_churn_average_contribution"
|
|
|
|
|
)
|
|
|
|
|
}},
|
|
|
|
|
{{
|
|
|
|
|
calculate_safe_relative_increment(
|
|
|
|
|
"listings_booked_in_month_churn_average_contribution"
|
|
|
|
|
)
|
2024-07-19 07:30:42 +00:00
|
|
|
}}
|
2024-07-08 15:58:36 +00:00
|
|
|
|
|
|
|
|
from plain_kpi_combination current
|
2024-07-10 08:52:19 +00:00
|
|
|
left join
|
|
|
|
|
plain_kpi_combination previous_year
|
2024-09-16 13:02:42 +02:00
|
|
|
on current.dimension = previous_year.dimension
|
2024-08-20 15:42:27 +00:00
|
|
|
and current.dimension_value = previous_year.dimension_value
|
|
|
|
|
and current.month = previous_year.month
|
2024-07-08 15:58:36 +00:00
|
|
|
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)
|
|
|
|
|
)
|