What is the Interaction Map?

The Interaction map contains a list of all correctly configured automatic Interaction Points. For a automatic Interaction Point to be correctly configured, it must be associated with an Activity Capture, Attribute Capture or Optimization Point.

To reduce the number of unnecessary interaction requests sent to MXO, automatically, by the SDK MXO processes only those requests received from Interaction Points contained in the Interaction map.

Configuring and Testing in Preview mode

If you have already created and published a Space in MXO, you can create mobile Touchpoints, Interaction Points and Capture Points automatically in the SDK, without publishing, to test your configuration. This lets you create and update Interaction Points, that will be added to the Interaction map later, using Edit and Preview modes in the SDK.

If you have not already created a Space, you can do that using the main MXO UI. For more information, see Create a Space.

Step 1: Create a Mobile Touchpoint Automatically

For more information about Mobile Touchpoints, see Create Mobile Touchpoints.

1. Configure the SDK to use the parameters for your Space. Include the details for your mobile Touchpoint as part of that configuration.
2. Run your app with the SDK initialized in Admin mode.
3. Tap the Poker chip to view the Login screen.
4. Log in using your MXO username and password. MXO automatically creates your mobile Touchpoint after you log in.

Step 2: Create Interaction Points Automatically

For more information about configuring Interaction Points, see Create Interaction Points for your Mobile Touchpoints.

1. Ensure you are still logged in to MXO in Admin mode.
2. Navigate to the page in your app when you want to create an Interaction Point.
3. Tap the Poker chip to enter Edit mode on that page.
   Tip: Remember that the Poker chip turns blue when in Edit mode.
   MXO automatically creates Interaction Points for all View Controllers where Edit mode has been activated at least once. Interaction Points created automatically are either assigned the name of a View Controller or the given programmatic name. You can view the new Interaction Point for your mobile Touchpoint, in the main MXO UI.

Step 3: Create at least one Capture or Optimization Point

You can create your Activity Capture and Attribute Capture Points using either the main MXO UI or Admin mode in the SDK. You can only create Optimization Points using the main MXO UI.

For more information, see:

• Create Activity Capture Points
• Create Attribute Capture Points
• Create Mobile Optimizations for iOS
• Create Mobile Optimizations for Android

Step 4: Check your configuration in Preview mode

1. Ensure you are still logged in to MXO in Admin mode.
2. Long press the Poker chip to enter Preview mode.The Poker chip turns green when in Preview mode.

When you launch Preview mode, MXO immediately adds your new Interaction Points to the Interaction map.

If you have access to the SDK logs, you can review the Interaction map array based on your configuration, as soon as you enter Preview mode.

Example Interaction map

{ "statusCode": "200", "interactions": [ "/loginView/?", "/featureStoreTableView/?", "/servicesTableView/?", "/branchFinderView/?" ] } 

Making Changes to the Interaction Map in Preview Mode

When entering or refreshing Preview mode, the Interaction map is always sent with a status code of 200.

In Preview mode, updates to the Interaction map are made immediately, as you make changes to the In the works snapshot. Changes include:

• Adding a new Interaction Point with associated Activity Capture, Attribute Capture, or Optimization Point.
• Adding a new Activity Capture, Attribute Capture, or Optimization Point to an existing Interaction Point.
• Removing all associated Activity Capture, Attribute Capture, and Optimization Points from an existing Interaction Point.
• Removing an Interaction Point.

Configuring and Testing in User mode

If you have already created and published a Space and mobile Touchpoint in MXO, you can configure any Interaction Points you want to include in the Interaction map.

If you have not already created and published a Space and mobile Touchpoint in MXO, configure those first. for more information, see Create a Space and Create Mobile Touchpoints.

Step 1: Create and Publish Interaction Points

MXO can send automatic interactions for any Interaction Points, with explicit Interaction paths, you configure for your mobile Touchpoint.

For more information about configuring Interaction Points, see Create Interaction Points for your Mobile Touchpoints.

You must also create and publish an associated Activity Capture, Attribute Capture or Optimization Point for each Interaction Point to ensure MXO includes it in the Interaction map and is able to trigger the interaction automatically.

For more information, see:

• Create Activity Capture Points
• Create Attribute Capture Points
• Create Mobile Optimizations for iOS
• Create Mobile Optimizations for Android

Example Interaction map

In this case, MXO sends the Interaction map as an array of Interaction paths for all published Interaction Points.

{ "statusCode": "200", "interactions": ["/MXO-app-install/?", "/MXO-app-reinstall/?", "/MainScreenViewController/?"] } 

After you create and publish your configuration, MXO triggers Interactions based on your published configuration. The SDK automatically refreshes its configuration file on every app open.

Optional Step 2: Create and Publish a Wildcard Interaction Point

When you configure a wildcard (/*) Interaction Point for a mobile Touchpoint, the SDK sends all automatically identified views, including the MXO-app-install, MXO-app-reinstall and MXO-click interactions, to MXO.

For more information, see Using Wildcards in Interaction Points

You must also create and publish an associated Activity Capture, Attribute Capture or Optimization Point for each Interaction Point to ensure MXO includes it in the Interaction map and is able to trigger the interaction automatically.

Example Interaction map

{ "statusCode": "200", "interactions": "/.*/?" } 

Making Changes to the Interaction Map in User Mode

In User mode, if no changes are made to the Interaction map following publishing, it is sent with a 304 status code instead of 200 status code. Changes include:

• Adding a new Interaction Point with associated Activity Capture, Attribute Capture, or Optimization Point.
• Adding a new Activity Capture, Attribute Capture, or Optimization Point to an existing Interaction Point.
• Removing all associated Activity Capture, Attribute Capture, and Optimization Points from an existing Interaction Point.
• Removing an Interaction Point.