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:


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.


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.

Basic batch consistency and visibility


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.

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.

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

Visualize the mapping between segments and connectors

Hey there,

Sometimes, you want to remove a segment but before clicking on the delete button you want to make sure that this segment is not used in any of your connectors.

Some of you told us that if you could easily see in which connectors that given segment is used, this would enable you to find out if you can safely remove it.

So, we released a new feature that allows you to see the list of connectors in which the segment is used by hovering on the number of connectors it is used in.

Here is a screenshot showing the feature :


Segments changes information

Hey there,

Several people inside your company may create segments inside your Hull organisation. Before, it was quite difficult to keep track of who changed or created a segment: whenever you witnessed a change, you had to ping your collaborators inside Hull to ask about who changed the segment and when.

To solve that problem, we now display under the name of the segment who in your organisation changed the segment and when (you can display the exact time by hovering on the date):


JSON Support

Hey there,

We are excited to announce that we now support JSON objects as User and Account attributes.

We're especially proud of this, as many other services do not support capturing and storing JSON data. They traditionally only support "primitive" types, such as: strings, numbers, booleans, date, arrays.

This results in important data being incompatible with the service. Some tangible examples of this might include stripe subscription data, web sessions, and calendly webhooks, just to name a few. You are now capable of capturing JSON objects like these inside Hull, where you can then transform and transmit this data exactly how and where you need it.

Here's how some of our customers are already benefiting from this new feature:

  • capture customer data from their customer success tool (like Vitally) and synchronize it back to other tools.
  • capture opportunities as a JSON object and send it to their CS tools in order to keep their CS team up to date on their customers.
  • capture sessions as a JSON object to then run logic to make accurate attribution analysis.

Practically, the JSON objects will be visible from the User and Account pages as follows:


You can also access them inside the User and Account attributes pages and are displayed as JSON type:


At the moment, it is not possible to create segments based on JSON objects.

We are confident that this new feature will allow you to capture more raw data from your different tools in order to synchronize them to your entire MarTech stack.

Ultimately, this new feature will allow you to capture, manipulate and synchronize even more data across your MarTech stack - unlocking tons of additional value for you.

We encourage you to read our updated Docs to see more examples of what you can achieve with this feature.

Move organization settings to user menu

Hey there,

We wanted to let you know about a small UI change. We have moved the "Settings" tab to the user profile panel and is now accessible under the name "Organization settings".


Copy segment names

We've made a slight improvement to the segment views for your convenience. You can now copy a segment name to your clipboard by clicking the "..." button, and selecting "copy segment name" from the drop-down list.


No published changelogs yet.

Surely Hull will start publishing changelogs very soon.

Check out our other public changelogs: Buffer, Mention, Respond by Buffer, JSFiddle, Olark, Droplr, Piwik Pro, Prott, Ustream, ViralSweep, StartupThreads, Userlike, Unixstickers, Survicate, Envoy, Gmelius, CodeTree