Skip to main content

Alert Level Metrics vs Dashboard Table Columns Comparison

Overview

This document provides a comprehensive comparison between the metrics available in the alert creation system and the actual columns available in the corresponding dashboard tables. This analysis helps ensure that alert configurations are accurate and that users can only create alerts for metrics that actually exist in the data.

Data Sources

  • Ad Level: dm_dashboard.ad_daily_dashboard
  • Campaign Level: dm_dashboard.campaign_daily_dashboard
  • Account Level: app.daily_metrics ⚠️ UPDATED

Summary Table

Metric CategoryAd LevelCampaign LevelAccount LevelStatus
Financial Metrics18 metrics18 metrics16 metricsUPDATED - Account now has more financial metrics
Advertising Metrics11 metrics11 metrics3 metricsUPDATED - Account now has basic advertising metrics
Leads Metrics9 metrics9 metrics7 metricsUPDATED - Account streamlined for daily_metrics
Bookings Metrics16 metrics16 metrics17 metricsUPDATED - Account has comprehensive booking metrics
Sales Metrics7 metrics7 metrics20 metricsUPDATED - Account has extensive sales metrics
Applications Metrics8 metrics8 metrics11 metricsUPDATED - Account has additional qualified app metrics
Cash Metrics0 metrics0 metrics6 metricsNEW - Account has dedicated cash tracking
Conversion Rates18 metrics18 metrics21 metricsUPDATED - Account has additional conversion rates

⚠️ IMPORTANT CHANGE

Account Level Data Source Updated: The account level alert system now uses app.daily_metrics instead of dm_dashboard.channel_daily_dashboard. This change provides:

  • More comprehensive metrics from the daily_metrics table
  • Better alignment with actual data structure
  • Additional cash tracking metrics not available in channel_daily_dashboard
  • Streamlined metric categories optimized for daily_metrics structure

Detailed Comparison

Financial Metrics

MetricAd LevelCampaign LevelAccount LevelNotes
spendTotal advertising spend
net_cashNet cash collected (including refunds)
net_cash_FENet cash from front-end products (Account only)
net_cash_BENet cash from back-end products (Account only)
projected_spendProjected advertising spend for the period
projected_net_cashProjected net cash for the period
projected_roasProjected return on ad spend
e_cash_l30Expected cash from bookings in last 30 days
e_cash_30dExpected cash from bookings within 30 days
e_roas_l30Expected ROAS from last 30 days
e_roas_30dExpected ROAS within 30 days
e_roas_2dExpected ROAS for bookings in next 2 days (Missing in Account)
e_roas_7dExpected ROAS for bookings in next 7 days (Missing in Account)
roas_30d30-day Return on Ad Spend
roasOverall Return on Ad Spend
ltvCustomer Lifetime Value
acvAverage Contract Value
cacCustomer Acquisition Cost

Advertising Metrics

MetricAd LevelCampaign LevelAccount LevelNotes
impressionsMISSING in Account level
cpmMISSING in Account level
link_clicksMISSING in Account level
cpcMISSING in Account level
ctrMISSING in Account level
landing_page_viewMISSING in Account level
cplpvMISSING in Account level
post_engagementMISSING in Account level
cppeMISSING in Account level
video_p50_watchedMISSING in Account level
frequencyMISSING in Account level

Leads Metrics

MetricAd LevelCampaign LevelAccount LevelNotes
num_leadsTotal number of leads generated
num_qualified_leadsNumber of leads marked as qualified (SAL)
num_mqlsNumber of Marketing Qualified Leads
num_mqls_setNumber of MQLs with set appointments (Account only)
num_mqls_not_setNumber of MQLs without set appointments (Account only)
p_lead_to_mqlConversion rate from lead to MQL
median_time_from_lead_to_booking_creationMedian time from lead creation to booking creation
median_time_from_application_to_booking_creationMedian time from application to booking creation
avg_time_mql_to_sql_in_hoursAverage time from MQL to SQL in hours
num_pending_mqlsNumber of pending MQLs
e_sqlsExpected number of SQLs

Bookings Metrics

MetricAd LevelCampaign LevelAccount LevelNotes
num_bookingsTotal number of bookings created
num_bookings_aNumber of bookings from rotator A
num_bookings_bNumber of bookings from rotator B
num_bookings_cNumber of bookings from rotator C
num_bookings_a_2dNumber of bookings from rotator A within 2 days
num_bookings_b_2dNumber of bookings from rotator B within 2 days
num_bookings_c_2dNumber of bookings from rotator C within 2 days
num_bookings_a_7dNumber of bookings from rotator A within 7 days
num_bookings_b_7dNumber of bookings from rotator B within 7 days
num_bookings_c_7dNumber of bookings from rotator C within 7 days
median_time_from_booking_creation_to_startMedian time from booking creation to start
num_scheduledNumber of AE bookings scheduled
num_pastNumber of AE bookings that have passed
num_past_htoNumber of past HTO bookings
num_past_mtoNumber of past MTO bookings (Account only)
num_past_ltoNumber of past LTO bookings (Account only)
num_takenNumber of AE bookings taken
num_unknownNumber of AE bookings with unknown SQL status

