1781031c9d
Adds the following metrics: - Guest Journey with Payment - Guest Journey Payment Rate by both visions (global and by deal id) **Important**: it does not expose these metrics to the dashboard, this will be done after we have feedback from Ben R. on the paid GJ without GJ completeness. Missing steps to make them appear is to adapt `int_core__mtd_aggregated_metrics` and `int_core__monthly_aggregated_metrics_history_by_deal` and the respective reporting counterparts. It adapts: - `int_core__mtd_guest_journey_metrics` - `int_core__monthly_guest_journey_history_by_deal` the approaches are similar in the sense that we join with `int_core__verification_payments` and filter by a PAID status, that has been defined in the `dbt_project.yml` in a similar manner as we did with cancelled bookings. It can happen that the same verification request has multiple payments (see screenshot), which in this case we keep the first date in which the paid payment happens. The volume is quite low anyway.  code for the screenshot: ``` with pre as ( select id_verification_request, count(distinct icvp.id_payment) as total_paid_payments from intermediate.int_core__verification_payments icvp where icvp.payment_status = 'Paid' group by 1 ) select case when total_paid_payments > 2 then 'more than 2' when total_paid_payments = 2 then '2' when total_paid_payments = 1 then '1' end as payment_volume_category, count(1) as vr_volume from pre group by 1 order by 2 desc ``` I also added a missing reference in `schema.yaml` int about `int_core__mtd_guest_journey_metrics` Related work items: #18105
60 lines
No EOL
1.8 KiB
YAML
60 lines
No EOL
1.8 KiB
YAML
# Name your project! Project names should contain only lowercase characters
|
|
# and underscores. A good package name should reflect your organization's
|
|
# name or the intended use of these models
|
|
name: "dwh_dbt"
|
|
version: "1.0.0"
|
|
config-version: 2
|
|
|
|
# This setting configures which "profile" dbt uses for this project.
|
|
profile: "dwh_dbt"
|
|
|
|
# These configurations specify where dbt should look for different types of files.
|
|
# The `model-paths` config, for example, states that models in this project can be
|
|
# found in the "models/" directory. You probably won't need to change these!
|
|
model-paths: ["models"]
|
|
analysis-paths: ["analyses"]
|
|
test-paths: ["tests"]
|
|
seed-paths: ["seeds"]
|
|
macro-paths: ["macros"]
|
|
snapshot-paths: ["snapshots"]
|
|
|
|
clean-targets: # directories to be removed by `dbt clean`
|
|
- "target"
|
|
- "dbt_packages"
|
|
|
|
# Configuring models
|
|
# Full documentation: https://docs.getdbt.com/docs/configuring-models
|
|
|
|
# In this example config, we tell dbt to build all models in the example/
|
|
# directory as views. These settings can be overridden in the individual model
|
|
# files using the `{{ config(...) }}` macro.
|
|
models:
|
|
+unlogged: true
|
|
dwh_dbt:
|
|
staging:
|
|
+materialized: table
|
|
+schema: staging
|
|
intermediate:
|
|
+materialized: view
|
|
+schema: intermediate
|
|
reporting:
|
|
+materialized: table
|
|
+schema: reporting
|
|
|
|
seeds:
|
|
dwh_dbt:
|
|
schema: staging
|
|
|
|
vars:
|
|
"dbt_date:time_zone": "Europe/London"
|
|
# A general cutoff date for relevancy. Many models assume this to be the point
|
|
# in time after which they should work.
|
|
"start_date": "'2020-01-01'"
|
|
|
|
# Booking state variables
|
|
# States should be strings in capital letters. Models need to force an upper()
|
|
"cancelled_booking_state": "'CANCELLED'"
|
|
|
|
# Payment state variables
|
|
# States should be strings in capital letters. Models need to force an upper()
|
|
"paid_payment_state": "'PAID'" |