Integrations

Movable Ink - V2
CategoriesAll

Event

Movable Ink enables brands to create compelling and unique visual content based on customer-specific data. Combine data from mParticle to produce even more relevant and personalized content.

Prerequisites

In order to enable mParticle’s integration with Movable Ink, you will need a Movable Ink account to obtain your configuration details, as well as a Stories behavioral license with Movable Ink. Contact your Movable Ink Client Experience (CX) team to get your API credentials for activating the connection with mParticle.

Supported Platforms

  • Android
  • iOS
  • Web
  • Custom Feeds

Supported Identity Types

mParticle will forward the following User Identities to Movable Ink:

  • mParticle ID
  • Customer ID
  • Device Application Stamp

Data Processing Notes

Movable Ink will not accept data older than 30 days.

Event Data Mapping

mParticle’s integration forwards the following event types to Movable Ink:

  1. Commerce Events (product_action)
  2. Custom Event
  3. User Identity Change

Commerce Events

The following sections describe product_action.action types and how they map to Movable Ink events.

AddToCart

Each item in the products array maps to one Movable Ink cart_add event. Relevant fields below are for each item in the product_action.products[] field.

Required Fields

  • product_action.products[].id: Uniquely identifies this product.
  • event_name: Must have a value to identify the event.
  • custom_attributes.timestamp: Timestamp of when the event occurred.

Optional Fields

  • product_action.products[].name: The name of the product.
  • product_action.products[].category: A category identifier that will associate this product with Movable Ink category events. Value passed should match the custom_attributes.list_id value in Product List View events, see below for details.
  • product_action.products[].price: The price for a single product.

ViewDetail

Each item in the products array maps to one Movable Ink product event. Relevant fields below are for each item in the product_action.products[] field.

Required Fields

  • product_action.products[].id: Uniquely identifies this product.
  • event_name: Must have a value to identify the event.
  • custom_attributes.timestamp: Timestamp of when the event occurred.

Optional Fields

  • product_action.products[].name: The name of the product.
  • product_action.products[].category: A category identifier that will associate this product with Movable Ink category events. Value passed should match the custom_attributes.list_id value in Product List View events, see below for details.
  • product_action.products[].price: The price for a single product.

Purchase

Maps to one Movable Ink conversion event. All product_action.products[] field items are associated with one conversion event. Optional fields which are not included will use data from an associated Movable Ink product event.

Required Fields

  • product_action.products[].id: Uniquely identifies this product.
  • event_name: Must have a value to identify the event.
  • custom_attributes.timestamp: Timestamp of when the event occurred.

Optional Fields

  • product_action.products[].name: The name of the product.
  • product_action.products[].category: A category identifier that will associate this product with Movable Ink category events. The value passed should match the custom_attributes.list_id value in Product List View events. See the following section “Custom Event” for details.
  • product_action.products[].price: The price for a single product.
  • product_action.products[].quantity: The quantity of the product.
  • product_action.total_amount: The combined cost of all products included in the event.
  • product_action.products[].custom_attributes.url: Contains the page URL for the specific product purchased.

Note: An alternative URL location can be specified in the URL Custom Attribute Name Configuration Setting.

Custom Event

Movable Ink also accepts Custom Events like (Product List View). Custom events can be mapped to Movable Ink so long as the below fields are available:

Required Fields

  • event_name: Must have a value to identify the event.
  • custom_attributes.timestamp: Timestamp of when the event occurred.

Optional Fields

  • custom_attributes.field: up to 20 additional fields associated with your custom event can be sent to Movable Ink.

Configuration Settings

Setting Name Data Type Default Value Description
POST URL string Your dedicated API endpoint to send your event to. Can be retrieved by contacting your Movable Ink Client Experience (CX) team.
Authorization Header string The HTTP header to include in the POST request. Movable Ink will provide a Secret and Access Key that must be converted into a base64 encoded string.

Connection Settings

Setting Name Data Type Default Value Platform Description
Include Location Information bool False All If enabled, location data will be forwarded with event data whenever possible.
Include Metadata bool True All If enabled, the following metadata - application_info, device_info and source_info will be forwarded.
Include User Attribute Change Events bool True All If enabled, User Attribute Change Events will be forwarded.
Include User Identity Change Events bool True All If enabled, User Identity Change Events will be forwarded.
Send Batches without Events bool False All If enabled, an event batch that contains no events will be forwarded.
Include Event Batch Location bool False All If enabled, event batch context.location data will be forwarded with event data.

Was this page helpful?