LookML dashboard · dating-platform

Three business dashboards: revenue, conversion and map tiles built on missing explores

At a glance

Does: Business overview (7 tiles), Conversion Rates (3 tiles) and Maps (3 tiles). They chart revenue, transactions by type, users by place and orientation, expected LTV and message activity.Trust: Source-defined
Why: Executive views of the dating business: revenue trend, user base, acquisition and where activity happens.Trust: Inferred
Breaks: 4 warnings. Top: Most tiles query explores or views that are not in the repo
Grain: Revenue tiles read the transactions explore, whose base view user_transactions is not in the repo. Most user tiles query a users explore that no model declares.Trust: Source-defined
Source: dating_platform/company_overview.dashboard.lookml, dating_platform/conversion_metrics.dashboard.lookml, dating_platform/geographics.dashboard.lookml 327 lines

Source: company_overview.dashboard.lookml L1-10

dating_platform/company_overview.dashboard.lookmlL1-10 Show context

1- dashboard: business_overview2  layout: tile3  tile_size: 1004  filters:5  - name: date_filter6    title: Date7    type: date_filter8    default_value: last 6 months9  elements:10  - name: total_revenue11    title: Total Revenue12    type: single_value13    explore: transactions

dating-platform, company_overview.dashboard.lookml, lines 1-10

Tile map: business_overview 7

Source-defined

Every tile in file order, with the fields it reads. Field links go to their definitions.

Total Revenue

single_value explore transactions

Measures: transactions.total_revenue (view missing)
Limit: 500
Listens to: date_filter

total_revenue L10-20

Transactions

single_value explore transactions

Measures: transactions.count (view missing)
Limit: 500
Listens to: date_filter

transactions L21-31

Transactions by Type

looker_area explore transactions

Dimensions: transactions.created_month (view missing)
Measures: transactions.count (view missing)
Pivots: transactions.type (view missing)
Sort: created_month, limit 500
Listens to: date_filter

transactions_by_type L32-61

Where are Users?

looker_geo_coordinates explore users explore not declared

Dimensions: users.zipcode (explore missing)
Measures: users.count (explore missing)
Listens to: no dashboard filters

users_map L62-73

Users by Orientation

looker_pie explore users explore not declared

Dimensions: users.orientation (explore missing)
Measures: users.count (explore missing)
Sort: count desc, limit 500
Listens to: date_filter

users_by_orientation L74-89

Average Expected LTV

looker_line explore users explore not declared

Dimensions: users.created_month (explore missing)
Measures: scores.avg_expected_ltv (explore missing)
Limit: 500
Listens to: date_filter

average_lifetime_value L90-115

Revenue by Type

looker_column explore transactions

Dimensions: transactions.created_month (view missing)
Measures: transactions.total_revenue (view missing)
Pivots: transactions.type (view missing)
Sort: created_month, limit 500
Listens to: date_filter

revenue_by_type L116-145

Tile map: Conversion Rates Dashboard 3

Source-defined

Every tile in file order, with the fields it reads. Field links go to their definitions.

Daily Revenue

line explore transactions

Dimensions: transactions.created_date (view missing)
Measures: transactions.gross_revenue (view missing)
Pivots: acquisition.channel (alias missing)
Filters: created_date = before today
Limit: 500
Listens to: date_range, channel, orientation

daily_revenue L21-52

GAP Revenue By Month

line explore transaction_ledger explore not declared

Dimensions: transaction_ledger.date_month (explore missing)
Measures: transaction_ledger.total_revenue (explore missing)
Filters: date_month = before this month
Sort: date_month, limit 500
Listens to: no dashboard filters

gap_revenue L53-82

Revenue By Month

line explore transactions

Dimensions: transactions.created_month (view missing)
Measures: transactions.net_revenue (view missing)
Filters: created_month = before this month
Sort: created_month, limit 500
Listens to: no dashboard filters

revenue_by_month L83-111

Tile map: Maps Dashboard 3

Source-defined

Every tile in file order, with the fields it reads. Field links go to their definitions.

