Documentation Experience Platform Migrate your mobile app from the Adobe Target to the Adobe Journey Optimizer - Decisioning extension

Replace the Target SDK with the Optimize SDK

Last update: April 8, 2025

Topics:
Implement Client-side,Implement Mobile,APIs/SDKs
Mobile SDK

CREATED FOR:

Intermediate
Experienced
Developer

Learn how to replace the Adobe Target SDKs with the Optimize SDKs in your mobile implementation. A basic replacement consists of the following steps:

Update dependencies in your Podfile or build.gradle file
Update imports
Update application code

INFO

Within the Adobe Experience Platform Mobile SDK ecosystem, extensions are implemented by SDKs imported into your applications which may have different names:

Target SDK implements the Adobe Target extension
Optimize SDK implements the Adobe Journey Optimizer - Decisioning extension

Update dependencies

Android exanple

Optimize SDK

build.gradle dependencies after migrating

implementation platform('com.adobe.marketing.mobile:sdk-bom:3.+')
implementation 'com.adobe.marketing.mobile:core'
implementation 'com.adobe.marketing.mobile:edgeidentity'
implementation 'com.adobe.marketing.mobile:edge'
implementation 'com.adobe.marketing.mobile:optimize'

Target SDK

build.gradle dependencies before migrating

implementation platform('com.adobe.marketing.mobile:sdk-bom:3.+')
implementation 'com.adobe.marketing.mobile:analytics'
implementation 'com.adobe.marketing.mobile:target'
implementation 'com.adobe.marketing.mobile:core'
implementation 'com.adobe.marketing.mobile:identity'
implementation 'com.adobe.marketing.mobile:lifecycle'
implementation 'com.adobe.marketing.mobile:signal'
implementation 'com.adobe.marketing.mobile:userprofile'

iOS example

Optimize SDK

Podfile dependencies after migrating

use_frameworks!
target 'YourAppTarget' do
    pod 'AEPCore', '~> 5.0'
    pod 'AEPEdge', '~> 5.0'
    pod 'AEPEdgeIdentity', '~> 5.0'
    pod 'AEPOptimize', '~> 5.0'
end

Target SDK

Podfile dependencies before migrating

use_frameworks!
pod 'AEPAnalytics', '~> 5.0'
pod 'AEPTarget', '~> 5.0'
pod 'AEPCore', '~> 5.0'
pod 'AEPIdentity', '~> 5.0'
pod 'AEPSignal', '~>5.0'
pod 'AEPLifecycle', '~>5.0'
pod 'AEPUserProfile', '~> 5.0'

Update imports and code

Android example

Optimize SDK

Java initialization code after migrating

import com.adobe.marketing.mobile.MobileCore;
import com.adobe.marketing.mobile.Edge;
import com.adobe.marketing.mobile.edge.identity.Identity;
import com.adobe.marketing.mobile.optimize.Optimize;
import com.adobe.marketing.mobile.AdobeCallback;

public class MainApp extends Application {

  private final String ENVIRONMENT_FILE_ID = "YOUR_APP_ENVIRONMENT_ID";

    @Override
    public void onCreate() {
        super.onCreate();

        MobileCore.setApplication(this);
        MobileCore.configureWithAppID(ENVIRONMENT_FILE_ID);

        MobileCore.registerExtensions(
            Arrays.asList(Edge.EXTENSION, Identity.EXTENSION, Optimize.EXTENSION),
            o -> Log.d("MainApp", "Adobe Journey Optimizer - Decisioning Mobile SDK was initialized.")
        );
    }
}

Target SDK

Java initialization code before migrating

import com.adobe.marketing.mobile.AdobeCallback;
import com.adobe.marketing.mobile.Analytics;
import com.adobe.marketing.mobile.Extension;
import com.adobe.marketing.mobile.Identity;
import com.adobe.marketing.mobile.Lifecycle;
import com.adobe.marketing.mobile.LoggingMode;
import com.adobe.marketing.mobile.MobileCore;
import com.adobe.marketing.mobile.Signal;
import com.adobe.marketing.mobile.Target;
import com.adobe.marketing.mobile.UserProfile;
import java.util.Arrays;
import java.util.List;
...
import android.app.Application;
...
public class MainApp extends Application {
...
    @Override
    public void onCreate() {
        super.onCreate();
        MobileCore.setApplication(this);
        MobileCore.setLogLevel(LoggingMode.DEBUG);
        ...
        List<Class<? extends Extension>> extensions = Arrays.asList(
            Analytics.EXTENSION,
            Target.EXTENSION,
            Identity.EXTENSION,
            Lifecycle.EXTENSION,
            Signal.EXTENSION,
            UserProfile.EXTENSION
        );


        MobileCore.registerExtensions(extensions, new AdobeCallback () {
            @Override
            public void call(Object o) {
                MobileCore.configureWithAppID(<Environment File ID>);
            }
        });
    }
}

