Branch to Power BI

This page provides you with instructions on how to extract data from Branch and analyze it in Power BI. (If the mechanics of extracting data from Branch seem too complex or difficult to maintain, check out Stitch, which can do all the heavy lifting for you in just a few clicks.)

What is Branch?

Branch Metrics lets businesses generate deep links they can use to track conversions and user engagement on web and mobile transactions. It provides a business analytics dashboard to surface user behavior data.

What is Power BI?

Power BI is Microsoft’s business intelligence offering. It's a powerful platform that includes capabilities for data modeling, visualization, dashboarding, and collaboration. Many enterprises that use Microsoft's other products can get easy access to Power BI and choose it for its convenience, security, and power.

With high-value use cases across analysts, IT, business users, and developers, Power BI offers a comprehensive set of functionality that has consistently landed Microsoft in Gartner's "Leaders" quadrant for Business Intelligence.

Getting data out of Branch

Branch exposes data for things like install, open, clicks, and web session start through webhooks to user-defined HTTP POST callbacks. You can add a webhook through the Branch dashboard.

Sample Branch data

Branch exchanges data in JSON format. Here’s an example of the data returned for a clicks endpoint:

User-agent: Branch Metrics API
Content-Type: application/json
    click_id: a unique identifier,
    event: 'click',
    event_timestamp: 'link click timestamp',
    os: 'iOS' | 'Android',
    os_version: 'the OS version',
    metadata: {
        ip: 'click IP',
        userAgent: 'click UA',
        browser: 'browser',
        browser_version: 'browser version',
        brand: 'phone brand',
        model: 'phone model',
        os: 'browser OS',
        os_version: 'OS version'
    query: { any query parameters appended to the link },
    link_data: { link data dictionary - see below }

// link data dictionary example
    branch_id: 'unique identifier for unique link',
    date_ms: 'link creation date with millisecond',
    date_sec: 'link creation date with second',
    date: 'link creation date',
    domain: 'domain label',
    data: {
        +url: the Branch link,
        ... other deep link data
    campaign: 'campaign label',
    feature: 'feature label',
    channel: 'channel label'
    tags: [tags array],
    stage: 'stage label',

Preparing Branch data

If you don’t already have a data structure in which to store the data you retrieve, you’ll have to create a schema for your data tables. Then, for each value in the response, you’ll need to identify a predefined datatype (INTEGER, DATETIME, etc.) and build a table that can receive them. Branch's documentation should tell you what fields are provided by each endpoint, along with their corresponding datatypes.

Complicating things is the fact that the records retrieved from the source may not always be "flat" – some of the objects may actually be lists. This means you’ll likely have to create additional tables to capture the unpredictable cardinality in each record.

Loading data into Power BI

You can analyze any data in Power BI, as long as that data exists in a data warehouse that's connected to your Power BI account. The most common data warehouses include Amazon Redshift, Google BigQuery, and Snowflake. Microsoft also has its own data warehousing platform called Azure SQL Data Warehouse.

Connecting these data warehouses to Power BI is relatively simple. The Get Data menu in the Power BI interface allows you to import data from a number of sources, including static files and data warehouses. You'll find each of the warehouses mentioned above among the options in the Database list. The Power BI documentation provides more details on each.

Analyzing data in Power BI

In Power BI, each table in the data warehouse you connect is known as a dataset, and the analyses conducted on these datasets are known as reports. To create a report, use Power BI’s report editor, a visual interface for building and editing reports.

The report editor guides you through several selections in the course of building a report: the visualization type, fields being used in the report, filters being applied, any formatting you wish to apply, and additional analytics you may wish to layer onto your report, such as trendlines or averages. You can explore all of the features related to analyzing and tracking data in the Power BI documentation.

Once you've created a report, Power BI lets you share it with report "consumers" in your organization.

Keeping Branch data up to date

Once you’ve set up the webhooks you want and have begun collecting data, you can relax – as long as everything continues to work correctly. You’ll have to keep an eye out for any changes to Branch’s webhooks implementation.

From Branch to your data warehouse: An easier solution

As mentioned earlier, the best practice for analyzing Branch data in Power BI is to store that data inside a data warehousing platform alongside data from your other databases and third-party sources. You can find instructions for doing these extractions for leading warehouses on our sister sites Branch to Redshift, Branch to BigQuery, Branch to Azure SQL Data Warehouse, Branch to PostgreSQL, Branch to Panoply, and Branch to Snowflake.

Easier yet, however, is using a solution that does all that work for you. Products like Stitch were built to move data from Branch to Power BI automatically. With just a few clicks, Stitch starts extracting your Branch data via the API, structuring it in a way that is optimized for analysis, and inserting that data into a data warehouse that can be easily accessed and analyzed by Power BI.