Removing the MXO Orchestration Plugin

The MXO Orchestration Plugin dependency is used to facilitate Identity Transfer and Last Click Attribution in Android Apps.

If the MXO Orchestration Plugin is enabled in your app, the SDK automatically:

  • adds tid as a URL or URI query parameter to web links opened in a WebView, CustomTab or external browser,
  • sends an Interaction request to /mxo-click when a URL or URI is opened in a WebView, CustomTab, or external browser, to facilitate last click attribution, and
  • enables the ability to pick up parameters from deep links that open in your App.

Why remove the MXO Orchestration Plugin?

You may decide to remove the MXO Orchestration Plugin for configurations reasons or if build times are adversely impacted by its inclusion in your App.

For more information, see Disabling automatic Identity transfer.

How do I remove the MXO Orchestration Plugin?

The MXO Orchestration Plugin must be removed by an App Developer.

For more information, see Removing Identity Transfer support.

How do I add the Identity Transfer functionality programmatically?

If you have disabled automatic identity transfer, you can still create a URL with a tid parameter to use in the app programmatically.

Identity Transfer enables MXO to link a customer across two Touchpoints and merge any information held for that customer into a single profile, for example, when a customer is using a mobile app and that app opens a web view. The MXO Orchestration plugin intercepts these location changes and updates the URL or URI location with that user's TID, enabling MXO to link a customer across the two Touchpoints and merge any information held for that customer into a single profile. You can preserve this functionality by programmatically creating a URL or URI with a tid parameter using the generateIdentityTransferUrl method.
Note: This assumes you have successfully configured the SDK, and that MXO has received at least one Interaction request and returned a TID.
For more information, see how to Create a URL with the tid parameter to facilitate identity transfer.

The MXO SDK also provides the ability to limit Identity transfer, programmatically, by including or excluding that functionality for a specific subset of links in your App.

Outbound Link tracking enables MXO to record last click attribution data, automatically, letting you capture where your users are heading after they leave your app. The MXO Orchestration Plugin intercepts these location changes and sends a /mxo-click interaction to MXO on your Apps behalf. You can preserve this functionality using the sendInteractionForOutboundLink method.

For more information, see how to Send Interaction for outbound link.
Note: This assumes you have successfully configured the SDK, and that MXO has received at least one interaction request and returned a TID.
Use this API to inform the SDK that an outbound action is occurring in any location where your app uses an Android Intent to open another application.

For more information, see how to Disable automatic outbound link tracking.

Deep Link enables MXO to track when your app is opened using a "Deep Link", typically represented by various query parameters. The MXO Orchestration plugin tracks these links by intercepting the Android Activity Lifecycle event for opening your Apps activity and sending the link's query parameters on your Apps behalf. You can preserve this functionality using the processDeepLink method.

For more information, see how to Send deep link properties programmatically.

On your Apps Activity check for any Android Intent data that has URI opening that Activity and call the Deep Link Properties API to inform the SDK that a deep link action has opened the app.
Note: This assumes you have successfully configured the SDK, and that MXO has received at least one interaction request and returned a TID.