https://s3-us-west-2.amazonaws.com/secure.notion-static.com/86da90fa-ccb9-4aa7-80ff-874c72c637bd/reports_section_-transparent.png

Challenges

Outcome

Phase 1

Reports - a white label embed

Reports - a white label embed

Reports with additional CSS and generic filters

Reports with additional CSS and generic filters

Adding the first report. In order to test the functionality of a BI tool integration we added a single tab which took users to the Reports page. This page was a single page white-label embedded of a Mode Analytics report. Each user saw the same report, showing data from within their organization. This feature launched with a single report drawn from a new data lake which was populated by data synced from Sema's database, as well as a script generated csv that Professional Services generated.

Over the next few months, the report continued to grow — numerous graphs and queries, a sidebar for report navigation, and tooltips — all with minimal engineering resources. The page was extended in collaboration between professional services (who were now preparing custom reports in the same BI tool) and the product & design team (just me). I added queries and styled the report using the theming and html/css editor native to the BI tool. The embedded reports and data lake proved a big win as engineering resources were limited and precious. It became the most visited page, had the highest engagement, and user feedback was clear — more of this.

Phase 2

Engineering, Product and Professional Services all agreed on the success of this integration, but we began to notice a few issues;