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.


Connector settings changelog

Many of you have requested more clarity around configuration changes within a connector. This highly sought-after new feature will display a log of the revisions made to a connector configuration, and can be found on the connector's "Overview" page.

In the Timeline section below the graph, the list of changes are now displayed as an inline text with information about the changes as well as the person who committed the change.


Moreover, these inlines are clickable, and when clicked, will display a side panel with additional details about the changes made. See below for an example.


We hope this new feature improves your ability to collaborate, communicate, and find clarity with your team.

Unify statistics for all user and account visible attributes

We've improved the Attributes page for both Users and Accounts, and unified the experience by showing the same types of attributes for both.

The list of attributes is as follows:

  • Column Count : this is the number of times the attribute was updated in the selected time period
  • Column Users/Accounts : this is the number of distinct entities updated in the selected time period for all visible user and account attributes
  • Column Updates/User and Updates/Accounts : Per User/Accounts, number of attributes' updates
  • Column Segment : Number of segments a given attribute is used in
  • Column Updated by : The connectors in your organization that updates this given attribute
  • Column Status : Hidden / Visible / Visible and Tracked on the User or Hidden / Visible on the Account. Indeed, we do not track events on the Account level.

Attributes on the Users level : 1).png

Attributes on the Accounts level :


Show which segments reference an attribute

Hi there!

Several customers have mentioned that it is unclear if a given attribute is being used as a segment filter. This made it difficult to quickly understand which attributes were safe to deprecate.

Going forward, we will now expose this in the Attributes list and Details views so that you can quickly assess if any given attribute is required by a segment.

This newly added Segments column is sortable, allowing you to see which attributes are used in the most segments.


Basic outgoing backlog information

Hey there,

In order to provide more transparency into your data flow progression, we've introduced a way for you view your outgoing traffic backlog.

From the overview page, you can access a column on the connector list that shows a number that represents the size of the outgoing backlog. This backlog size is represented represents the following numbers:

  • 0
  • < 500
  • then rounded to hundreds: ~600, ~700, ~800, ~900
  • then rounded to thousands: 1k, 2k, 20k
  • then > 999k

You can also see the backlog trend in the form of a rising or falling arrow or a steady line. This trend illustrates the changes in the backlog over the last hour. This icon is displayed as follows:

  • if the change was above zero we show a growing arrow
  • if the change was below zero we show a shrinking arrow
  • if the change is zero we show a steady line


Furthermore, you can now view the backlog for individual connectors from the connector overview screen, which will specifically show that connector's outgoing backlog over the last few hours.


You can learn more about this in the documentation for outgoing backlogs

Slack notification triggers for Account changes and activity

Hey there,

A highly requested feature has now been released.

Previously, only User activities could trigger a Slack notification. Now, you can also have Account change notifications in Slack! Using the Slack connector, you can configure notifications to fire whenever an account enters or leaves a segment.

Here's how:

  • First, you can choose a "Built-in" event between "Entered User Segment" or "Left User Segment". Hull does not support events on the Account level hence the possibility to select only "Built-in" Events. slack_1.png

  • Then, you can choose between "Built-in" Segment which is basically "All users" and "Custom" Segment which encompasses all the segments that you created on the Account level inside of your organization. slack_2.png

  • Finally, like on the User level, you can select a #channel or a @user in Slack to send the message to. This message will contain all the Account attributes that you can select inside the Account Attribute White List below: slack_3.png

For instance, if you have an account segment called "Inactive accounts" which you configured in order to track accounts that are potentially at risk, you can now notify your CS team whenever an account falls into that category!

More validation rules

Hey there,

You may have noticed some invalid domains that are creating issues when they are ingested inside Hull's platform. To prevent this behavior, we have worked on implementing a more unified way of controlling data that is ingested with new validation rules.

The first addition is verification on the Account level. There are two ways to do this:

  • A regular expression on the account's external ID: you can now use regex to validate account external ids in addition to user external ids.
  • Domain blacklisting: you can now define domains that you want to be excluded from account identity resolution.

The second new capability is that you are now able to define the actions that you want to trigger on the accounts or users that you have blacklisted. You can now trigger the two actions below:

  • Move to anonymous ID: The invalid identifier will be stored as an anonymous ID, so that you can inspect it afterwards and/or process with custom Processor logic. If this action is picked for the account domain, the account will remain anonymous.
  • Ignore: Reject the account or user identifier from the incoming payload. The payload will be rejected if this was the only identifier sent for the user and/or account.

More validation rules.png

Display data ingestion errors and input record in logs in Dashboard

Hey there,

Today we're announcing a major improvement: We've leveled up our logging and the result is that we've considerably improved the clarity in how we represent the traffic flows into your Hull account.

Previously, each connector was responsible for logging the incoming data individually. This worked, but it lacked reliability and clarity in some specific but critical situations:

  • It was not apparent if the platform ended up rejecting the payload due to invalid data
  • It didn't show you which user the log was actually tied to
  • It didn't show logs for data ingested through our Bulk import feature (which some connectors such as the SQL connector are using)
  • It sometimes lacked consistency because it was manually implemented.
  • Custom and forked connectors, which don't have access to the logging infrastructure couldn't expose those logs.
  • Inconsistent formats and listing of touched attributes

Today we're happy to announce that we're now generating reliable ingestion logging data from the platform's ingestion steps for all connectors and all data sources.

Here are some of the benefits of this new architecture:

Transparent support for logs even from forked connectors

For those of you who are using custom forked connectors, this is big! You'll now start seeing ingestion logs for your connectors and you will be able to see what was sent and how it was ingested.

Logging of import job ingestion logs (this one is big for SQL connector users)

The SQL connector and others who are using our bulk import API weren't generating per-user and per-account logs, which made that data invisible in the logs. Now, they're generating the same data as the others.



More details about the ingestion decisions made by the platform.

The Hull platform has validation rules to ensure proper data is ingested. For instance, we filter domains at the account level so that we don't create accounts based off of "freemail" domains (think Sometimes, data is simply invalid and we're forced to drop the payload entirely. If such an error occurs now, you'll be able to see it and understand why.


Uniform support for captured attributes

We're now showing all the attributes that were received. This lets you search for them and see exactly what data was received and which user it was resolved to, making the process of analyzing data flow a much simpler process.


Uniform support for attribute changes

Within the logs, we're now showing the full list of attribute change made to a user. Not only do you see which data we captured, but you'll also see which attributes were modified, and the changes it made to the resolved profile. This makes it easy to identify loops and other data flow issues.

Changes_incoming_records (1).png

Outgoing Webhooks Account Support

Hey there,

We're pleased to announce an improvement to the Outgoing Webhooks connector! You are now able to send Accounts through this connector, whereas you were previously only able to send Users. See below for a glance at this new feature!


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