Create Mobile Touchpoints

Before you can start integrating the mobile SDKs with MXO and your app, you need to create your mobile Touchpoints.

You can think of these Touchpoints as being your apps. The SDKs send insights and behavioral data about your app users to these Touchpoints.

We recommend that you create a Touchpoint for each platform and each app that you want to connect to MXO.

For more information, see Creating and Managing Touchpoints.

Prior to creating your Touchpoints you must ensure you have created a Space, in MXO. For more information, see Creating and Managing Spaces.

Step 1: Create your Mobile Touchpoints

In MXO, create mobile Touchpoints for iOS and Android (as required).

Example details for iOS Touchpoint

FieldDescription
ChannelMobile.
Touchpoint

"My iOS App" or "App Name - iOS".

We recommend a name that resembles your app name and platform to make it easier to identify throughout MXO.

Base URI

"ios://myAppName".

The Base URI you provide must be unique. It is this URI that is used to send data from the SDK, after installation. We recommend using "ios://" as the prefix for your Base URI to make it easier to identify throughout MXO and to distinguish it from other platform apps.

Mobile - iOS Touchpoint

Example details for Android Touchpoint

FieldDescription
ChannelMobile.
Touchpoint

"My Android App" or "App Name - Android".

We recommend a name that resembles your app name and platform to make it easier to identify throughout MXO.

Base URI

"android://myAppName".

The Base URI you provide must be unique. It is this URI that is used to send data from the SDK, after installation. We recommend using "android://" as the prefix for your Base URI to make it easier to identify throughout MXO and to distinguish it from other platform apps.

Note: You can also create mobile Touchpoints, automatically, by running the SDK in Admin mode. After logging in to the SDK in Admin mode, your Touchpoint is automatically added to your Space, based on the Touchpoint URI you define in the initialization parameters used to configure the SDK.

Step 2: Publish Your Changes

In MXO, publish your changes to push them to your live environment.

You do not need to publish your changes until you want your configuration to be accessible in User mode. Any changes to the In the works snapshot, or on the Launchpad are available to view and test in Preview mode, without publishing.

For more information, see introduction to Publishing.

Note: You must have Publish role in MXO to be able to publish changes to your live environment. For more information, see Team Roles.