Powering BI

Go back and forth with stakeholders without any worry.

How it works

Bring everything together in three easy steps

1. Define the dataset

Generate the query that has the data you want

2. Materialize It

Convert the query into a table via materialization

3. Visualize it

Add the data to your BI tool and create the neccessary dashboards

The Narrator difference is how we handle iterations

Slice anything by anything

Stakeholders want to see data sliced by an infinite list of features. For each new slice, you don't have to worry about joining in new columns. Narrator handles the added SQL complexity for you.

Add columns in seconds from anywhere
Never duplicate or drop rows
No more 1000+ line SQL queries to maintain
Encourage your team to ask more questions
User attributes

Add customer attributes

"Show me what this looks like by gender."
"Grab customers by city."
"Let's explore order status by age."

Adding the Gender customer attribute column to a Narrator dataset
Adding in the first ever Started Session's Ad Source and Referring Domain columns to a Narrator dataset
Activity attributes

Add features from other activities

"Please, add the first touch ad source."
"Add the contract value before that opportunity stage."
"Bring in the last email campaign"

Behavioral attributes

Add features dependent on behavior

"Well, did this user call us before they converted?"
"What action did they take since their previous support ticket?"
"Have they ever met with sales?"

Editing Definiton in Narrator's Dataset tool to add the "Called Us" activity but only before the first "Completed Order"

Yes, you can still use dbt

In Narrator, you can materialize any query for BI or send it to dbt as a new model.

It's simple to iterate using Narrator's materialized view integration. Once you have something ready for production, you can trigger a pull request to your dbt project to have it be maintained there.

Ready to iterate quickly from question to answer?

Create an account today.