Leads

looker_geo_coordinates explore users explore not declared

Dimensions: users.zipcode (explore missing)
Measures: users.count (explore missing) users.city (explore missing)
Sort: count desc
Listens to: date_range, source

map L16-34

Message Activity

looker_geo_coordinates explore messages

Dimensions: sender.zipcode (view missing)
Measures: messages.count
Sort: count desc
Listens to: date_range

map L35-51

Add a title

looker_geo_choropleth explore users explore not declared

Dimensions: users.state (explore missing)
Measures: users.count (explore missing)
Listens to: date_range, source

another_map L52-71

Filter wiring: business_overview

Source-defined

Dashboard filters only reach tiles that declare a listen binding. Tiles in the Skips column ignore the filter even when it is set.

Filter	Default	Field	Drives	Skips
`date_filter`Date	`last 6 months`	date_filter	6 of 7: T1 T2 T3 T5 T6 T7	T4

Filter wiring: Conversion Rates Dashboard

Source-defined

Dashboard filters only reach tiles that declare a listen binding. Tiles in the Skips column ignore the filter even when it is set.

Filter	Default	Field	Drives	Skips
`date_range`Date Range	`30 days`	date_filter	1 of 3: T1	T2 T3
`channel`Acquisition Channel	none	`acquisition.channel`	1 of 3: T1	T2 T3
`orientation`Orientation	none	`users.orientation`	1 of 3: T1	T2 T3

Filter wiring: Maps Dashboard

Source-defined

Dashboard filters only reach tiles that declare a listen binding. Tiles in the Skips column ignore the filter even when it is set.

Filter	Default	Field	Drives	Skips
`date_range`Date Range	`this year`	date_filter	3 of 3: T1 T2 T3	none
`source`Source	none	`referral.source`	2 of 3: T1 T3	T2

Filters and exclusions that change meaning

Date filters reach most tiles, not all

Source-defined

The business overview date filter defaults to last 6 months, but Where are Users? has no listen, so it shows all time. On the conversion dashboard only Daily Revenue listens to any filter.

Source: company_overview.dashboard.lookml L62-73

dating_platform/company_overview.dashboard.lookmlL62-73 Show context

59    y_axis_min: null60    y_axis_max: null61    hide_points: true62  - name: users_map63    title: Where are Users?64    type: looker_geo_coordinates65    explore: users66    map: usa67    dimensions:68    - users.zipcode69    measures:70    - users.count71    limit: null72    width: null73    height: null74  - name: users_by_orientation75    title: Users by Orientation76    type: looker_pie

dating-platform, company_overview.dashboard.lookml, lines 62-73

Channel and orientation filters need joins that do not exist

Source-defined

Daily Revenue listens to acquisition.channel and users.orientation. The transactions explore has no acquisition join, and users is not in the repo.

Source: conversion_metrics.dashboard.lookml L21-36

dating_platform/conversion_metrics.dashboard.lookmlL21-36 Show context

18    explore: users19    dimension: users.orientation20  elements:21  - name: daily_revenue22    title: Daily Revenue23    type: line24    explore: transactions25    dimensions:26    - transactions.created_date27    measures:28    - transactions.gross_revenue29    pivots:30    - acquisition.channel31    listen:32      date_range: transactions.created_date33      channel: acquisition.channel34      orientation: users.orientation35    filters:36      transactions.created_date: before today37    limit: 50038    width: 1239    height: null

dating-platform, conversion_metrics.dashboard.lookml, lines 21-36

Worth noticing

Gross on one tile, net on another

Source-defined

Daily Revenue charts transactions.gross_revenue and Revenue By Month charts transactions.net_revenue, on one dashboard with no label saying which is which.

Source: conversion_metrics.dashboard.lookml L83-92

dating_platform/conversion_metrics.dashboard.lookmlL83-92 Show context

