Overview

Movable Ink Da Vinci is an AI-powered email orchestration and personalization platform. Simon Data sends contact, transaction, and product data to Movable Ink Da Vinci over SFTP, enabling Da Vinci to power personalized email campaigns with up-to-date customer and behavioral data.

📘
This integration is separate from Movable Ink Studio
Movable Ink offers two distinct products. The Movable Ink Studio integration handles real-time content generation for messages delivered by your ESP. Da Vinci is a separate AI orchestration platform that uses batch data feeds to drive email decisioning. They are configured independently.

Action Type

Action	Function	Connected Flows	One-time	Triggered	Stream	Recurring	Journeys
Send File to Movable Ink Da Vinci (via SFTP)	Deliver a flat file of customer data to a Movable Ink Da Vinci SFTP connection	❌	✅	✅	❌	✅	✅

Authentication

To authenticate the Movable Ink Da Vinci integration, reach out to your Simon Data account manager. Your Movable Ink Implementation Architect or Client Experience Manager will provide the SFTP connection details required for setup.

You will need the following information from Movable Ink:

Host — the SFTP server hostname
Port — typically 22
Username — your SFTP account username
SSH Private Key or Password — your authentication method
GPG Encryption Key (optional) — required if you want to use PGP encryption, which Da Vinci supports and recommends

Data Feeds

Da Vinci requires three types of recurring data files. Each should be configured as a separate Simon flow or journey. Movable Ink will specify the exact file naming pattern, cadence, and required fields for your account during onboarding.

Contacts

Deliver contact attributes — email address, customer ID, opt-in status, and profile data — to Da Vinci once daily, ideally in early morning before business hours.

Recommended file name pattern:

DV_contacts_{clientname}_{label}_{{ now() | format_datetime('yyyyMMddHHmmss') }}.txt

Example: DV_contacts_acmecorp_attributes_{{ now() | format_datetime('yyyyMMddHHmmss') }}.txt

Required fields:

Field	Description
Email address or reference ID	Primary key — must map one-to-one with the email identifier in your ESP
Customer ID	Used to link transaction records
Opt-in status	One or more fields that indicate email opt-in
Template fields	Any fields needed for email components (e.g. first name, postal code)

Transactions

Deliver recent purchase and behavioral data to Da Vinci once daily. Each file should cover a 1–5 day lookback window.

Recommended file name pattern:

DV_transactions_{clientname}_{{ now() | format_datetime('yyyyMMddHHmmss') }}.txt

Required fields:

Field	Description
Customer ID	Must match the customer ID in your Contacts feed
Order / transaction ID	Unique identifier for each transaction
SKU or product identifier	Links to the Products feed
Transaction timestamp	ISO 8601 format (e.g. `2024-08-27T12:34:00`)
Revenue amount	Per-SKU revenue in dollars, excluding shipping and tax
Quantity	Per-SKU quantity purchased

🚧
Historic transactions
Da Vinci requires a one-time historic transactions file (1–5 years of history) in addition to the recurring feed. This is typically coordinated with your Movable Ink Implementation Architect. Contact your Simon Data account manager to set up a one-time flow for this initial backfill.

Products

Deliver product catalog data to Da Vinci at least once weekly.

Recommended file name pattern:

DV_products_{clientname}_{{ now() | format_datetime('yyyyMMddHHmmss') }}.txt

Required fields:

Field	Description
SKU	Primary key — must be unique; no duplicates
Product ID	Required if SKU is variant-level (e.g. color/size)
Division	e.g. Mens, Womens, Kids, Home
Category	e.g. Jackets
Section	e.g. Denim Jackets
Product title	Full product name

File Requirements

Movable Ink Da Vinci has strict requirements for all delivered files:

Compression or encryption required: Files must be gzip compressed, bzip compressed, or PGP encrypted. Do not combine compression with PGP.
File extensions: .txt (uncompressed), .txt.gz (gzip), .txt.pgp or .txt.gpg (PGP)
Encoding: UTF-8
Headers: All files must include a header row
Column names: Cannot contain spaces or these special characters: ; { } ( ) \n \t =
Date and datetime fields: Must use ISO 8601 format
Sensitive data: Movable Ink Da Vinci does not permit Sensitive Personal Data, including government-issued IDs, financial account numbers, health or biometric data, or other legally designated sensitive categories

📘
PGP encryption is recommended
Movable Ink Da Vinci supports PGP encryption and requires files to be either compressed or encrypted. Contact your Simon Data account manager to configure a GPG encryption key on your credentials, then enable the Enable PGP encryption option on each flow action.

Use the Action

Once your account is authenticated, add the Send File to Movable Ink Da Vinci (via SFTP) action to a flow or journey:

Create a flow or journey.
Under Destination, choose Moveable Ink Da Vinci as the channel and Send File as the action.
Set File Path and Name using the file naming pattern provided by your Movable Ink Implementation Architect. Use a Jinja datetime expression to include a timestamp, which Da Vinci requires for unique file delivery.
Add the Fields corresponding to the data feed type (Contacts, Transactions, or Products).
If PGP encryption is configured on your credentials, enable Enable PGP encryption.

Configuration Parameters

Parameter	Description
`File Path and Name`	Remote path and file name. Must include a Jinja timestamp per Da Vinci's naming specification. Do not begin with a forward slash.
`Fields`	The fields to include in the output file. No fields are included by default — add all required fields for the feed type.
`Enable PGP encryption`	Encrypts the output file with PGP before delivery. Only appears when a GPG encryption key is configured on your credentials.

📘
Dynamic file names are required
Da Vinci's file naming specification requires a timestamp in every file name. Always include a Jinja datetime expression such as {{ now() | format_datetime('yyyyMMddHHmmss') }} to satisfy this requirement and prevent file overwrites.
Example: DV_contacts_acmecorp_attributes_{{ now() | format_datetime('yyyyMMddHHmmss') }}.txt

🚧
Coordinate field schemas with Movable Ink before launch
Once your production feeds are live, any changes to file name patterns, field names, or delivery timing require at least 5 business days' notice to your Movable Ink account contacts. Align on your schema during onboarding before activating flows.