Supported syncing
For more information about sync modes, refer to the sync modes docs.
Connect to Movable Ink
To connect Movable Ink to Hightouch you need an endpoint URL, an access key, and an access secret. Movable Ink’s Client Experience team provisions all three. Hightouch authenticates each request with HTTP Basic auth.- Go to the Destinations overview page and select Add destination.
- Select Movable Ink from the destination catalog.
-
Enter the following credentials, then select Continue:
- Endpoint URL: the Customer Data API endpoint provided by Movable Ink. The shape is
https://collector.micpn.com/behavioral/<key>for US accounts orhttps://collector.micpn-eu.com/behavioral/<key>for EU accounts, where<key>is your account-specific path segment. - Access key: the username portion of HTTP Basic auth.
- Access secret: the password portion of HTTP Basic auth.
- Endpoint URL: the Customer Data API endpoint provided by Movable Ink. The shape is
Contact your Movable Ink Client Experience team if you don’t have an endpoint
URL or credentials yet. Movable Ink’s developer reference
(
learning.movableink.com) requires a customer login.Sync configuration
Sync events
Send behavioral events to Movable Ink. Hightouch inserts one event per row in the model’s query results each time the sync runs.Event type
Select the Movable Ink event type for this sync:Identifiers
Map at least one identifier per event:
Rows with neither a User ID nor an Anonymous ID are rejected without aborting the sync. You can review rejected rows in the Live debugger.
Event timestamp
Map a model column to the event timestamp. If left unmapped, Hightouch defaults to the time the sync sent the event. Hightouch validates that the timestamp is no more than 30 days in the past and no more than 1 day in the future. Events outside that window are rejected.Field mapping
The mappable fields depend on the event type:
For Order Completed, the Products field expects an array of product objects. Use Hightouch’s inline mapper or an array column from your model.
For Custom events, Movable Ink supports up to 10 unique custom event names per account by default. Contact your Movable Ink rep if you need more.
Payload limits
Movable Ink rejects events that exceed its payload limits. Hightouch checks these before sending and rejects offending rows:- Any string field longer than 256 characters.
- A total event payload larger than 32 KB.
Tips and troubleshooting
To see the exact API requests and responses from each sync run, use the live debugger. To get notified by Slack, PagerDuty, SMS, or email when a sync fails, set up sync alerts. If you run into an issue this page doesn’t cover, .Validate your setup
After your first sync completes, confirm the events landed in Movable Ink:- Ask your Movable Ink Client Experience team to confirm events are arriving on the configured endpoint. Movable Ink’s developer site (
learning.movableink.com) is customer-login-gated, so direct verification from Hightouch’s side ends at a successful HTTP 2xx response from the Customer Data API. - Check the Live debugger for rejected rows. The most common rejections are missing identifiers, missing event names on custom events, out-of-window timestamps, oversized string fields, and oversized payloads.