Filtering and mapping data to a DestinationUpdated 20/11/2019

Hull makes it easy to synchronize lists of users from one tool to another. To achieve that, our product provides connectors which for the main part have at least these two main features in their settings:

  • A whitelist segment placeholder: this feature allows you to select the segments of users you want to sync in your third party tool. It will help filter out the users that you want to synchronize and thus reduce the number of API calls in your third party tool.

Screenshot 2019-11-19 at 11.44.15

  • An attribute mapper: this feature allows you to map an attribute coming from the connector's third-party tool to an attribute inside Hull and the other way around. It gives you the flexibility to match any field inside Hubspot to a field into Hull to another field inside Intercom for instance.

Screenshot 2019-11-19 at 11.45.28 (1)

Configuring your whitelisted segments

Navigate to the settings of your connector. If the connector supports outgoing data, it will show an outgoing data section. If the connector supports users and accounts, it will show two outgoing data sections.

Screenshot 2019-11-18 at 14.42.13

You can see a placeholder called User filter or Account filter depending on whether you are handling users or accounts. Using this field, you will be able to select segments you have created in Hull. This placeholder will define the users or accounts you want to synchronise to the destination.

Important notes:

  • If you see that a user has not been updated inside your destinations, it is likely that he does not belong to one of the segments listed inside this placeholder.

  • The first time you set up your outgoing data, select the segments you want to sync and the attributes you want to match (see section below on the attribute mapper for outgoing data). However, to see your users inside the destination, you need to perform a manual push from the Users or Accounts list. This operation needs to be done once when you first set-up a connector.

Configuring the Attribute Mapper for outgoing data

Navigate to the attribute mapper of the outgoing data section of your connector.

Screenshot 2019-11-19 at 11.12.17

Click on the Edit the Mapping button to start selecting the attributes you want to send to your outgoing destination. You can see a modal with a list of attributes sorted by sources. Select the attributes you are interested in synchronising inside Hull.

Screenshot 2019-11-19 at 11.16.04

You see that they are autopopulated inside the Incoming data section.

Screenshot 2019-11-19 at 11.18.28

Now select one by one the corresponding attribute inside your Destination (here Hubspot) that you want to match to each of those attributes.

Screenshot 2019-11-19 at 11.21.27

If you don't find an attribute inside your Destination you want to match, you can create a custom attribute. To do so, you can directly create that new customer attribute from the attribute mapper. This will create a new field inside your destination automatically.

Screenshot 2019-11-19 at 11.24.43

⚠️ Warning ⚠️:

  • The creation of custom attributes directly from the attribute mapper only works for some connectors. For instance, the Salesforce connector will require you to first create a custom field inside Salesforce before making it available inside your attribute mapper. Once you have created a new field inside Salesforce, make sure to refresh your connector settings page in order to see the newly added field inside the mapper. Please refer to the connector's documentation to know how it handles outgoing custom attribute.

  • You need to make sure the data types are matching. This means matching a string with a string, a number with a number but also more complex combinations depending on the connector. Inside Hull, the attributes named with a _at suffix are considered as dates (ex: deleted_at). Please refer to your connector's documentation to figure out more about data type matching.