Movable Ink Integration with Simon Data

Overview

Simon Data integrates with Movable Ink Studio to enable real-time and batch-based personalized content generation. Movable Ink Studio transforms customer data into dynamic, personalized visuals that can be embedded in marketing messages.

Important Note: Movable Ink does not deliver emails or mobile messages. Instead, it relies on customer engagement platforms like Braze, Attentive, Iterable, MoEngage, and Salesforce Marketing Cloud to distribute messages containing Movable Ink content.

Integration Methods

Simon Data supports multiple integration methods with Movable Ink:

1. Audiences API → Movable Ink

Movable Ink queries Simon's Audiences API at the moment of message open.
Retrieves Events or Profile Traits stored in the API.
Requires the customer to have purchased Movable Ink's Audiences API.

2. Simon → Movable Ink Webhooks

Simon Data sends Events and Profile Traits to Movable Ink.
Supports real-time data transfer.
Requires an endpoint URL and API credentials provided by Movable Ink.

3. Movable Ink → Simon Webhooks

Movable Ink sends Events or Profile Traits back to Simon Data.
Data can be stored as events or on user profiles for customers with Audiences API enabled.

4. Simon → Movable Ink CSV Exports

Simon Data exports customer data in CSV format for batch processing.
Suitable for clients who do not require real-time updates.
Audiences API or Webhooks are preferred for most cases.

Note: This is a beta integration. Details on methods 1, 3, and 4 will be added over time.

Webhook Integration (Simon → Movable Ink Webhooks)

Movable Ink's Customer Data API ingests behavioral event data in real time. Please reach out to your Movable ink solution architect and/or CX manager to have an endpoint and credentials generated and sent to the Simon Data team.

Required Fields

event_id: Unique identifier for each event.
ts: Timestamp of the event.
customer_id_: Unique user identifier that aligns with the mi_u parameter in Movable Ink.

API Endpoint

https://collector.movableink-dmz.com/behavioral/{key}

HTTP Method: POST

Authentication

Basic Auth (username + password)

Headers

Authorization: Basic {credentials}
Content-Type: application/json

Additional Fields

Additional fields for events not predefined in the Movable Ink event schema need to be included in test payloads and sent to the Movable Ink team to be configured before events can be sent directly to the Movable Ink endpoint.

Payload Example

{
  "event_id": "12345",
  "ts": "2024-03-01T12:00:00Z",
  "customer_id_": "987654",
  "custom_event_date": "2024-06-15",
  "custom_event_field1": "Dummy data value $100"
}

Considerations

Message Size: Limited to 32kb.
Timestamp: Must be within the past 30 days and no further than 1 day into the future.
Field Size: String fields cannot exceed 256 characters.
Product Data Limits:
- products cannot contain more than 10 categories.
- conversions cannot include more than 100 products.
- product added and product viewed events cannot have more than 20 meta field entries.

Webhook Configuration

Movable Ink provides an endpoint URL and API credentials unique to the client's account.
Simon Data sends test payloads to verify event ingestion.
Movable Ink Solutions Architects configure the event mapping.
Webhooks are activated in the production environment.

Testing: Initial test payloads were sent through Pipedream and validated by Movable Ink before full implementation.

Summary

Simon Data's integration with Movable Ink enables real-time and batch data transfers, ensuring personalized and up-to-date marketing content. Customers can leverage APIs, webhooks, or CSV exports based on their needs. Movable Ink's Solutions Architects assist in configuring and validating data ingestion to ensure seamless integration.

For further assistance, please reach out to your Simon Data account representative or Movable Ink's Client Experience team.