Reporting in Drupal Commerce
summary
Three reporting paths exist with clear tradeoffs. Commerce Reports stores denormalized order rows in-site for SQL queries and tax reports but adds DB load and needs developer-written reports. Commerce Google Analytics sends client-side transaction events and UTM tracking so you can trace user journeys but loses raw data to Google and misses JS-blocked users unless you buy GA360. Lean Commerce Reports is a SaaS sales dashboard that backfills server events with front-end analytics, offers funnel, per-store revenue and tax snapshots, recovers recent lost data, is in private beta with a 72-franchise user and a ~$10/mo starter plan.
AI-written summary · about
chapters (13)
- 0:00Intro
- 0:54Why is reporting important?
- 2:23Insights & Intelligence
- 3:12Reporting in Drupal Commerce
- 4:58Free: On-site reporting using the existing database
- 12:12Client side, allows reporting with user behavior
- 13:41Social and marketing campaign conversion tracking
- 16:14Custom reports require product specific knowledge
- 21:04Client side and server side event tracking
- 21:38Out of the book reporting, no configuration or code
- 23:04Cart and checkout funnel analysis
- 23:46Revenue reports by store
- 26:20Lean Commerce Reports++ An evolving reporting tool built specifically for your platform
related talks
33mAnalytics Data Driven Testing
45mBy Enrico Pavan
46mSimple and Cheap Business Analytics with Google BigQuery
44mA Crash Course in Google Analytics for Firebase and BigQuery
16mMeasure and debug performance with Google Analytics 4 and BigQuery
30mLightweight Business Intelligence
39mEmbedded Analytics through Data API
44mHow Much Does This Even Cost? Using Analytics Tools to Measure ROI on Consoles & PC.