iOS

Optimize SDK

Swift initialization code after migrating

import AEPCore
import AEPEdge
import AEPEdgeIdentity
import AEPOptimize

@UIApplicationMain
final class AppDelegate: UIResponder, UIApplicationDelegate {
  var window: UIWindow?

  func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]? = nil) -> Bool {

      // register the extensions
      MobileCore.registerExtensions([Edge.self, AEPEdgeIdentity.Identity.self, Optimize.self]) {
        MobileCore.configureWith(appId: <YOUR_ENVIRONMENT_FILE_ID>) // Replace <YOUR_ENVIRONMENT_FILE_ID> with a String containing your own ID.
      }

      return true
  }
}

Target SDK

Swift initialization code before migrating

import AEPCore
import AEPAnalytics
import AEPTarget
import AEPIdentity
import AEPLifecycle
import AEPSignal
import AEPServices
import AEPUserProfile
...
@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate {
    func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {
        MobileCore.setLogLevel(.debug)
        let appState = application.applicationState
        ...
        let extensions = [
            Analytics.self,
            Target.self,
            Identity.self,
            Lifecycle.self,
            Signal.self,
            UserProfile.self
        ]
        MobileCore.registerExtensions(extensions, {
        MobileCore.configureWith(<Environment File ID>)
        if appState != .background {
            MobileCore.lifecycleStart(additionalContextData: ["contextDataKey": "contextDataVal"])
            }
        })
        ...
        return true
    }
}

API comparison

Many Target extension APIs have an equivalent approach using the Decisioning extension outlined in the table below. For more details about the functions, refer to the API reference.

Target extension

Decisioning extension

Notes

prefetchContent

updatePropositions

retrieveLocationContent

getPropositions

When using getPropositions API, no remote call is made to fetch non-cached scopes in the SDK.

displayedLocations

Offer -> displayed()

In addition, generateDisplayInteractionXdm Offer method can be used to generate the XDM for item display. Subsequently, Edge network SDK’s sendEvent API can be used to attach additional XDM, free-form data and send an Experience Event to the remote.

clickedLocation

Offer -> tapped()

In addition, generateTapInteractionXdm Offer method can be used to generate the XDM for item tap. Subsequently, Edge network SDK’s sendEvent API can be used to attach additional XDM, free-form data and send an Experience Event to the remote.

clearPrefetchCache

clearCachedPropositions

resetExperience

n/a

Use removeIdentity API from Identity for Edge Network extension for the SDK to stop sending the visitor identifier to the Edge network. For more details, see the removeIdentity API documentation.

Note: Mobile Core’s resetIdentities API clears all stored identities in the SDK, including the Experience Cloud ID (ECID) and it should be sparingly used!

getSessionId

n/a

state:store response handle carries session-related information. Edge network extension helps manage it by attaching non-expired state store items to subsequent requests.

setSessionId

n/a

state:store response handle carries session-related information. Edge network extension helps manage it by attaching non-expired state store items to subsequent requests.

getThirdPartyId

n/a

Use updateIdentities API from Identity for Edge Network extension to supply the third party ID value. Then, configure the third party ID namespace in the datastream. For more details, see the Target Third Party Id mobile documentation.

setThirdPartyId

n/a

Use updateIdentities API from Identity for Edge Network extension to supply the third party ID value. Then, configure the third party ID namespace in the datastream. For more details, see the Target Third Party Id mobile documentation.

getTntId

n/a

locationHint:result response handle carries the Target location hint information. It is assumed Target edge will be co-located with Experience Edge.

Edge network extension uses the EdgeNetwork location hint to determine the Edge network cluster to send requests to. To share Edge network location hint across SDKs (hybrid apps), use getLocationHint and setLocationHint APIs from Edge Network extension. For more details, see the getLocationHint API documentation.

setTntId

n/a

locationHint:result response handle carries the Target location hint information. It is assumed Target edge will be co-located with Experience Edge.

Edge network extension uses the EdgeNetwork location hint to determine the Edge network cluster to send requests to. To share Edge network location hint across SDKs (hybrid apps), use getLocationHint and setLocationHint APIs from Edge Network extension. For more details, see the getLocationHint API documentation.

Next, learn how to request and render activities to the page.

NOTE

We are committed to helping you be successful with your mobile Target migration from the Target extension to the Decisioning extension. If you run into obstacles with your migration or feel like there is critical information missing in this guide, please let us know by posting in this Community discussion.

recommendation-more-help