How to setup Adobe Target(Edge SDK) in react native mobile app

​@N_G use the AEP Mobile SDK with the Edge extension. React Native wrappers exist (packages like @adobe/react-native-aepcore, aepedge, aepedgeidentity, aepedgeconsent, aeptarget).

Native iOS and Android initialization is required, the JS side registers extensions and configures the mobile property.

In native screens, call Target.retrieveLocationContent() at the lifecycle moment the test surface renders, apply the response to props or state, send a clickedLocation event on interaction.

For webviews, install Web SDK (alloy) in the HTML and pass the ECID from native into the webview so the same profile is used. That identity bridge is the only piece without a default.

The app dev work will be required beyond setup: identify every mbox surface, fetch and apply the response, render a default fallback when nothing returns, send display and click events back, gate on consent.

Hi ​@N_G  

Agree with ​@v-lazar , he outlined all the implementation steps below. Please also find the reference links to get started 

• React Native AEP SDK (GitHub)  Contains packages and sample implementations for mobile SDK https://github.com/adobe/aepsdk-react-native    

• Mobile SDK documentation This covers setup, extensions, and architecture basics
  https://experienceleague.adobe.com/en/docs/mobile 

• Edge SDK (React Native) Used for sending events and decisioning requests 
  https://www.npmjs.com/package/@adobe/react-native-aepedge

• Target React Native extension Retrieve offers using retrieveLocationContent()
  https://www.npmjs.com/package/@adobe/react-native-aeptarget 

• WebView + Target integration guide  This explains identity sharing between app and WebView
  https://experienceleague.adobe.com/en/docs/target-dev/developer/mobile-apps/native-app

So your app developer controls how the UI is rendered. And all UI logic, variants, fallback handling, and tracking must be implemented in the app. 

Hope this help

Thank you.