Expand my Community achievements bar.

Help shape the future of AI assistance by participating in this quick card sorting activity. Your input will help create a more effective system that better serves your needs and those of your colleagues.
SOLVED

AEP Mobile SDK question

Avatar

Level 3

Hi,

 

- Any there any best practices for implementing AEP Mobile SDK on Hybrid App? Specifically, what methods can be used to share Visitor Information(ECID) from the native screen to Web App?


- as per Adobe documentation, recommended approach for sending events is through the "sendEvent" API from the application end to capture custom Variables. Howerver, are there any downsides to using EdgeBridge Extension while continuing to rely on MobileCore.trackState and MobileCore.trackAction to pass custom data via ContextData.

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Level 5

Hi @MA1985v1 

 

SDK has API to prepare your URL for opening Web View so that ECID can be passed for visitor persistence. See below for reference,

 

https://developer.adobe.com/client-sdks/home/base/mobile-core/identity/tutorials/id-sharing/

 

But please note that the API has changed if you use the new Identity for Edge.

 

For using sendEvent, you will have to put the XDM structure in the client side code. For Edge Bridge, it's sort of a backward compatibility mechanism for app developer who want to upgrade the SDK but do not have resource to change the trackState/Action calls to the new sendEvent API.

 

 

View solution in original post

2 Replies

Avatar

Correct answer by
Level 5

Hi @MA1985v1 

 

SDK has API to prepare your URL for opening Web View so that ECID can be passed for visitor persistence. See below for reference,

 

https://developer.adobe.com/client-sdks/home/base/mobile-core/identity/tutorials/id-sharing/

 

But please note that the API has changed if you use the new Identity for Edge.

 

For using sendEvent, you will have to put the XDM structure in the client side code. For Edge Bridge, it's sort of a backward compatibility mechanism for app developer who want to upgrade the SDK but do not have resource to change the trackState/Action calls to the new sendEvent API.