What’s new at Blendo: NetSuite, Relational and NoSQL databases, Usage Statistics, and Updates for Pardot and Hubspot connectors plus more

What can you do this month that you couldn’t do last month?

We made quite a few cool updates in September. There are new major data source integrations, new functionality for better visibility of your data pipeline status and usage statistics and updates on a few connectors.

So here’s what’s new.

1. New Integrations: Microsoft SQL Server, MySQL, MariaDB, MongoDB

In all honesty, we were lagging in the data source integrations that cover relational and NoSQL databases.

But today I’m incredibly proud of what we cover.

Along with PostgreSQL as a data source, Blendo now supports Microsoft SQL Server, MySQL, MariaDB and MongoDB as data source integrations.

What does this mean for you and your data team? Fewer data silos, faster implementation, less maintenance, get only the data you need when you need it. Effectively data integration automation with no hassle.

Read more on the Microsoft SQL Server, MySQL, MariaDB and MongoDB integration announcement here.

2. New Integration: NetSuite

NetSuite portraits itself as the world’s #1 cloud Enterprise Resource Planning (ERP) solution. But for Business Intelligence, you need to get data from NetSuite into a data warehouse, and that is not a small feat.

Blendo now supports NetSuite as a data source integration. Get your raw data or your Saved Searches results into your data warehouse by integrating NetSuite and Blendo.

Read more on the NetSuite integration announcement here.

3. Brand new Historical Status and Usage for your data pipelines

This is a pretty big deal actually, so it was already announced with a dedicated article:

What’s new at Blendo: Data Source Status History and Usage Views

Blendo History Tab

The new Blendo History tab provides an overview of your pipeline’s previous runs, but it also lets you drill down into the details of each run. A run is every time we sync data from a data source.

To give you a quick overview, I will have to tell you a little bit about how these runs work:

Let’s say you have an Intercom pipeline pushing data to your data warehouse every hour.

Every one hour, Blendo will try to pull data from Intercom and push to your data warehouse. This is one run.

For every run, we are going to pull some records from the source and push to destination. The resource is the table, records synced are the records we synced with your data warehouse.

If the run is smooth you will see a tick in front. If not you will see a triangle with an error.

In any case, you can dig deeper and see which resource failed. Always have in mind that Blendo “smartly” pulls resources in parallel so even if you see an error in one of the resources, the rest will not stop syncing.

Blendo Usage Tab

Ever wondered where most of your usage volume is coming from?

Here is how this can help.

The information you see in the Usage tab has daily granularity and for now, gives you the last 30 days view. Following up on the example above, let’s say we have synced 1000 records in one day.

You will be able to see these 1000 records but you are also able to see which resource (table) pulled most and filter to that resource too.

So…

Combining the info between the Usage tab that gives you the daily granularity and the History tab that gives you run granularity, you can pinpoint issues or optimize your pipeline and understand their status better.

I hope these new tabs will give you great insights into how your pipelines run and behave. For more details please read this article or our documentation.

4. Important Update for Our Pardot and Hubspot Integrations

Good news for data teams and marketers that are using Pardot and Hubspot. We worked on some updates that we think you will be excited about.

What’s New with Salesforce Pardot

We have improved the speed of our Salesforce Pardot connector. With your Pardot integration, you can make sure that data in Pardot replicate in your data warehouse efficiently and get reflected in your BI tool automatically.

We now use the bulk API to improve the sync speed of the following Pardot resources:

• Custom Redirects
• Dynamic Content & Dynamic Content Variations
• Forms
• Lifestyle histories
• Lists
• Prospects, Prospect Accounts, Prospect List Subscriptions & Prospect Profile Criteria
• Tag Objects
• Tags
• Visitor Activities
• Visitors

For existing customers: For the resources mentioned above, nested data will not be available in the same tables any longer. E.g., Campaign data is not available in visitor_activities table that relates to a campaign, it can be found in a different table, that is relevant to the resource. The initial table will still contain the id that can be used for association (checking the campaign table using the provided associated campaign’s id in the record).

I would love to hear your experience with Pardot, so please let me know about it or contact our support team in case you need help.

How to Automate Pardot sync with Blendo

1. Make sure you have a Blendo account, a Salesforce Pardot account, and a data warehouse.
2. Connect your data warehouse and Pardot with Blendo. You may also check out our Salesforce Pardot help documentation for details on connecting your account and setting up your data integration.
3. Your data from Pardot will flow into your data warehouse in a consistent manner and with document and normalized schema you can find on our Pardot knowledge base.

What’s New with Hubspot

You can now sync your Hubspot Contact properties history (contacts_property_histories) and Deals properties history (deals_property_histories).

If you were wondering how you can track which property changed, from which source or which vid is involved, then you can see all these data into your Business Intelligence tool.

For Contact properties history:

Your Hubspot contact property history information now syncs with your data warehouse, and you can visualize effectively how its value has been updated over time. We sync properties like Vid (the internal name of the contact record), source_type (which source was involved eg, change was done from API, CRM_UI, FORMS, etc.) and value.

For Deals properties history:

You now have available data like the dealid, source_type (which source was involved eg, change was done from API, CRM_UI, FORMS, etc.) and value.

With these properties, you can have better visibility on when a new deal enters a particular stage and get insights on your deal velocity. Do you need to understand the bottlenecks in your sales process? Find out how many times a deal has changed stages and/or how many times a deal’s close date has changed.

That’s it!

We’re hoping that you will enjoy these new updates to Blendo that were made in September.

And if you have any questions or feedback, please do not hesitate to let us know about it!