80    hide_points: true81    interpolation: step-after82    x_axis_datetime_tick_count: 4083  - name: revenue_by_month84    title: Revenue By Month85    type: line86    explore: transactions87    dimensions:88    - transactions.created_month89    measures:90    - transactions.net_revenue91    filters:92      transactions.created_month: before this month93    sorts:94    - transactions.created_month95    limit: 500

dating-platform, conversion_metrics.dashboard.lookml, lines 83-92

Fixed axes clip outliers

Inferred

Revenue by Type pins the y axis from -50000 to 500000, and Average Expected LTV pins it from 70 to 85. Values outside those ranges fall off the chart.

Source: company_overview.dashboard.lookml L138-145

dating_platform/company_overview.dashboard.lookmlL138-145 Show context

135    stacking: normal136    x_axis_label: null137    x_axis_datetime: true138    x_axis_datetime_label: null139    x_axis_label_rotation: null140    y_axis_orientation: null141    y_axis_combined: null142    y_axis_labels: null143    y_axis_min: -50000144    y_axis_max: 500000145    hide_points: true

dating-platform, company_overview.dashboard.lookml, lines 138-145

Leftovers from editing

Source-defined

The maps dashboard has two tiles named map and one titled Add a title. Daily Revenue carries the legend title Testing Title.

Source: geographics.dashboard.lookml L52-58

dating_platform/geographics.dashboard.lookmlL52-58 Show context

49    sorts:50    - messages.count desc51    point_radius: 552  - name: another_map53    title: Add a title54    type: looker_geo_choropleth55    explore: users56    dimensions:57    - users.state58    measures:59    - users.count60    listen:61      date_range: users.created_date

dating-platform, geographics.dashboard.lookml, lines 52-58

What can change the answer 4

Blocker: Most tiles query explores or views that are not in the repo

Source-defined

Five tiles query a users explore that no model declares. Gap Revenue queries transaction_ledger, which does not exist. The revenue tiles read user_transactions, which is missing.

What goes wrong: These tiles cannot be traced to a definition, so their numbers cannot be checked or reproduced from this repo.

Read the guide: Missing tables and stale references

Source: conversion_metrics.dashboard.lookml L53-64

dating_platform/conversion_metrics.dashboard.lookmlL53-64 Show context

50    y_axis_labels: null51    y_axis_min: null52    y_axis_max: null53  - name: gap_revenue54    title: GAP Revenue By Month55    type: line56    explore: transaction_ledger57    dimensions:58    - transaction_ledger.date_month59    measures:60    - transaction_ledger.total_revenue61    filters:62      transaction_ledger.date_month: before this month63    sorts:64    - transaction_ledger.date_month65    limit: 50066    width: null67    height: null

dating-platform, conversion_metrics.dashboard.lookml, lines 53-64

Caution: The transactions explore exists twice

Inferred

Both the enterprise and event_tracker models declare an explore named transactions, and each includes every dashboard file. A tile's meaning depends on which model it runs in.

What goes wrong: Total Revenue points at user_transactions in one model and at the events-based transactions view, which has no total_revenue field, in the other.

Read the guide: Missing tables and stale references

Source: company_overview.dashboard.lookml L10-20

dating_platform/company_overview.dashboard.lookmlL10-20 Show context

7    type: date_filter8    default_value: last 6 months9  elements:10  - name: total_revenue11    title: Total Revenue12    type: single_value13    explore: transactions14    measures:15    - transactions.total_revenue16    listen:17      date_filter: transactions.created_date18    limit: 50019    width: 620    height: 221  - name: transactions22    title: Transactions23    type: single_value

dating-platform, company_overview.dashboard.lookml, lines 10-20

Caution: The source filter reads a view that does not exist

Source-defined

The maps dashboard filter source reads referral.source, and two tiles listen to it. No view or join is named referral.

What goes wrong: Lead maps cannot be narrowed by acquisition source, so lead counts by place ignore the filter.

Read the guide: Filters that change metric meaning

Source: geographics.dashboard.lookml L10-14

dating_platform/geographics.dashboard.lookmlL10-14 Show context

