diff --git a/foundation-extensions/mobile-core/identity/README.md b/foundation-extensions/mobile-core/identity/README.md
index 34b97083e..7ef17933a 100644
--- a/foundation-extensions/mobile-core/identity/README.md
+++ b/foundation-extensions/mobile-core/identity/README.md
@@ -2,8 +2,8 @@
 
 The Identity extension is bundled with [Mobile Core](../README.md) and enables your app with the Experience Cloud ID (ECID). This service helps with the synchronization of Adobe and other customer identifiers.
 
-{% hint style="danger" %}
-On web or other platforms, there might situations where this extension might not be required, and the implementation of this SDK extension on mobile apps is required.
+{% hint style="warning" %}
+The implementation of this SDK extension on mobile apps is required. On web or other platforms, there may be situations where this extension is not required.
 {% endhint %}
 
 To get started with Identity, complete the following steps:
@@ -454,7 +454,7 @@ Alternately, starting in SDK version 1.4.0 (Identity version 1.1.0), you can cal
 Identity.getUrlVariables(new AdobeCallback<String>() {    
     @Override    
     public void call(String stringWithAdobeVisitorInfo) {        
-        //handle the URL query parameter string here 
+        //handle the URL query parameter string here
         //For example, open the URL on the device browser        
         //        
         Intent i = new Intent(Intent.ACTION_VIEW);        
@@ -679,8 +679,8 @@ class StringCallback : Java.Lang.Object, IAdobeCallback
     if (stringContent != null)
     {
       Console.WriteLine("Appended url: " + stringContent);
-    } 
-    else 
+    }
+    else
     {
       Console.WriteLine("null content in string callback");
     }
@@ -710,8 +710,8 @@ class StringCallback : Java.Lang.Object, IAdobeCallback
     if (stringContent != null)
     {
       Console.WriteLine("Url variables: " + stringContent);
-    } 
-    else 
+    }
+    else
     {
       Console.WriteLine("null content in string callback");
     }
@@ -722,4 +722,3 @@ class StringCallback : Java.Lang.Object, IAdobeCallback
 {% endtabs %}
 
 The ID service code on the destination domain extracts the ECID from the URL instead of sending a request to Adobe for a new ID. The ID service code on the destination page uses this ECID to track the visitor. On hits from the mobile web content, verify that the `mid` parameter exists on each hit, and that this value matches the `mid`value that is being sent by the app code.
-
diff --git a/using-mobile-extensions/adobe-analytics/analytics-faq.md b/using-mobile-extensions/adobe-analytics/analytics-faq.md
index bd429e0d2..e167f90b5 100644
--- a/using-mobile-extensions/adobe-analytics/analytics-faq.md
+++ b/using-mobile-extensions/adobe-analytics/analytics-faq.md
@@ -16,6 +16,14 @@ If you see SDK identifiers unexpectedly change, try the following fixes to addre
 
 ----
 
+### What identifier types does the AEP Mobile SDK use for Analytics implementations
+
+The Analytics mobile extension uses the ECID as the main identifier type for mobile visitors, so it requires the Identity extension to operate. The Identity extension preserves the ECID for the current visitor and generates a new ECID when the application is first installed. For more details, see the [Identity extension](../../foundation-extensions/mobile-core/identity) documentation.
+
+In the case where your mobile implementation used AID (Analytics tracking identifier) or VID (custom visitor identifier) for existing users, these identifiers are preserved when migrating to AEP Mobile SDK and continue to be sent to Adobe Analytics along with the ECID. Read more about the [order of operations for Analytics IDs](https://experienceleague.adobe.com/docs/id-service/using/reference/analytics-reference/analytics-order-of-operations.html).
+
+----
+
 ### Why are Crashes inflated in the Analytics report
 
 The metric `Crashes` is computed based on the Lifecycle start and pause API calls implemented in your mobile application. How can you verify if the implementation is correct: