rebase and updated schema
This commit is contained in:
parent
6b5b7d2d5a
commit
68644630d4
1 changed files with 0 additions and 79 deletions
|
|
@ -5304,85 +5304,6 @@ models:
|
||||||
Sum of total payments paid by guests, excluding taxes, in GBP
|
Sum of total payments paid by guests, excluding taxes, in GBP
|
||||||
on the same date in the previous year, segmented by the specified dimension.
|
on the same date in the previous year, segmented by the specified dimension.
|
||||||
|
|
||||||
- name: int_kpis__product_guest_agg_metrics
|
|
||||||
description:
|
|
||||||
This model aggregates multiple metrics on a Year-to-date, Month-to-date or
|
|
||||||
Week-to-date basis. This model changes the display format of the model
|
|
||||||
int_kpis__product_guest_daily_metrics pivoting the metrics columns and
|
|
||||||
adding a timeframe dimension.
|
|
||||||
columns:
|
|
||||||
- name: metric
|
|
||||||
data_type: text
|
|
||||||
description: Name of the business metric
|
|
||||||
|
|
||||||
- name: has_payment
|
|
||||||
data_type: string
|
|
||||||
description: Has there been any guest payments on the guest journey.
|
|
||||||
tests:
|
|
||||||
- not_null
|
|
||||||
- accepted_values:
|
|
||||||
values:
|
|
||||||
- W/O Payment
|
|
||||||
- With Payment
|
|
||||||
|
|
||||||
- name: has_id_check
|
|
||||||
data_type: string
|
|
||||||
description: Does the verification in the guest journey
|
|
||||||
includes Government Id Check for the bookings.
|
|
||||||
tests:
|
|
||||||
- not_null
|
|
||||||
- accepted_values:
|
|
||||||
values:
|
|
||||||
- W/O Id Check
|
|
||||||
- With Id Check
|
|
||||||
|
|
||||||
- name: main_billing_country_iso_3_per_deal
|
|
||||||
data_type: string
|
|
||||||
description: |
|
|
||||||
Main billing country of the host aggregated at Deal level.
|
|
||||||
tests:
|
|
||||||
- not_null
|
|
||||||
|
|
||||||
- name: timeframe
|
|
||||||
data_type: text
|
|
||||||
description: |
|
|
||||||
Timeframe considered for the aggregation, it could be Year-to-date,
|
|
||||||
Month-to-date or Week-to-date
|
|
||||||
tests:
|
|
||||||
- not_null
|
|
||||||
- accepted_values:
|
|
||||||
values:
|
|
||||||
- YTD
|
|
||||||
- MTD
|
|
||||||
- WTD
|
|
||||||
|
|
||||||
- name: current_value
|
|
||||||
data_type: numeric
|
|
||||||
description: |
|
|
||||||
Numeric value (integer or decimal) that corresponds to the timeframe
|
|
||||||
computation of the metric at the current date.
|
|
||||||
For example if the current date is 27/11/2024 and the timeframe is MTD,
|
|
||||||
then this value would correspond to the computation of the metric for
|
|
||||||
the dates between 01/11/2024 and 27/11/2024.
|
|
||||||
|
|
||||||
- name: py_value
|
|
||||||
data_type: numeric
|
|
||||||
description: |
|
|
||||||
Numeric value (integer or decimal) that corresponds to the timeframe
|
|
||||||
computation of the metric at the current date but on the previous year.
|
|
||||||
For example if the current date is 27/11/2024 and the timeframe is MTD,
|
|
||||||
then this value would correspond to the computation of the metric for
|
|
||||||
the dates between 01/11/2023 and 27/11/2023.
|
|
||||||
|
|
||||||
- name: pp_value
|
|
||||||
data_type: numeric
|
|
||||||
description: |
|
|
||||||
Numeric value (integer or decimal) that corresponds to the timeframe
|
|
||||||
computation of the metric at the current date but on the previous period.
|
|
||||||
For example if the current date is 27/11/2024 and the timeframe is MTD,
|
|
||||||
then this value would correspond to the computation of the metric for
|
|
||||||
the dates between 01/10/2024 and 27/10/2024.
|
|
||||||
|
|
||||||
- name: int_kpis__metric_daily_new_dash_created_services
|
- name: int_kpis__metric_daily_new_dash_created_services
|
||||||
description: |
|
description: |
|
||||||
This model computes the Daily Created Services at the deepest granularity.
|
This model computes the Daily Created Services at the deepest granularity.
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue