Movable Ink - Email

Overview

This guide will walk you through how to setup your email campaigns with Movable Ink using Branch's Universal Email product to automatically convert your email links into multi-platform deep links.

Universal Email allows you to automatically convert your email links into multi-platform deep links that take users directly to content in the app on mobile devices, while still maintaining the same web experience for desktop and mobile users without the app.

When a link is clicked by a user without the app, it will route that user to the original web URL (including on desktop). When a link is clicked by a user with your app, it will direct that user into the relevant in-app content regardless of platform or email client.

Movable Ink link format

Please make sure that you are using web URLs on the Movable Ink platform rather than URI schema.

Setup Email Link

Configure your ESP

You can use Movable Ink personalization links with any ESP, so before we start to configure Movable Ink, please find your ESP in this list - Email Partners List - and follow the integration guide to make sure that you have configured and enabled the integration.

Setup link behavior

Once you have completed the ESP configuration, you can start adding Movable Ink links to the email body.

Please check a checkbox to tell Movable Ink that you are using Branch. Then MovableInk automatically appends all required parameters.

Once enabled, you will see the option, Copy Branch URL, as a split action button to copy creative tags for email and mobile channels.

QA Testing For Movable Ink

To test the tracking you’ll take the finalized Branch URL that is placed within your email template and click the URL. After the URL is clicked, you’ll check to make sure the clicks are recorded within the Movable Ink campaign dashboard:

image

If clicks are recording then the setup is successful.

Updated about 11 hours ago

Movable Ink - Email


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.