Movable Ink Destination
Movable Ink lets email marketers deliver jaw-dropping customer experiences. Our cloud-based software activates any data to generate intelligent content at the moment of open.
This destination is maintained by Movable Ink. If you have any issues, contact Movable Ink at email@example.com.
This document is about a destination which is in beta
This means that the Movable Ink Destination is in active development, and some functionality may change before it becomes generally available.
Perform the following steps to get started with Segment’s Movable Ink destination:
- Ensure you have an active Movable Ink account.
- Turn on the Movable Ink destination using the Segment dashboard.
- Talk to your Movable Ink account manager to get your Movable Ink API key.
- Enter the API key into the Movable Ink destination settings.
- set up the Segment SDK to send
identifyevents to Movable Ink.
If you’re not familiar with the Segment Specs, take a look to understand what the Identify method does.
When you send an
identify event with one of Segments sources, this is passed to the Movable Ink API and includes the user
traits you provide along with the previously used
anonymousId as well as the
userId that was given.
Once the Movable Ink API receives this
identify event, it will associate the events made by the previous
anonymousId to the provided
traits.email if one is provided. From that point on, the events will now appear in the user profile. This enables Signals features such as behavioral targeting, as well as content integrations like Behavioral Apps.
If you’re not familiar with the Segment Specs, take a look to understand what the Track method does.
When you send a
track event with one of Segment’s sources, Movable Ink will normalize them into the same events that Movable Ink’s API would normally receive. They will then be available to target against in behavioral marketing campaign content as well as being available in Custom Apps and Behavioral Apps.
Track events that are sent to Movable Ink will be attributed to the user identifier provided by any
identify call. This user identifier may be an email or another unique identifier if one exists for that user.
identify call has been made, then the events will be attributed to an anonymous user using the
anonymousId, until an
identify call is made and the
userId is set.
Events coming from Segment have a few required properties for them to work with Signals.
Ecommerce Supported Events
Movable Ink currently supports the Segment Ecommerce event specification, and in the future Movable Ink may expand the supported events to work with additional client use cases.
Product Viewed and
track events must include the following properties in order for them to be used in Signals:
Order Completed is used to create conversion events in Signals. The required properties are:
productsto list the products that were purchased. Each item in this list must contain the properties
product_idas well as
- Send a
trackevent with no identity, it will attribute to an anonymous user.
- Send an
identifyevent to set the user identifier.
- Send another
trackevent. It will be attributed to the user set by the
No Events in Movable Ink associated with profiles
Product Viewed and
Product Added must include
product_id and must include a
url. These properties enable events to be associated with an user’s profile.
For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Personas sends an Identify call with the property
order_completed_last_30days: true. When the user no longer satisfies this condition (for example, it’s been more than 30 days since their last order), Personas sets that value to
When you first create an audience, Personas sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.
Real-time to batch destination sync frequency
Note that real-time audience syncs to Movable Ink may take six or more hours for the initial sync to complete. Upon completion, a sync frequency of two to three hours is expected.
Segment lets you change these destination settings from the Segment app without having to touch any code.
Adding Movable Ink to the integrations object
To add Movable Ink to the
integrations JSON object (for example, to filter data from a specific source), use one of the following valid names for this integration:
This page was last modified: 08 Mar 2022
Questions? Problems? Need more info? Contact Segment Support for assistance!