LookML view · dating-platform
How this LookML events view models page views, pings, transactions and usage time
At a glance
Does A derived table over events_atomic with page, referer, structured event and ecommerce columns. It defines event, page view, ping and transaction counts, per-session and per-visitor ratios, and an approximate usage time. Trust: Source-defined
Why Event-level engagement for the dating site: how many pages and pings a session produces and how often sessions end in a transaction. Trust: InferredGrain One row per tracked event, keyed by event_id , which is the declared primary key. Rows without a domain_userid are dropped. Trust: Source-defined
Source dating_platform/activities.view.lookml 338 lines
Source: activities.view.lookml L1-10
dating_platform/activities.view.lookml L1-10 Show contextCopy
1 - view : events 2 derived_table : 3 sql : | 4 SELECT 5 app_id, 6 domain_userid, 7 domain_sessionidx, 8 event_id, 9 event, 10 collector_tstamp, 11 dvce_tstamp, 12 page_title, 13 page_urlscheme,
dating-platform, activities.view.lookml, lines 1-10
Shape Trust: Source-defined
Every field as declared, with the dashboard tiles that read it. Computed from the source; nothing here is edited.
Derived table: rebuilt on a SQL trigger. Reads warehouse tables directly.
Dimensions 48
Measures 21
Relationships Trust: Source-defined
No joins, no upstream views and no dashboard tiles reference this view. It is an island in the model.
Relationships of events
Text version events is the base view of events: base view
Filters and exclusions that change meaning
Events without a user id are excluded Trust: Source-defined
The derived table keeps only domain_userid IS NOT NULL. Events from clients that never set the cookie are invisible to every measure.
Source: activities.view.lookml L47-50
Worth noticing
Landing page views are inferred from the referer Trust: Source-defined
first_event_in_session is true when refr_medium != 'internal'. landing_page_views_count counts page views where that flag is true.
Source: activities.view.lookml L108-113
Usage time counts active 10-second buckets Trust: Source-defined
approx_user_usage_in_minutes counts distinct 10-second windows per user with APPROXIMATE COUNT(DISTINCT ...) and divides by 6 to get minutes.
Source: activities.view.lookml L265-277
What can change the answer 4
!
Caution: Seconds measures are computed from minutesTrust: Source-defined
approx_usage_per_visitor_in_seconds and approx_usage_per_visit_in_seconds divide approx_user_usage_in_minutes by visitors or sessions without multiplying by 60.
What goes wrong: A visitor with 3 minutes of activity shows as 3 seconds, so usage looks 60 times lower than it is.
Source: activities.view.lookml L265-277
!
Caution: NULL referers are not landing viewsTrust: Inferred
When refr_medium is NULL, refr_medium != 'internal' is NULL, so the event is neither a landing view nor an internal view.
What goes wrong: Direct traffic with no referer can drop out of both landing_page_views_count and internal_page_views_count .
Read the guide: Filters that change metric meaning
Source: activities.view.lookml L108-110
!
Caution: user_agent reads a column the derived table does not selectTrust: Source-defined
user_agent reads ${TABLE}.useragent, but the derived SQL never selects useragent. The field is hidden, which hides the error too.
What goes wrong: Any query that unhides or references user_agent fails with a missing column error.
Read the guide: Missing tables and stale references
Source: activities.view.lookml L147-149
i
Note: Ratios return NULL instead of zeroTrust: Source-defined
Measures such as page_pings_per_session wrap the numerator in NULLIF(..., 0). Sessions with no pings show an empty cell, not 0. Drill sets also reference sessions.*, source.* and domain_session_index, which do not exist here.
Source: activities.view.lookml L218-233
dating_platform/activities.view.lookml L218-233 Show contextCopy
215 type : count_distinct 216 sql : ${session_id} 217 detail : detail* 218 - measure : page_pings_per_session 219 type : number 220 decimals : 2 221 sql : NULLIF (${page_pings_count} ,0 )/NULLIF (${sessions_count} ,0 )::REAL 222 - measure : page_pings_per_visitor 223 type : number 224 decimals : 2 225 sql : NULLIF (${page_pings_count} ,0 )/NULLIF (${visitors_count} ,0 )::REAL 226 - measure : transactions_per_session 227 type : number 228 decimals : 3 229 sql : NULLIF (${transactions_count} ,0 )/NULLIF (${sessions_count} ,0 )::REAL 230 - measure : transactions_per_visitor 231 type : number 232 decimals : 2 233 sql : NULLIF (${transactions_count} ,0 )/NULLIF (${visitors_count} ,0 )::REAL 234 - measure : visitors_count 235 type : count_distinct 236 sql : ${user_id}
dating-platform, activities.view.lookml, lines 218-233
Parser checks 4 Trust: Source-defined
Mechanical findings from parsing the LookML. They are facts about the files. The cards above explain which ones matter.
Show all 4 checks
name-collision 1 activities.view.lookml:64 events.timestamp is declared as both dimension and dimension_group.set-missing 1 activities.view.lookml:214 events.sessions_count drills into set "detail", which is not declared.set-member-missing 2 activities.view.lookml:296 Set events.visit_detail lists "domain_session_index", which is not a field or set in this view.activities.view.lookml:322 Set events.transaction_detail lists "domain_session_index", which is not a field or set in this view.
Related
Guides built on this file Related source files
Source file
sessions
One derived table that stitches session basics, geo, landing page, exit page, source and technology into a ...
2 views 4 warnings
Source file
visitors
One row per cookie visitor with first and last touch, lifetime events, pages and sessions, plus the landing...
view 4 warnings
Source file
transactions
Builds web orders from transaction events: order id, affiliation, total, tax, city, state, country and the ...
view 3 warnings
Source file
event_tracker
Six explores on project_connection: events joined to sessions and visitors, sessions joined to visitors, pl...
model 3 warnings
Source model