sh-notion/notion_data_team_no_files/2025-02-19 - Data Planning 19e0446ff9c98063be3df87905cc8ca4.md
Pablo Martin a256b48b01 pages
2025-07-11 16:15:17 +02:00

45 lines
No EOL
3.4 KiB
Markdown
Raw Permalink Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

# 2025-02-19 - Data Planning
### General Updates
- Uri off on Friday 21st (reminder)
### Done
- KPIs - New Dash vs. Old Dash (vs. API) category ([Main KPIs report](https://app.powerbi.com/groups/me/apps/33e55130-3a65-4fe8-86f2-11979fb2258a/reports/5ceb1ad4-5b87-470b-806d-59ea0b8f2661/cabe954bba6d285c576f?experience=power-bi))
- KPIs - Implement Live Deals ([Main KPIs report](https://app.powerbi.com/groups/me/apps/33e55130-3a65-4fe8-86f2-11979fb2258a/reports/5ceb1ad4-5b87-470b-806d-59ea0b8f2661/cabe954bba6d285c576f?experience=power-bi))
- KPIs - Implement Billable Booking KPI for new dash after definition ([Main KPIs report](https://app.powerbi.com/groups/me/apps/33e55130-3a65-4fe8-86f2-11979fb2258a/reports/5ceb1ad4-5b87-470b-806d-59ea0b8f2661/cabe954bba6d285c576f?experience=power-bi))
- Product/RevOps - Include a user adoption funnel per service for New Dash, to identify adoption/upsell possibilities ([New Dash - Offered Services report](https://app.powerbi.com/groups/me/apps/d6a99cb6-fad1-4e92-bce1-254dcff0d9a2/reports/44d8eee3-e1e6-474a-9626-868a5756ba83/99f744c80b91c605a7a1?ctid=862842df-2998-4826-bea9-b726bc01d3a7&experience=power-bi))
- Ad hoc requests, specially on Home Team Vacations Rentals (Kayla) → Risk of losing Booking fees after decrease from 10 USD to 6 USD
- Guests - Align for Illustrations A/B test launching next week
- Resolutions - Ingest Resolution Centre Data into DWH
- Data internal - Fixed CPU consumption
- Data internal - Fixed New Dash Reporting being down after release
### In Progress
- Finance - Screen and Protect API reporting for invoicing purposes
- Other - Excel tips and best practices documentation (reviewed) - How do you want to proceed? Share resources and/or schedule session? → Session + Resources
- KPIs - Main KPIs overview (YTD+MTD) - First partial delivery
### Stopped / No advancement
- KPIs/New Dash/AM reporting - Exclude known test accounts to increase data quality (wont remove all of them) - Engineering to built it properly for us to exclude it properly
- Guests - Start discussing on the implementation for Guest Products and Single Payment - Multi Service refactor. (No further news)
### To Do (does not include critical subjects)
- Report to support Pass The Keys migration to New Dash
- Resolutions - DWH modelling
- KPIs - Main KPIs overview (YTD+MTD) - Second delivery
- Creation of APIs KPIs (for Bookings mostly)
- Revenue Churn & MRR metrics
- Targets
- Guests - Adapt A/B test monitoring with specs of Illustrations A/B test
- Finance - Update legacy (old dash) invoicing exporter to show unit price and quantity besides total price + Deal id
- Resolutions - Reporting
- Invoicing Incident - Further automation improvements: Xero (for source of truth in actual invoiced amount) + Hubspot (for churn/onboarding/AM info) + Backend (for what we should have invoiced, New Dash mostly)
- KPIs - Payment Count and Average Amount per Payment Count (Waiver/Deposit Fee/etc)
- RevOps (Kayla) - Churn prevention: alerting system if user had a PMS and no longer has it, if recent created bookings per account is decreasing, display last time account was contacted. This could be potentially the first step towards a “Account Manager KPIs” for AM teams
- RevOps (Kayla) - Churn tracking: see if we can automate manual monthly Churn reports and enhance it with other data (revenue last 12 m, etc)
- RevOps (Alex) - Client Cohorts: explore retention + key metrics to understand if its valuable for further client understanding