Step 6 - Create your Mobile Touchpoint and Configure the SDK

In MXO, create a mobile Touchpoint for Android and then configure the SDK on your mobile device.

FieldDescription
ChannelMobile
Touchpoint"app". We recommend a name that resembles your app name and platform to make it easier to identify throughout MXO.
Base URI"android://app" 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.

For more information, see What are Touchpoints?

To create your Touchpoint

  1. In MXO, choose Collect.
  2. Select Touchpoints.
  3. Click Create.
  4. Create your new Touchpoint, using the details provided in the table above.
  5. Click Save.

Once created, your Touchpoint will appear in the main MXO UI, as follows:

Mobile - Android Step 5 Touchpoint

To configure the SDK

You need to provide the specific parameters for your MXO environment when integrating your Android solution with the SDK. Use these parameters to replace the defaults in the mobile app under gradle.properties and configure the SDK in Admin mode for internal distribution.

These integration parameters include:

  • Site Key (for your specific Space).
  • Touchpoint URI.
    • The native MXO SDK will automatically prefix the URI scheme (that is, android:// and ios://) when it is omitted. For example, if you use optimization-example.
    • If you want to configure a single Touchpoint, you can explicitly prefix your URI scheme. For example ionic://optimization-example.
  • API Key & Shared Secret (required for OAuth 1.0 authentication).
  • Username/User ID (required for OAuth 1.0 authentication).
  • Host name.
  • Admin mode.
    • Admin mode (adminMode: true) provides you with an interface that lets you add Interaction Points, Activity Capture Points, and Attribute Capture Points to native UI elements within the app. Hybrid apps, however, do not support this feature because they typically use non-native UI elements. For Hybrid apps,only Preview mode is supported, allowing you to view your unpublished (In the Works) configuration before you publish to your live environment.
    • The Admin mode build should only be distributed internally to business users involved in MXO setup. This is your internal dev build.
  • User mode.
    • User mode (adminMode: false) builds should be used for production builds, when you are satisfied that all insights are being tracked in Admin mode and all internal QA requirements have been met.

For more information, see Find the Information required when Integrating MXO with Other Solutions.