Send attributes and events to Customer.io using Hull's Customer.io connector. This will allow you create targeted email sequences in Customer.io based on granular segments in Hull.
First, log-in to your Customer.io account and locate the Integrations
item on the menu to the left side of your screen. Click on the button Settings
next to Customer.io API
:
Then, copy the Site ID
and API Key
from the following page:
Go back to your Customer.io connector and paste those two elements respectively inside the Customer.io Site ID
and Customer.io API Key
placeholders inside the Credentials
section.
First, select the unique main identifier for each User. Be careful to select one that defines unequivocally Users to avoid the creation of duplicates.
You need to first select the segments Users need to belong to be sent out. A User that does not belong to any of those segments will not be synchronized put to Customer.io. You can select the segments inside the User Filter
dropdown:
Then, select the attributes you want to send on the Users. You will be able to choose these attributes inside Customer.io to create segments of people on which to trigger email sequences.
⚠️Warning ⚠️
Note that Hull also sends a default attribute called hull_segment
that will take as a value the name of the segments a User belongs to in Hull. It will be written in low case in Customer.io.
This attribute is very useful when you want to replicate a segment in Hull inside Customer.io.
By default, no event is sent from Hull to Customer.io. You can select the events you want to send inside the Events filter
dropdown:
You can also choose to delete the Users in Customer.io that do not belong to segments in Hull. This is useful to reduce the number of People to make sure you limit your Customer.io bill.
To do so, activate the toggle button called Enable User Deletion
:
We also have an advanced option that allows sending events to Users who do not have an email. You can activate it using the following toggle button. Before, please refer to the Customer.io to know more about setting-up Anonymous Events.