Department-Wide Adoption
Case Study: Sales Analytics with Databricks Genie
Stan Konkin
ML Content Developer, DataCamp
The pilot worked, now scale it
Pilot proven on
payments
Sales Director → roll out department-wide
Marketing wants in too
One table isn't enough
Revenue by booking outcome
Revenue by country and segment
Needs more tables,
connected
Connecting tables with relationships
Add the
bookings
table
Join on
booking_id
, many-to-one
Previous chapter's rules still apply
Watch the second money column
total_amount
= quoted price
Not the money actually received
A description keeps
amount
the real revenue
A three-table chain
Add
users
, join to
bookings
Chain: payments → bookings → users
Entity matching resolves segments
Locking a shared definition
"Net revenue"
means different things
SQL example = titled, prebuilt query
Genie reuses it
exactly
One asset, every country
One formula → every country
Trusted Asset = reusable query + placeholder
Test it with the word
"country"
Let's practice!
Case Study: Sales Analytics with Databricks Genie
Preparing Video For Download...