New settings section for Hubspot, Salesforce, Segment, Intercom and Mailchimp

Hey there,

We have updated the settings sections of some of our connectors, including Hubspot, Salesforce, Segment, Intercom and Mailchimp.

You can see an example here with a side by side comparison of the settings of the Intercom connector:

Below screenshots showing before and after the updates on the settings design:

Screenshot_2019-07-16_at_11.12.56.pngScreenshot_2019-07-16_at_11.10.59.png

The reasons for these changes are the following:

  • The related settings fields are now grouped together in sections in grey to emphasize their logical relationships.
  • Each setting section now has a description to embed documentation and other helpful tips.
  • The settings sections are now arranged in the order that the connector should be configured.
  • The navigation bar on the left helps you jump to a particular section of the settings page.
  • With these settings, we introduce better designed, bigger and more robust form components.

Ingesting Salesforce Tasks as events inside Hull

Hey there,

It is now possible to ingest Salesforce tasks as events inside Hull. Tasks are native objects inside Salesforce that are used to improve the productivity of your Sales team.

By ingesting these tasks as events, you will be able to create segments of users based on whether they had a task attached to them inside Salesforce.

A standard use case with that new feature involves refining segments of users in Hull which are then sent out to marketing automation tools to trigger email campaigns.

Let's say a member of your sales team had a call with a given user 2 days ago. You want to exclude that user from a nurturing campaign because you do not want to be too pushy with your users. This call is often stored inside Salesforce as a task. By ingesting this task as an event inside Hull, you are going to be able to add a criteria to the segment that is sent out to your marketing automation tool for you nurturing campaign which will be something like did not have a task with a customer in the last 7 days. That way you can exclude these particular customers with whom you had recently contacted from your nurturing campaigns.

Here is the new section inside the connector to fetch tasks inside the Salesforce connector:Screenshot_2019-08-06_at_12.05.43.png

New Marketo connector

Hey there,

We are delighted to announce the release of our new Marketo connector!

Marketo is a marketing automation tool that allows you to automate the generation of personalized multi-channel marketing campaigns. Furthermore, Marketo enables you to handle lead management, email campaigns, and mobile campaigns.

This new connector allows you to leverage Hull's ability to create advanced, granular segments in order to create hyper-personalized marketing and email sequences in Marketo. This use case is similar to how many of our customers currently use our Mailchimp, Customer.io, and Outreach connectors.

This Marketo connector has 3 main features:

  • Fetching leads: ingesting the list of leads and their attributes that you store inside Marketo and make them available inside of Hull
  • Fetching leads activities: ingesting the events tied to the leads in your Marketo organization in Hull (email opened, email bounced,...)
  • Sending users to Marketo: define the segments of users that you want to send out to Marketo, along with their attributes. They will be stored as leads inside Marketo

Here are the steps to follow to complete the full set-up of the connector:

  • Connect with Marketo using your credentials Screenshot_2019-08-28_at_11.05.35.png
  • Define your identity resolution strategy Screenshot_2019-08-28_at_11.06.41.png
  • Fetch users with their events and attributes: define your incoming attributes mapping the same way you can do it with most of our connectors. Screenshot_2019-08-28_at_11.07.13.png
  • Send users from Hull to Marketo: define the whitelist segments and the outgoing attribute mapping the same way you can do it with the most of our connectors Screenshot_2019-08-28_at_11.12.55.png

Showing recently deleted connectors

Hey there,

New enhancement to the connectors list.

Especially during the set-up of your Hull organization, you are brought to delete connectors as you run some tests or need to perform some clean-ups. If you were several collaborators to set-up Hull including our customer support team when they jumped in, it was really painful to see from one day to another that some connectors had disappeared. You simply could not access the information about who deleted that given connector and when.

This pain is now over as we have now added a list of your deleted connectors. This list is accessible via a modal you can pop-up by clicking on a button next to the "Add a connector" button on the top right of the connectors list.

Here is a screenshot on how the feature works:

Screenshot_2019-08-22_at_10.24.36.png Screenshot_2019-08-22_at_09.55.26.png

New refresh button on the users and accounts tabs

Hey there,

We have added a new "refresh" button inside the Users and Accounts tabs.

Before, when you wanted to make a track or traits call on a given user to test out your Processor code, for instance, you had to hit the cmd + R button to refresh the page to update the user.

This was cumbersome because you were compelled to refresh the entire page and thus lose some time.

To prevent that, we have added a new "refresh" button that will quickly update the users or accounts without refreshing the entire page. This will help you make the updates faster and help you increase your productivity.

Screenshot_2019-08-21_at_11.49.59.png

Data pipeline status monitor

Hey there,

Until now, it was difficult to have a clear overall view of what was delaying synchronization of data in Hull; a holistic view containing the status of all of your connectors was missing.

