Frequently asked questions

Q: I am using AEP Edge and Adobe Solutions extensions, which Identity Extension should I install and register?

A: Both.

When using both Adobe Experience Platform Edge and Adobe Solutions extensions, both Identity for Edge Network and Identity for Experience Cloud ID Service extensions can be registered with the Mobile SDK at the same time.
The following instructions are for configuring an application using both Edge Network and Adobe Solutions mobile extensions. If an application will include only Adobe Experience Platform Edge extensions, follow the instructions here.

Download and import the Identity and Identity for Edge Network extensions

Android
iOS

Java

  1. 1.
    Add the Mobile Core and Edge extensions to your project using the app's Gradle file.
    1
    implementation 'com.adobe.marketing.mobile:core:1.+'
    2
    implementation 'com.adobe.marketing.mobile:identity:1.+'
    3
    implementation 'com.adobe.marketing.mobile:edge:1.+'
    4
    implementation 'com.adobe.marketing.mobile:edgeidentity:1.+'
    Copied!
  2. 2.
    Import the Mobile Core and Edge extensions in your application class.
    1
    import com.adobe.marketing.mobile.*;
    Copied!
  1. 1.
    Add the Mobile Core and Edge extensions to your project using CocoaPods. Add following pods in your Podfile:
    1
    use_frameworks!
    2
    target 'YourTargetApp' do
    3
    pod 'AEPCore'
    4
    pod 'AEPIdentity'
    5
    pod 'AEPEdge'
    6
    pod 'AEPEdgeIdentity'
    7
    end
    Copied!
  2. 2.
    Import the Mobile Core and Edge libraries:

Swift

1
// AppDelegate.swift
2
import AEPCore
3
import AEPIdentity
4
import AEPEdge
5
import AEPEdgeIdentity
Copied!

Objective-C

1
// AppDelegate.h
2
@import AEPCore;
3
@import AEPIdentity;
4
@import AEPEdge;
5
@import AEPEdgeIdentity;
Copied!

Register the Identity and Identity for Edge Network extensions with Mobile Core

Android
iOS

Java

1
public class MobileApp extends Application {
2
3
@Override
4
public void onCreate() {
5
super.onCreate();
6
MobileCore.setApplication(this);
7
MobileCore.configureWithAppID("yourLaunchEnvironmentID");
8
9
try {
10
Edge.registerExtension();
11
com.adobe.marketing.mobile.edge.identity.Identity.registerExtension(); // Register Identity for Edge Network with Mobile Core
12
com.adobe.marketing.mobile.Identity.registerExtension(); // Register Identity with Mobile Core
13
MobileCore.start(new AdobeCallback() {
14
@Override
15
public void call(final Object o) {
16
// processing after start
17
}});
18
} catch (Exception e) {
19
//Log the exception
20
}
21
}
22
}
Copied!

Swift

1
// AppDelegate.swift
2
func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {
3
MobileCore.registerExtensions([AEPEdgeIdentity.Identity.self, AEPIdentity.Identity.self, Edge.self], {
4
MobileCore.configureWith(appId: "yourLaunchEnvironmentID")
5
})
6
...
7
}
Copied!

Objective-C

1
// AppDelegate.m
2
- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {
3
[AEPMobileCore registerExtensions:@[AEPMobileEdgeIdentity.class, AEPMobileIdentity.class, AEPMobileEdge.class] completion:^{
4
...
5
}];
6
[AEPMobileCore configureWithAppId: @"yourLaunchEnvironmentID"];
7
...
8
}
Copied!

Q: Will an existing Experience Cloud ID (ECID) migrate to the Identity for Edge Network extension?

A: Yes

If the application previously installed the Identity for Experience Cloud ID Service extension and upgrades to the Identity for Edge Network extension, the existing ECID value is migrated to the Identity for Edge Network extension on first launch of the application.
Note, however, if the Mobile SDK's privacy status was set to optedOut at the time the application is upgraded, the Identity for Experience Cloud ID Service extension will not have an ECID, as it was cleared. In this case, the Identity for Edge Network extension will generate a new ECID.

Q: What is the Experience Cloud ID (ECID) used by the SDK when using both AEP Edge extensions and Adobe Solutions extensions?

A: The Identity for Edge Network extension and the Identity for Experience Cloud ID Service extension each manage their own ECID. However, the two ECIDs are synced as part of the XDM IdentityMap.

