🎉 Bedrock Data is now Formstack Sync! · Learn More 🎉

Jeremy Martin | April 4, 2018

Mapping Systems and Fields in Fusion

Fusion Custom Field Mappings

How Mappings Work: Fusion's Tables   

If you're curious how Fusion handles custom fields and objects, you've come to the right place. But first, let's cover the three kinds of tables you’ll find when you connect your warehouse to a BI tool:

1. Fused: data extracted from each connected system creates a table for each major object type. The fused records reside in tables marked with names that correspond to an object. For example:

    • fused_activity
    • fused_company
    • fused_opportunity
    • fused_ticket

2. Raw: represents the SaaS system and the object type that we support in that SaaS table. These will be marked with names like:

    • gotoweb0_session
    • hubspot0_contact
    • salesforce0_lead

3. Links: form relationships between the different objects. Using links tables you can very easily join objects in a very simple SQL query. You’ll recognize them with names like:

    1. links_activity_ticket
    2. links_company_contact
    3. links_contact_opportunity 
So if you connect your warehouse to a BI tool, you might find an assortment of all three:

fusedDatabase

Selecting Systems

Now that we know which kinds of tables exist in Fusion, this will help us understand how to map fields.

The first step in mapping fields in Fusion requires we select our systems. If you’ve done this already — feel free to skip ahead to the steps below. After you log in to Fusion, hit the Manage Connections button from the Dashboard.

Modify your connectors in Fusion

For systems in this example, I’ll be selecting HubSpot & Salesforce. 

HubSpot logo          Salesforce logo

After you’ve authorized your connectors, they’ll look fuzzy. You can change, reactivate, or deactivate them at any time. 

 

Authorize your connectors in Fusion 

Once you've done so, your dashboard should populate with the connectors you've selected. 

 

Selecting Fields

As Salesforce users, we’re always asking "Where are leads coming from?” “What leads are resulting in deals?” 

For this reason, in Salesforce we use the Lead Source field, which has a dependent field called Lead Source Detail. Below you can see this latter field populates with a list of values. 

Salesforce dependent fields for leads

 

Since these lead sources and their details aren't by default in Fusion’s universal mappings, they make ideal candidates for customized mappings.

 

What Are Mappings?

A mapping defines how one field relates to another field for a given object. Fusion objects include: 

  • Events
  • Companies
  • Contacts
  • Contact Lists
  • URL Mappings
  • Deals
  • Deal Pipelines
  • Engagements
  • Forms
  • Owners
  • Broadcast Messages

 

How are Fusion mappings created?

Your connectors have unique schemas. As such, every object has a name proprietary to that system. One connector may have an object called Contact; another, Account; yet another, User. Such unique structures get very complicated.

Overcoming Data Silos to get a Unified View of Customers

Fusion simplifies this mess with mappings. It has a deep knowledge of what each connector's proprietary objects are (Account, Contact, User, for example) and all their concomitant fields (first_name, last_name, etc.). And if the API endpoints ever change, Fusion automatically adapts to reflect these mappings. 

Overcoming Data Silos to get a Unified View of Customers (1)

For example, let's imagine you were using HubSpot and Netsuite. HubSpot uses Contact for an object; Netsuite, Leads. 

Fusion reads the hubspot_contact_first_name field and the netsuite_lead_first_name field, then fuses the two fields into one table in your fused warehouse called fused_contact, under the field first_name.

Such mappings make storage in your Fusion warehouse way more than efficient. They give you a blueprint of your fused warehouse so that querying and visualizing customer data is easy to find within your BI tool of choice.

fused_contact

 

Custom Field Mappings

Although Fusion also has universal, or default mappings, let’s create a mapping for HubSpot and Salesforce custom fields.

First go to Schema in Fusion, which will pop you over to Create Custom Field. Select a type from the drop down list.

Screen Shot 2018-10-04 at 3.31.45 PM
 

Now I’m going to select Contact as my Field TypeSalesforce as my first connector, and Lead Source as the custom field.  

Once that’s all set, Lead Source should be connected with Contact, and Lead tied to Lead Source for the Salesforce connector.

Screen Shot 2018-10-04 at 3.34.19 PM
 

Next, we'll select HubSpot as our second connector. We'll do much the same as we did for Salesforce. The analog here for the Contact mapping in this system is a field called SFDC Lead Source which will appear in the dropdown menu.

Screen Shot 2018-10-04 at 3.36.49 PM
 

That’s it. Great job! You’ve just completed your very first custom mapping in Fusion.

Keep in mind that when you go to the All Custom Fields tab, you can review your custom fields, search for them by name, or sort by when they were created.

 

Real-Time Mappings for Real-Time Analytics

You might now be wondering: "Does my new mapping setup write back to the original source applications?" That is, would Fusion apply this HubSpot-Salesforce mapping back in HubSpot? For now, these mappings exist simply within your Fused Warehouse, and for the sake of powering your real-time analytics.

Which begs the next question: "After I've made a change, how long do I have to wait for my new Fusion mappings to refresh?"

Although this answer is a bit more nuanced, as the refresh time depends on the size of your warehouse, Fusion will pull updates from your systems every 5-10 minutes. If your warehouse is larger, the longest you should ever expect to see the mapping changes reflected is a couple hours.

 

Next Steps

Getting started with custom mappings is easy. Just log in to Fusion. And if you've yet to unify your SaaS data, Fusion's easy and free to try.

 

Subscribe Here!