We addressed this issue by adding a status monitor within the overview page. Here's what you'll find there:

  • The Platform, which displays ingestions delays coming from the connectors, website tracking and imports.
  • The Connectors, which displays the outgoing backlog delays with a quick overview of each connector.

These delays are displayed chronologically in the form of pills, which give you an indication of synchronization health at a glance:

  • green stands for "OK"
  • yellow stands for "WARNING" if at least one connector in the list has the status "WARNING"
  • red stands for "CRITICAL" if at least one connector in the list has the status "CRITICAL"

Also, by hovering on a given pill, you will be shown more detailed information:

  • For the incoming bar, you'll find user and account ingestion delays
  • For the outgoing bar, you'll see which connectors are affected by the delays

The delays are computed with a 15 minute time range :

  • < 15 min for a delay between 0 and 15 minutes
  • < 30 min for a delay between 15 and 30 minutes
  • < 45 min for a delay between 30 and 45 minutes
  • < 60 min for a delay between 45 and 60 minutes
  • > 60 min for a delay above 1 hour

Here's a screenshot of what it looks like on an organization overview:

Screenshot_2019-08-06_at_12.16.19.png

Better visibility on the number of API calls in your third party tool

Hey there,

We wanted to announce you that we have improved the way you can monitor the number of API calls on each given connector inside the API calls dashboard.

Before, you could only see the number of API calls in the last 30 minutes during the last 24 hours. So, to retrieve the number of API calls each day you had to add up all the 30min time ranges of the day to compute your overall number of API calls in one single day. That was painful and it did not even give you the number of API calls of the month which is the most import metric you want to monitor to make sure you do not overuse your third party tool's plan.

To prevent that, we have made it possible for you to select the time range for which you want to control the API calls: with a dropdown on the top right, you can select either "Last 24 hours", "Last 7 days" or "Last 30 days". You also have on the top left a direct access to the overall number of API calls corresponding to the time range you chose.

apicalls2.png

We hope this new feature will enable you to better monitor your API calls and also understand how Hull can help you reduce that number by filtering the data synchronised to your third party tool and thus save you money.

New data warehouse connector

Hey there,

We are excited to announce the release of a new connector: a Postgres Data Warehouse connector.

This new connector allows you send all of your user and account profiles, as well as events in Hull to your data warehouse. This will allow you to unlock immeasurable clarity from your Hull data.

This choice to work on this connector essentially stems from the need for our customers to run accurate reports based on the data gathered inside Hull. Indeed, to design your personas, visualize your customers journeys, run attribution reports and to make many other reportings, you often have to use a BI tool (Tableau, Periscope, Chartio, etc.) on top of your data warehouse. But you can only achieve that if you have enough data inside your data warehouse. Thanks to the release of this new connector, Hull allows you to do that by sending all the data you captured from various tools (product data, firmographic data, offline data, etc.) inside your data warehouse.

Once the Data Warehouse Connector has been installed, authorize it by entering your data warehouse credentials:

  • Database connection information Screenshot_2019-07-15_at_15.49.22.png
  • Database login information Screenshot_2019-07-15_at_15.49.34.png Your Hull data will be sent in three different tables: one for users, one for accounts and one for events. Thus, the second step is to fill-in the names of these tables as they are going to appear inside your data warehouse. Screenshot_2019-07-15_at_15.50.05.png Last, we allow to filter the users and accounts that you want to send to your data warehouse. You can either choose to send all the segments or select the segments users need to belong for their data to be sent.

Basic batch consistency and visibility

Hello,

We are super happy to announce you a new enhancement to the Outgoing Backlog Metrics feature.

Quick reminder before: Since a few weeks, you can now have access to the number of entities which are waiting to be processed out of Hull to your third party tools. These entities are called backlog. This feature allows you to better understand the processing delays that result in some attributes not being yet updated in your third party tool. If you want to run into more details about this reminder, feel free to have a look at the official release available here : Basic Outgoing Backlog Information

However, you may have witnessed that some data was missing. Indeed, the Outgoing backlog as it was computed before did not take into account the backlog coming from the manual batch operations. The manual batches have now been added up to the Outgoing backlog so that now you can see the exact total outgoing delays information.

Segment last change commit message

Hey there,

The commit message feature on the connectors' settings was very well adopted. It seems it has relieved you from the stress of not knowing what the other collaborators inside your organisation changed in the settings of the connectors.

We are glad to announce that we have added this feature to the segments. So, from now on, you will be able to document what's the purpose of this new segment you created and/or what changes you provided and why. Note that only the last commit message will be displayed and that it will pop up when you hover on the name of the last user who changed the segment.

We know segments can be handled by many collaborators inside your company and that you can lose track of what they all do so we hope this feature will help you solve that.

Here is a screenshot to show you how it works: commit_changes_segment_1.png commit_message_2.png