7    title: Date Range8    type: date_filter9    default_value: this year10  - name: source11    title: Source12    type: select_filter13    explore: users14    dimension: referral.source15  elements:16  - name: map17    title: Leads

dating-platform, geographics.dashboard.lookml, lines 10-14

Note: A dimension sits in the measures list

Inferred

The Leads map lists users.city under measures next to users.count. City reads as a grouping field, so the tile mixes a dimension into its measures.

Source: geographics.dashboard.lookml L16-28

dating_platform/geographics.dashboard.lookmlL16-28 Show context

13    explore: users14    dimension: referral.source15  elements:16  - name: map17    title: Leads18    type: looker_geo_coordinates19    explore: users20    dimensions:21    - users.zipcode22    measures:23    - users.count24    - users.city25    listen:26      date_range: users.created_date27      source: referral.source28    limit: null29    map: usa30    width: null31    height: null

dating-platform, geographics.dashboard.lookml, lines 16-28

Parser checks 16

Source-defined

Mechanical findings from parsing the LookML. They are facts about the files. The cards above explain which ones matter.

Show all 16 checks

missing-view 8
- company_overview.dashboard.lookml:10 Tile total_revenue reads transactions.total_revenue, transactions.created_date from user_transactions, which is not in the repo.
- company_overview.dashboard.lookml:21 Tile transactions reads transactions.count, transactions.created_date from user_transactions, which is not in the repo.
- company_overview.dashboard.lookml:32 Tile transactions_by_type reads transactions.created_month, transactions.count, transactions.type, transactions.created_date from user_transactions, which is not in the repo.
- company_overview.dashboard.lookml:116 Tile revenue_by_type reads transactions.created_month, transactions.total_revenue, transactions.type, transactions.created_date from user_transactions, which is not in the repo.
- conversion_metrics.dashboard.lookml:21 Tile daily_revenue reads transactions.created_date, transactions.gross_revenue from user_transactions, which is not in the repo.
- conversion_metrics.dashboard.lookml:21 Tile daily_revenue reads users.orientation from users, which is not in the repo.
- conversion_metrics.dashboard.lookml:83 Tile revenue_by_month reads transactions.created_month, transactions.net_revenue from user_transactions, which is not in the repo.
- geographics.dashboard.lookml:35 Tile map reads sender.zipcode from users, which is not in the repo.
missing-explore 6
- company_overview.dashboard.lookml:62 Tile users_map queries explore users, which no model in the repo declares.
- company_overview.dashboard.lookml:74 Tile users_by_orientation queries explore users, which no model in the repo declares.
- company_overview.dashboard.lookml:90 Tile average_lifetime_value queries explore users, which no model in the repo declares.
- conversion_metrics.dashboard.lookml:53 Tile gap_revenue queries explore transaction_ledger, which no model in the repo declares.
- geographics.dashboard.lookml:16 Tile map queries explore users, which no model in the repo declares.
- geographics.dashboard.lookml:52 Tile another_map queries explore users, which no model in the repo declares.
missing-field 1
- conversion_metrics.dashboard.lookml:21 Tile daily_revenue reads acquisition.channel; explore transactions has no view or join named acquisition.
duplicate-tile 1
- geographics.dashboard.lookml:35 Tile name "map" is used more than once in maps_dashboard.

At a glance

Tile map: business_overview 7

Tile map: Conversion Rates Dashboard 3

Tile map: Maps Dashboard 3

Filter wiring: business_overview

Filter wiring: Conversion Rates Dashboard

Filter wiring: Maps Dashboard

Filters and exclusions that change meaning

Date filters reach most tiles, not all

Channel and orientation filters need joins that do not exist

Worth noticing

Gross on one tile, net on another

Fixed axes clip outliers

Leftovers from editing

What can change the answer 4

Blocker: Most tiles query explores or views that are not in the repo

Caution: The transactions explore exists twice

Caution: The source filter reads a view that does not exist

Note: A dimension sits in the measures list

Parser checks 16

Related

Guides built on this file

Related source files

Source model