Mobile SDK - create ECID locally (without request to demdex) within Identity Extension

[ericb17371700]

Hi all, 

Within the visitor ID Service I have a way to receive the ECID locally in the client with disabling third party calls /cookies. (https://experienceleague.adobe.com/docs/id-service/using/id-service-api/configurations/disablethirdp...) 

We use this mostly for privacy reasons. 

In the app, when using the Identity extension, there is also a request happening. 

Is there a way to set a flag similar to the web, to tell the Identity Extension to create the ECID locally? 
I could not find anything in this documentation : https://aep-sdks.gitbook.io/docs/foundation-extensions/mobile-core/identity 

Best 

Eric 

[PratheepArunRaj · Accepted solution]

Hello Eric,

To be honest, I am also curious. However, did you go through the new documentation from Adobe on Mobile Implementation? If not, take a look and keep us posted.

Link: https://developer.adobe.com/client-sdks/documentation/identity-for-edge-network/

Thank You, Pratheep Arun Raj B (Arun) | NextRow Digital | Terryn Winter Analytics

[ericb17371700]

Hi Pratheep, 

I also checked those pages and I couldn't find anything regarding deactivation of third party requests there.

Best

Eric 

[leocwlau]

I never use this option.

But referring to the documentation, disableThirdPartyCalls | Adobe Experience Cloud Services, that option is used in the authentication section of the website and requires a normal third-party domain request in the non-authentication section first.

Also, the whole idea is about third-party domain, it is not applicable to native mobile app as "app" is running on mobile phone natively without any domain.

[mjanik]

@ericb17371700 @leocwlau @PratheepArunRaj When I worked on the online banking app where we had similar requirements, Adobe consultant suggested (after checking it with Adobe engineering team) that we can use custom Experience Cloud Server. The trick was that the customer IT had to provide the endpoint which always returned HTTP error, and thus, the extension had to create a fallback ID. That solution was used in production. Maybe someone from Adobe could refer to it? I used this approach in 2021... not sure if it is still valid.