Skip to content

Commit 3f11fda

Browse files
authored
Merge pull request #5720 from segmentio/thomas/movable-ink
add docs for new movable ink destination
2 parents 8334a09 + 10e363e commit 3f11fda

File tree

1 file changed

+56
-0
lines changed
  • src/connections/destinations/catalog/actions-movable-ink

1 file changed

+56
-0
lines changed
Lines changed: 56 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,56 @@
1+
---
2+
title: Movable Ink (Actions) Destination
3+
id: 6537b55db9e94b2e110c9cf9
4+
beta: true
5+
---
6+
7+
[Movable Ink](https://movableink.com/){:target="_blank"} lets email marketers deliver jaw-dropping customer experiences. Movable Ink's cloud-based software activates any data to generate intelligent content at the moment of open.
8+
9+
This destination enables you to send Segment event data which can be used to automatically generate personalized content at scale across email and mobile experiences.
10+
11+
> info ""
12+
> This destination is maintained by Movable Ink. For any issues with the destination, please reach out to your Movable Ink Client Experience team.
13+
14+
## Pre-Requisites
15+
16+
A Movable Ink Stories license is required to use this integration. Please reach out to your Movable Ink client experience team with any questions.
17+
18+
You'll need to share sample event payloads with your Movable Ink Client Experience team before enabling the destination in Segment. Your Client Experience team will then work with a Solutions Architect to map the event within Movable Ink and share an endpoint URL, access key ID, and access secret. This event mapping in Movable Ink and API credentials are required for a successful response.
19+
20+
### Find sample event payloads in Segment:
21+
22+
To find sample event payloads in Segment:
23+
24+
1. Navigate to **Connections > Sources** and click on the source you’d like to stream data from.
25+
2. Select the **Debugger** tab. You'll see a list of incoming sample events.
26+
3. Select the event you’re interested in, then select **Raw** to view a full sample payload.
27+
4. Copy and paste this sample payload and share with your client experience team.
28+
29+
Your client experience manager will then provide you with a Movable Ink endpoint URL, access Key ID, and access secret.
30+
31+
## Getting started
32+
33+
1. From the Segment web app, navigate to **Connections > Catalog**, then select **Destinations**.
34+
2. Search for "Movable Ink (Actions)" and select it.
35+
3. Click **Add Destination**.
36+
4. Within the **Settings** tab of your destination, input your Movable Ink API credentials into the following fields:
37+
- **Username**: paste your Movable Ink Access Key ID
38+
- **Access Secret**: paste your Movable Ink Access Secret
39+
- **Movable Ink URL**: paste your Movable Ink Endpoint URL
40+
41+
## Select events and event properties to stream to Movable Ink
42+
43+
"Send Entire Event" is the only action available with this destination. To configure this action:
44+
1. Navigate to the **Mappings** section of your destination.
45+
2. Select **Edit Mapping** and tailor the events you wish to send by adding or removing conditions that trigger this action.
46+
3. Preview the data:
47+
- Load a test event from the source or use a sample event for data preview.
48+
4. Map specific fields (optional):
49+
- Click **Test Mapping** to send a test event and identify any potential issues.
50+
- Return to the Mappings overview page and enable your mapping.
51+
6. Navigate to your integration’s **Settings** tab and activate the integration by toggling on **Enable Destination**.
52+
53+
> info ""
54+
> For any unexpected errors, contact your Movable Ink client experience team with the full sample payload.
55+
56+
{% include components/actions-fields.html %}

0 commit comments

Comments
 (0)