Create Interaction Points for your Mobile Touchpoints

After creating your mobile Touchpoints, you can set up Interaction Points on those Touchpoints to capture customer activity within your app.

For more information, see Creating and Managing Interaction Points.

Interaction Point Requirements

When creating automatic Interaction Points, be aware that you must also create an associated Activity Capture, Attribute Capture or Optimization Point for each one, to enable MXO to trigger these Interactions.

This is to reduce the number of unnecessary Interaction requests sent to MXO, automatically, by the SDK.

Correctly configured Interaction Points are added to the Interaction Map.

Step 1: Create any required Interaction Points

Set up Interaction Points to see all requests sent to MXO by the SDK when using Monitor.

Think of Interactions as the key steps (or elements) of the customer experience, representing the ongoing conversation between you and your customer on any of your Touchpoints.

Interaction Points are the are the means through which you can capture information about those key steps. In a mobile app, an Interaction Point represents an individual screen or context; on a web site, an individual page, and in the call center a customer's reason for calling.

You can create Interaction Points in two ways:

  • In the main MXO UI. Typically, these Interaction Points are triggered programmatically by the SDK.
  • Automatically, when logged in to the SDK, in Admin mode. These Interaction Points are triggered automatically by the SDK.

To create an Interaction Point in the main MXO UI

  1. In MXO, choose Collect.
  2. Select Interaction Points.
  3. Select the Touchpoint to which you want to add an Interaction Point from the drop-down menu.
  4. Click Add Interaction Point.
  5. Enter the following details for your Interaction Point:Mobile - Interaction example
  6. Click Create.

To create a automatic Interaction Point using Admin mode

  1. On your device, open your app. You'll see the MXO Poker Chip on-screen.
  2. Tap the Poker Chip to view the Login screen.Mobile - Step 7a Poker Chip
  3. Log in using your MXO username and password.Mobile - Step 7b Login Screen
  4. Navigate to the page in your app when you want to create an Interaction Point.
  5. Tap the Poker chip to enter Edit mode on the first page of the app.The Poker chip turns blue when in Edit mode.
    Mobile - Step 7c
    MXO automatically creates an Interaction Point for you. You can view the new Interaction Point for your mobile Touchpoint, in the main MXO UI.

Step 2: Create App Install and Reinstall Interaction Points

The Mobile SDKs are configured to trigger app install and app reinstall interactions automatically, when integrated into your app, allowing you to track when a mobile app is installed and/or reinstalled by your customers. These interactions are triggered:

  • the first time a mobile app, including our SDK, is installed and opened, and
  • each time a mobile app is reinstalled, as long as the SDK was integrated prior to uninstall.

To track these interactions, set up the following Interaction Points:

For iOS

NamePath
App Install/MXO-app-install
App Reinstall/MXO-app-reinstall

For Android

NamePath
App Install/MXO-app-install
App Reinstalln/a
Note: If you do not wish to track app install or reinstall events, do not create the associated Interaction Points. The events will simply be ignored by MXO when triggered by the SDKs.

Step 3: Create Last Click Attribution Interactions

The SDKs can track last click attribution in your app by automatically triggering the destination to which a user is going when they click on a link.

Use the following details:

FieldDescription
NameLast Click Attribution
Path/MXO-click

Any links opened from the app send a formatted URL to a /MXO-click Interaction Point in MXO. The URL contains the following parameter

Whenever a user taps on link in the app, the SDK triggers the /MXO-click interaction and sends a formatted URL to the Interaction Point in MXO. The URL contains the following parameters:

  • the full URL, sent as a MXO-url property
  • the host, sent as a MXO-host property
  • the path, sent as a MXO-path property
  • any URL parameters, sent with the parameter name as a key

Example

Create a MXO-click Interaction Point that automatically assigns activity based on the URL opened by the customer.

  1. Create a generic Last Click Interaction Point that uses a RegEx wildcard in the URL. For example, /MXO-click?MXO-host=*.
    Mobile - LCA Interaction Point
  2. Create any relevant Attribute Capture Points for that Interaction Point. For example:
    1. UTMs, such as utm_source, utm_medium, and utm_campaign.
      Mobile - LCA Capture Point 1
    2. MXO-host property captured into a new attribute, sponsorURL.Mobile - LCA Capture Point 2
  3. Create an On Load Activity Capture Point that sets the Proposition automatically at runtime, using the value captured for the sponsorURL attribute.
    Mobile - LCA Tracking Point 1
  4. Add each sponsor as a separate Proposition with a Proposition code that matches their respective value for the MXO-host parameter.

Using a /MXO-click Interaction Point offers a more robust solution to tracking different links that are opened in the same container, avoiding the need to trigger a more generic Interaction Point every time. For example, when you use the same webview to open a variety of different links.

Note: If you do not wish to track last click attribution events, do not create the associated Interaction Points. The events will simply be ignored by MXO when triggered by the SDKs.

Step 4: Publish Your Changes

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

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

Publishing is necessary only when you want to make your configurations available in User mode. You can view and test any changes to the In the works snapshot or on the Launchpad in Preview mode, prior to publishing.

For more information, see an Introduction to Publishing.

Optional - Step 5: Create a Wildcard Interaction Point

Set up a Wildcard Interaction Point to catch all automatic and programmatic requests sent to MXO by the SDK to help you to monitor and test your configuration during initial integration.

Use the following details:

FieldDescription
NameWildcard Interaction
Path/*

Mobile - Interaction catch all

Note: Unless you have a specific use case, remove this Interaction Point when testing of your initial integration is complete. This will reduce the number of automatic interaction requests made by the SDK to include only those that are actually of interest to you.

Optional - Step 6: Create a Base Interaction Point

Set up a Base Interaction Point to send Attribute Capture Points at the application level which cannot be associated with an interaction. For example, where you have a set of properties you want to capture in the customer profile without capturing any activity.

Use the following details:

FieldDescription
NameBase Interaction Point
Path/

Mobile - Interaction base

After creating your Base Interaction Point, create the associated Attribute Capture Point.

Example

Mobile - Interaction base cp

Note: The property name you use to send the value from the SDK, must match the API parameter name for the attribute in MXO.

For information on how to send properties to a Base Interaction Point see our documentation on Github: