Connector Documentation Supercharge your email engagement in to Hull Mapping Object Captured in Hull as Description
Customer Subscribed
User Event

Captured as a User Event in Hull

Customer Unsubscribed
User Event

Captured as a User Event in Hull

Email Bounced
User Event

Captured as a User Event in Hull

Email Clicked
User Event

Captured as a User Event in Hull

Email Delivered
User Event

Captured as a User Event in Hull

Email Converted
User Event

Captured as a User Event in Hull

Hull to Mapping

Hull Object Sent to as Description
User Event Email Delievered

Any Hull Event

User User

Hull Users will be sent to along with the selected attributes Connector

The Connector enables your team to automate customer lifecycle emails and campaigns by synchronizing users from Hull with It also has the ability to send email activity events to Hull.


The Connector allows you to:

  1. Synchronize users in Hull with persons in to automate customer lifecycle emails and campaigns
  2. Forward events/activities from Hull to to trigger powerful workflows such as sending emails, SMS and more
  3. Feed events related to email activity from into Hull where you are able leverage this information in your other connected tools.

The Connector supports the actions update traits and create events.

Getting Started

Authorize outgoing traffic

  1. In head to Integrations and select API section. At the top of the screen you will find SITE ID and API KEY.

Go to Integrations in

Go to API

Copy Credentials in

  1. In Hull, open the Settings tab of your connector, scroll down to the Credentials section and fill in the SITE ID and API KEY.

Paste Credentials

That’s it! The connector is now ready to send data to!

Receiving Email activity from

To receive customer activity from you need to tell to send events to Hull when something happens.

  1. Start by opening the Settings tab in Hull, and copying the generated Webhook URL: Copy Webhook Url
  2. Then go to
  3. Click on “Integrations”.
  4. Find and click on “Email Activity Webhooks”.
  5. Paste the URL you copied in the box. Check all event types below it.
  6. Click on the button “Send Test” and save your changes if the symbol indicates success. Paste Webhook Url in

That’s it! The connector is now ready to receive data to!


When connector is authorized against API, it’s time to define what data exactly will be send and received from

Sending Users

Start with Outgoing Mapping section in the settings.

The most important decision you have to make here is which user attribute to send as the **customerId** to which is the unique identifier within Our recommendation is to either use the external_id if you assign your own identifier to users in Hull or use the Hull id.

To send users to, first define which whitelisted segments users will need to belong to. If the segments are not specified, users will not be sent to Second, specify which attributes will be sent from Hull to By default, the attributes email, customerId and hull_segments (all the segments the user belongs to) will be sent to

IMPORTANT: Please keep in mind that API allows to send maximum 30 attributes per API call so bigger number of selected attributes will double the number of API calls and can make the connector slower.

When users leave all whitelisted segments, you have to ability to remove that user from To enable this feature, toggle on enable user deletion and the connector will automatically remove users from if they no longer belong to any of the whitelisted segments. Otherwise, if a user leaves all whitelisted segment it will be kept in, but will no longer receive updates.

Furthermore, you can specify which events will be sent to by selecting the events from the dropdown list. By default no events are sent. Each outgoing event will create a new activity in For all events except Page View Events (see below), the activity type will be set to “Event” and the activity name will have the same name as the Hull event, which allows basic segmentation in

Sending Page View Events allows you the option to handle Page View Events differently than generic events. To begin sending these events to, in the connector settings, add the page event to whitelisted events list. The connector will then send all future Page View Events to as activities. Unlike generic events, the type of the activity will be set to “Page” and the name of the activity will be the url of the Page View. This is aligned with documentation on tracking page views and allows you to build more fine grained segments in The url of the Page View activity will be picked from Hull Event url property, or, if not available, will fall back to the page_url context property. Additionally, a referrer will be added to the activity.

Sending Anonymous Events

You can also activate Anonymous Events, which is an advanced feature in If you are not familiar with this feature, please refer to’s documentation.

Optional - receiving subset of events

You are able to limit the events Hull will receive from The list of all events is available in the docs under

To customize this list, navigate to your dashboard, select Integrations from the menu on the left, and navigate to Email Activity Webhook card:

Webhook Events Step 1

On the next page, you can select the events you want to receive from the list and save your changes:

Webhook Events Step 2

Get a customized demo

Book a personalized demo with a product expert to see how Hull can help you unify data across your entire stack.