Sales Metrics

MetricAd LevelCampaign LevelAccount LevelNotes
num_sqlsNumber of Sales Qualified Leads
num_sqls_aNumber of SQLs from rotator A
num_sqls_bNumber of SQLs from rotator B
num_sqls_cNumber of SQLs from rotator C
num_wonNumber of won deals
num_won_htoNumber of won HTO deals
num_won_mtoNumber of won MTO deals (Account only)
num_won_ltoNumber of won LTO deals

Costs Metrics

MetricAd LevelCampaign LevelAccount LevelNotes
cplCost per lead (spend / num_leads)
cpmqlCost per MQL (spend / num_mqls)
cpmql_not_setCost per MQL without set appointments (Account only)
cpbCost per booking (spend / num_bookings)
cpsqlCost per SQL (spend / num_sqls)
cpe_sqlsCost per expected SQL

Applications Metrics (NEW)

MetricAd LevelCampaign LevelAccount LevelNotes
num_appsTotal number of applications
num_apps_aNumber of applications from rotator A
num_apps_bNumber of applications from rotator B
num_apps_cNumber of applications from rotator C
num_apps_unknownNumber of applications with unknown rotator
num_qappsNumber of qualified applications (SAL = Yes or p_sql >= 0.25)
cpaCost per application (spend / num_apps)
cpqaCost per qualified application (spend / num_qapps)

Conversion Rates

MetricAd LevelCampaign LevelAccount LevelNotes
p_showShow rate (taken/scheduled)
p_show_aShow rate for rotator A
p_show_bShow rate for rotator B
p_show_cShow rate for rotator C
p_qualQualification rate (SQL/taken)
p_sqlSQL rate (SQL/past scheduled)
p_sql_aSQL rate for rotator A
p_sql_bSQL rate for rotator B
p_sql_cSQL rate for rotator C
p_closeClose rate (won/SQL)
p_close_aClose rate for rotator A
p_close_bClose rate for rotator B
p_close_cClose rate for rotator C
p_winWin rate (won/past)
p_win_htoWin rate for HTO
p_win_mtoWin rate for MTO (Account only)
p_win_ltoWin rate for LTO (Account only)
p_win_aWin rate for rotator A
p_win_bWin rate for rotator B
p_win_cWin rate for rotator C

Key Findings

Correctly Implemented

  1. Ad and Campaign levels have identical metrics (as expected)
  2. Account level has additional MTO (Medium Ticket Offer) metrics
  3. Account level has frontend/backend cash breakdown
  4. Account level has MQL appointment tracking metrics
  5. Account level has additional LTO (Low Ticket Offer) metrics
  6. NEW: Applications metrics are available across all levels

Critical Issues Found

  1. Account level is missing ALL advertising metrics (impressions, clicks, CTR, etc.)
  2. Account level is missing e_roas_2d and e_roas_7d metrics
  3. Alert configuration includes advertising metrics for account level that don't exist in the data
  1. Remove advertising metrics from account level alert configuration
  2. Add missing financial metrics (e_roas_2d, e_roas_7d) to account level if they should exist
  3. Verify if account level should have advertising metrics or if they're intentionally excluded
  4. Update alert creation UI to only show available metrics for each level
  5. Add applications metrics to alert configuration for all levels

Implementation Status

  • Ad Level: ✅ Fully aligned with ad_daily_dashboard (including new applications metrics)
  • Campaign Level: ✅ Fully aligned with campaign_daily_dashboard (including new applications metrics)
  • Account Level: ❌ Needs fixes - advertising metrics should be removed, applications metrics should be added

New Applications Metrics Details

The following application-related metrics have been identified in all three dashboard tables:

Application Counts

  • num_apps: Total number of applications
  • num_apps_a: Applications from rotator A
  • num_apps_b: Applications from rotator B
  • num_apps_c: Applications from rotator C
  • num_apps_unknown: Applications with unknown rotator

Qualified Applications

  • num_qapps: Number of qualified applications (SAL = 'Yes' OR p_sql >= 0.25)

Cost Metrics

  • cpa: Cost per application (spend / num_apps)
  • cpqa: Cost per qualified application (spend / num_qapps)

Next Steps

  1. Update CreateAlertWizard.tsx to include applications metrics for all levels
  2. Remove advertising metrics from account level alert configuration
  3. Verify if missing financial metrics should be added to account level
  4. Test alert creation for all levels to ensure only valid metrics are available
  5. Update this document when changes are implemented

Last updated: December 2024 Document version: 2.0 Added: Applications metrics analysis