In this movie I’ll show you what to do with your Fusion warehouse credentials, walk you through how to use those credentials to connect to your BI tool, and then help you understand exactly what’s in your Fusion Warehouse once you’ve hooked it all up. By the end, you’ll have a great idea of how your Fusion Warehouse is architected and how to join any of the tables based on that organization.
So once Fusion has built my warehouse, I’ll see my data populate the dashboard. There, I can get a nice overview of the number of fused records as well as the number of raw records for each of the systems I have connected.
Here we have Zendesk, along with an instance of Salesforce and HubSpot. And I can see whether my connectors are online or offline, as well as whether the number of records has gone up or down over time.
OK so now all I need to do is grab my warehouse credentials, which I’ll find on a tile on my Fusion dashboard where it says “Looking for your warehouse credentials?”. So I would just click “Get Credentials” to get the information that I’ll need to enter in my BI tool and that’ll bring me to my credentials screen here.
And here I’ll find what most in the data business would agree is pretty standard stuff -- the host, my username, database, password, and the port number. In Fusion, I can download a .csv file of my credentials and save them in a safe location if I’d like. I can also just copy paste them from the UI itself.
The great thing about having this Fused Warehouse is that I can now connect Fusion to any reports, dashboards, or BI tool that accepts a MySQL database, which in today’s market is about 95% or more. And so now that I have this warehouse, I can connect Fusion to Looker, Tableau, Yellowfin, Metabase, Quicksight, or any number of analytics platforms which are all amazing when it comes to querying data and data visualization.
OK so now that I have my credentials, this is actually the fun part. In this example, I’m using Metabase. And I’m going to navigate to the Admin Panel, where I’ll select Databases on the top menu bar. That allows me to Add a Database, which brings me to this next page.
And like I said, it doesn’t matter a whit whether I’m using MySQL Workbench or Microsoft Power BI. All I need to do is choose MySQL as my database type. Paste in my credentials. Then, once I’m done, I just click Save. And doing so will let me access my Fusion Warehouse at anytime, in real-time, and so I’m now 100% ready to do my analysis using my state-of-the-art Fused Database.
Once you've established your connection with your Fusion Warehouse, it's high time to explore what's in it.
The best way to see what’s in your Fused Database is by running a simple “show tables” command. After which you’ll be able to identify the fused, raw, and links tables in your warehouse.
As you can see, the fused tables will always begin with fused “underscore” -- followed by the object. In this example, we have fused_activity and fused_company. But it could easily be fused_contact or fused_opportunity, and so on.
These fused tables are the real special sauce that will power your analysis because what Fusion’s done is gather every major object type and organize them nice and neat as Fused objects like contacts and opportunities.
But the raw records are also there. Once I connect my systems, Fusion will also go ahead and replicate all the raw data from my systems. So when I connect my Fused Warehouse to my BI tool, I’ll see these raw tables marked as the system + object. In this example they’re marked with names like: gotoweb, which is the system, followed by an underscore, then object, which is session. And the same pattern applies to this second example where we have hubspot, the system, tied to the contact object. In other words, not only do I get every major category, combined in a hyper intelligent way -- I also have access to the original data source, too.
And finally, we have the links tables, whose importance cannot be understated.Think of a links table like a pencil. It doesn’t do anything by itself. It also doesn’t do anything just in my hand. But it can do incredible things when I bring that pencil onto a sketch pad and begin to draw what I see in my mind. In that sense, the links tables form relationships between my SaaS applications’ different objects. So, for example, I could have an Activity object and a Ticket object and want to know how my customers’ activities relate to the number of tickets in my support systems. I could also link any company and tie it to a contact.
OK, but these are just the names of my warehouse tables. The data model here shows how all three relate to one another.
Let’s say Jane Doe exists in both HubSpot and Salesforce. Meaning both connectors will have her in their raw records. Both HubSpot and Salesforce have data about the Company she’s worked at, and so they combine that information into a Fused Company table. And likewise, the same thing goes for her Contact information. That also goes into a Fused Contacts table.
Using the Links Company Contacts table, I can now return a report with all the data that relates to Jane Doe from both connectors. Take a moment to let that sink in. Because this is not something I could do natively, in either HubSpot or Salesforce. Nor is it something I could do by exporting data or reading their APIs unless I did a whole lot of data prep. All the data about Jane Doe, and customers like her, is a million-fold more accessible and easier to work with. All the data about her is standardized and up-to-date.