Integrations
      Back to home
      1. Help Center
      2. Integrations

      Integrate Convert Experiences with Microsoft Power BI

      This Article Will Help You:


      Convert-Microsoft Power BI Integration

      Integration of Microsoft Power BI with Convert Experiences will help you to import Convert data into your central data warehouse (we will use Panoply) with an ETL tool (we will use Stitch). From there, it's easy to use Power BI to perform the in-depth analysis you need.

      For each experiment, the integration uses track events to pass along the experiment name and variation name that the visitor is currently bucketed into (if any).

      The general flow will look like this:


      We will need:

      1. A Segment account to be used as the middleware to send data from Convert Experiences to the powerful ETL tool Stitch.
      2. A Stitch account to connect your Segment data with your other data sources in a data warehouse in minutes.
      3. A Panoply account or any other data warehouse account that Segment supports (see here) list: 
      4. A Microsoft Power BI account to connect to your data warehouse. For Panoply read more instructions here.

      Add Tracking Code Snippets

      Make sure the Convert tracking code and the Segment tracking code (analytics.js) are installed on your pages. The Segment tracking code looks like this:

      Activate Convert-Segment Integration 

      Add the code below to your website right after the Convert + Segment tracking codes which will send Convert Experience and Variation names to Segment Debugger/Schema:

      var refObject = window['convert']['data']['experiments']
      	for (var key in window["convert"]["currentData"]["experiments"]) {
      			if (!window["convert"]["currentData"]["experiments"].hasOwnProperty(key)) {
      				continue;
      	}}
                  
      var currentExperiment = window["convert"]["currentData"]["experiments"][key];
      var curExperimentName = refObject[key] && refObject[key].n ? refObject[key].n : "unknown experiment name";
      curExperimentName = curExperimentName.replace("Test #", "Test ");
      var curVariant = currentExperiment['variation_name'] ? currentExperiment['variation_name'] : "unknown variant";
      curVariant = curVariant.replace("Var #", "Variation ");
      		
      analytics.track('Convert Experiences', {
      	Exp_Name: curExperimentName,
      	Var_Name: curVariant
      	});

      View Convert Data in Segment

      When you log in to your Segment account, you should go to your Schema. Inside your Schema, you can see all of the track events that you are sending through Segment, and if they are active or inactive.

       

      Add Stitch as Destination in Segment

      Then you should add an ETL tool (in our case we use Stitch) as your destination in Segment dashboard:

      Add Panoply as Destination in Stitch

      Then you should add your data warehouse (in our case we use Panoply) in your Stitch account and very quickly you will be able to see the tables/rows that are replicated:

      View Convert Data in Panoply

      In Panoply account you will be able to see the Convert Experiences data (experience + variation name) that you have sent initially:

      Connect Microsoft Power BI to Panoply

      To analyze your data, Panoply integrates with Business Intelligence (BI) tools such as Microsoft Power BI, Metabase, Tableau, Data Bricks, Looker, Chartio, Re:dash, Zeppelin, iPython Notebook, Shiny Apps by RStudio, and Sisense.

      To connect Power BI, note the following requirements:

      • You must use Power BI April 2018 or newer.
      • Use the Postgres connector. Panoply does not support the Redshift driver for Power BI. For other BI tools, we recommend that you use the Redshift driver.
      • Use port 5432 instead of the default port 5439.
      • If you are using Connect with Google to log into Panoply, you must reset your password in Panoply. This creates a password for logging into Panoply via Power BI. You will still be able to log into Panoply via Google after the password reset.