Providing relevant and timely customer interactions relies on fresh and accurate data in your Iterable account. By automatically syncing customer data from your data warehouse into Iterable, you don't need to worry about data consistency or staleness. Instead, you can focus on building world-class customer experiences.
Update user's shopping cart and creates event for it
Insert
Catalogs
Sync data from any source to your Iterable catalogs
Insert
Segments
Create new or use existing list to sync users to it
Insert
Update email address
Update user email address
Update
User API actions
Delete, forget, or unforget users.
Insert
To ensure syncs send each event, use a hash function for the event model's primary key . The hash should combine all columns, including member ID, timestamp, etc. See the event sync documentation for more information.
Hightouch lets you send data to user data fields. You can map data to existing fields or to new fields.
When creating new fields, Iterable automatically generates a schema for that field based on the first data sent.
You cannot change the schema once it's set. See Iterable's article here.
Iterable supports user and event attributes containing JSON objects or arrays of objects. These objects and object arrays are commonly used to support "entities" related to each user—for example, devices, medications, pets, etc.—especially when marketing communication needs to include metadata about these related entities.
Hightouch is a great tool to sync to these types of attributes because you can leverage your data warehouse to manage these associations. To do so, you must build the full JSON object into a single column within your Hightouch data model.
Modeling nested attributes into JSON can be done in a few ways:
Natively in the warehouse, for example with ARRAY_CONSTRUCT(value1, value2, ...) or ARRAY_AGG(column) SQL functions
Let's say you want an array of a customer's pets to be an attribute named pets in Iterable. You would need a data model with a column named pets and would then build the full JSON pets object array to populate that column. This array might look something like this:
Add context to your custom events by mapping data fields to them. Your must provide at least an email or user ID in your mappings. The integration uses these fields for identifying the user associated with this event. If you provide both, email takes precedence.
These fields can be modified on an existing event:
Event name
Campaign ID
Template ID
Timestamp
Custom fields (Mappings)
Any custom destination fields are provided to Iterable in the dataFields property of the request.
Sync purchase events to track them in Iterable. The integration inserts new events into Iterable when they first appear in your query results. It then keeps those events up-to-date using the event ID.
You are required to provide the shopping cart items as Items and the Total order dollar amount in the mappings. You must also provide at least an email or a user ID in your mappings.
The integration uses the email or user ID for identifying the user associated with the event. If you provide both email and user ID, email takes precedence. See Iterable's API documentation for more information.
You are required to provde the shopping cart items as Items.You must also provide at least an email or a user ID in your mappings.
The integration uses the email or user ID for identifying the user associated with the event. If you provide both email and user ID, email takes precedence. See Iterable's API documentation for more information.
You can either use email or user ID to map records from your query results to your users in Iterable. If you match by email, the update call is only made the first time the record appears in your query results.
Matching by user ID makes an update email call the first time the record shows up in your query results and every time changes in your record are detected.
You can either use email or user ID to match records from your query results to your users in Iterable.
You should select the one that corresponds to the project type you selected when first setting up your project type.
Hightouch provides complete visibility into the API calls made during each of your sync runs. We recommend reading our article on debugging tips and tricks to learn more.