At first launch of the application after upgrading to the Identity for Edge Network extension, the existing ECID from the Identity for Experience Cloud ID Service extension is migrated to the Identity for Edge Network extension. In this case both extensions will have the same ECID value.
The resetIdentities API regenerates a new ECID used by the Identity for Edge Network extension. This API call does not change the ECID used by the Identity for Experience Cloud ID Service extension. After calling this API, the ECID used by each identity extension will be different.
Changing the privacy status to optedOut will clear the ECID value used by the Identity for Experience Cloud ID Service extension. Changing the privacy status back to optedIn will generate a new ECID used by the Identity for Experience Cloud ID Service extension. Privacy status changes do not change the ECID used by the Identity for Edge Network extension. Changing the privacy status will cause the ECID used by each identity extension to be different.
When each identity extension has a different ECID, the Identity for Edge Network extension will include the Identity for Experience Cloud ID Service ECID in its IdentityMap, and so the Adobe Experience Platform Identity Service will link the the two ECIDs in the customer's Identity Graph.
The following example shows an IdentityMap containing the ECIDs from both Identity for Edge Network extension and Identity for Experience Cloud ID Service extension. The ECID from the Identity for Edge Network extension is always listed first in the list of ECIDs.
1
"identityMap" : {
2
"ECID" : [
3
{
4
"id" : "73586628797489658169123381027155647197",
5
"authenticatedState" : "ambiguous",
6
"primary" : false
7
},
8
{
9
"id" : "81117527655405132265917409409236407340",
10
"authenticatedState" : "ambiguous",
11
"primary" : false
12
}
13
]
14
}
Copied!

Q: I set privacy status to opted out, why do I see an ECID value when calling Identity.getExperienceCloudId()?

A: The Identity for Edge Network extension does not change its ECID based on privacy status changes.

The Identity for Edge Network extension and the Identity for Experience Cloud ID Service extension each manage their own ECID value and are generated independently of each other.
The Identity for Edge Network extension does not clear its stored identities or regenerate the ECID due to privacy status changes. Instead, use the resetIdentities API. Note this API does not clear the ECID but instead generates a new ECID.
Each identity extension has its own API to retrieve their respective ECIDs as well. Use Identity.getExperienceCloudId to get the Identity for Edge Network extension's ECID, and Identity.getExperienceCloudId to get the Identity for Experience Cloud ID Service extension's ECID.

Q: How can I get all the identifiers used by the SDK when using both AEP Edge extensions and Adobe Solutions extensions?

A: Use both getSdkIdentities and getIdentities

To get the identifiers used by the Adobe Solutions extensions, call getSdkIdentities.
To get the identifiers used by the AEP Edge extensions, call getIdentities.

Q: How can I clear all the identifiers from the SDK when using both AEP Edge extensions and Adobe Solutions extensions?

A: Set privacy status to optedOut and call resetIdentities

To clear the identifiers used by the Adobe Solutions extensions, call setPrivacyStatus and set the privacy status to optedOut.
To clear the identifiers used by the AEP Edge extensions, call resetIdentities

Q: What steps are needed to generate a new Experience Cloud ID (ECID) for a user when using both AEP Edge extensions and Adobe Solutions extensions?

A: Both identity extensions' ECID must be regenerated in sequence to avoid linking the old and new ECIDs in Adobe Experience Platform.

When using Real-time Customer Profile and Identity Service, the ECIDs from both identity extensions are linked together in the customer's Identity Graph. Care must be taken when regenerating new ECIDs such that the old and new ECIDs are not linked within the same Identity Graph.
Perform the following API calls to regenerate the ECIDs in sequence:
  1. 1.
    Set privacy status to optedOut to clear the ECID from the AEP Identity direct service extension.
  2. 2.
    Call resetIdentities to regenerate a new ECID in the Identity for Edge Network extension.
  3. 3.
    Call getExperienceCloudId on the Identity for Edge Network extension. This ensures the new ECID is generated before continuing.
  4. 4.
    Set privacy status to optedIn to generate a new ECID in the AEP Identity direct service extension.
After completing the above steps, each identity extension will have its own, different, ECID. The new ECIDs will get linked under a new Identity Graph for the customer.
Android
iOS

Java

1
MobileCore.setPrivacyStatus(MobilePrivacyStatus.OPT_OUT);
2
MobileCore.resetIdentities();
3
com.adobe.marketing.mobile.edge.identity.Identity.getExperienceCloudId(new AdobeCallback<String>() {
4
@Override
5
public void call(String s) {
6
// ignore
7
}
8
});
9
MobileCore.setPrivacyStatus(MobilePrivacyStatus.OPT_IN);
Copied!

Swift

1
MobileCore.setPrivacyStatus(.optedOut)
2
MobileCore.resetIdentities()
3
AEPEdgeIdentity.Identity.getExperienceCloudId { _, _ in }
4
MobileCore.setPrivacyStatus(.optedIn)
Copied!

Objective-C

1
[AEPMobileCore setPrivacyStatus:AEPPrivacyStatusOptedOut];
2
[AEPMobileCore resetIdentities];
3
[AEPMobileEdgeIdentity getExperienceCloudId:^(NSString *ecid, NSError *error) {
4
// ignore
5
}];
6
[AEPMobileCore setPrivacyStatus:AEPPrivacyStatusOptedIn];
Copied!
Last modified 1mo ago