Skip to content

Getting Started with the MovableInk Mobile SDK

Welcome! This guide will help you understand what MovableInk is and what you'll need before integrating the Mobile SDK into your app.

What is MovableInk?

MovableInk is a marketing personalization platform that helps brands create dynamic, personalized content for email, mobile, and web channels. Our platform enables marketers to generate content that adapts to each recipient based on real-time data, user behavior, and preferences.

The MovableInk Mobile SDK connects your mobile app to this ecosystem, enabling two key capabilities:

  1. Deeplinking from Email Campaigns: When users tap links in marketing emails created with MovableInk, they can be routed directly into your app to specific content (product pages, categories, special offers, etc.)
  2. Behavior Event Capture: Capture user interactions in your app (product views, searches, purchases, etc.) to power personalized marketing content in future campaigns

Key Concepts

Understanding these terms will help as you work through the documentation:

Studio

MovableInk's content creation platform for email marketing. Marketers use Studio to create dynamic, personalized email content that can include deeplinking into your mobile app.

DaVinci

MovableInk's AI-powered personalization engine. DaVinci uses machine learning to deliver product recommendations and personalized content based on user behavior.

Creative Tags

Dynamic content blocks created in MovableInk that are embedded in marketing emails. When a user opens an email, Creative Tags generate personalized content based on the recipient's data.

MIU (MovableInk User ID)

A unique, non-personally-identifiable identifier that links your app users to their marketing profile in the MovableInk platform. The MIU enables consistent personalization across email and mobile app touchpoints.

Important: The MIU is not an email address or other PII. It's a unique identifier (typically a UUID) that your marketing team and email service provider use to identify users.

Special URLs in the format https://mi.yourcompany.com/p/... that appear in marketing emails. When clicked, these links:

  1. Resolve to a final destination URL
  2. Can deeplink directly into your app (if the SDK is integrated)
  3. Track engagement for marketing analytics

What Does the SDK Do?

The MovableInk Mobile SDK enables the following capabilities:

Primary Use Case: Deeplinking

Enable users to tap links in marketing emails and land directly on specific content within your mobile app. For example:

  • Email promotes a specific product → User taps → Opens your app to that product page
  • Email showcases a sale → User taps → Opens your app to the sale landing page
  • Email recommends content → User taps → Opens your app to that content

Secondary Use Case: Behavior Events

Capture user interactions in your app to inform future personalization. Events like product views, searches, and purchases help marketers create more relevant email content. This data can be used in:

  • Studio campaigns: Dynamic content based on browsing history
  • DaVinci recommendations: AI-powered product suggestions

Optional Features

  • In-App Messages: Display HTML-based messages within your app
  • Push Notification Analytics: Capture push notification interactions
  • Deferred Deeplinking: Handle deeplinks for users who don't have your app installed yet

Prerequisites

Before you begin integrating the SDK, you'll need to coordinate with your MovableInk team to ensure the following items are configured:

Required from Your Organization

  • MovableInk Subdomain: Your unique subdomain (e.g., mi.yourcompany.com) where MovableInk links are hosted
  • Bundle Identifier / Package Name: Share your iOS Bundle Identifier and Android Package Name with your MovableInk team
  • MIU Strategy: Work with your marketing team to determine which user identifier to use as the MIU (must match what your email service provider uses)

Required Technical Setup (MovableInk Will Configure)

  • iOS: Apple Team ID and Bundle Identifier shared with MovableInk
  • iOS: AASA (Apple App Site Association) file configured at https://mi.yourcompany.com/.well-known/apple-app-site-association
  • Android: Package Name and SHA-256 certificate fingerprint shared with MovableInk
  • Android: Digital Asset Links file configured at https://mi.yourcompany.com/.well-known/assetlinks.json

Optional (For Behavior Events)

  • API Key: Request an API Key from your MovableInk team if you plan to implement behavior event capture
  • Region Configuration: Specify your region (US or EU) for data compliance

Getting Help

If you don't have these items or need assistance, reach out to your Movable Ink client experience team. They can help you:

  • Obtain your MovableInk subdomain
  • Configure AASA and Digital Asset Links files
  • Get an API Key for behavior events
  • Coordinate MIU strategy with your marketing team

Next Steps

Choose your platform to get started with a quick integration:

Native SDKs

Cross-Platform SDKs

Additional Resources

  • Glossary - Definitions of common terms used in this documentation
  • Full Documentation - Detailed guides for each platform under "Native MovableInk SDKs" and "SDK Wrappers" in the navigation

Typical Integration Timeline

Here's what a typical SDK integration looks like:

  1. Week 1: Prerequisites gathering and coordination with MovableInk team
  2. Week 2: Basic deeplinking implementation and testing
  3. Week 3: Behavior events implementation (if needed)
  4. Week 4: Production deployment and QA with marketing team

Most teams can complete a basic deeplinking integration in 1-2 days of development time once prerequisites are in place.