Can't commit a collectPii request to Adobe Campaign Standard before setting Privacy to OPT_OUT

[JAElliott]

Our app dev teams are struggling to find a way to implement the AEP Mobile SDK Privacy service alongside Adobe Campaign.

Our app has preferences that are collected from a user via a control panel. These determine the type of push notification they wish to receive. They are sent to Adobe Campaign Standard using collectPii.

When the Privacy status is changed to OPT_OUT, we need to update a flag to ACS to stop push notifications going out before setting the Privacy Service to be OPT_OUT. The reason for this is documented in a previous thread, but in summary if we don't then we end up with a disembodied subscribed application in ACS and no means of updating push notification preferences. We want to turn all push notifications off at this stage.

The problem is that when we call collectPii and then immediately set Privacy to OPT_OUT, the collectPii request doesn't complete and commit to ACS.

Any thoughts about how to make Adobe Privacy work nicely with marketing Consent management?

This is hindering release of our apps.

[Ryan_Morales · Accepted solution]

HI @JAElliott,

This behavior is expected as setting privacy to opt-out will prevent all network requests from being sent by the ACP SDK. Adding or removing push notification app subscribers is not handled by the ACP SDK. If the functionality for removing app subscribers is needed, we recommend that you open a customer care ticket with Adobe Campaign so the work can be prioritized.

Thanks,

Ryan

[JAElliott]

Even though the sequence is sending to ACS first, THEN setting privacy status? I'm expecting that we can do something prior to switching everything off.

[JAElliott]

I've raised a support ticket

[Rev_J]

AEP Mobile SDK privacy service deletes all data when set to OPT_OUT, however this is also used to collect consent for push permissions for ACS thereby creating a situation where you have a targetable application in ACS with no means to update consent via the app directly to ACS via collectPii etc. According to our tests, it's currently impossible to update consent in ACS to be false using collectPii prior to setting Privacy = OPT_OUT. Placing these requests in sequence still results in the later Privacy request cancelling collectPii. My enhancement request is that queued requests from the mobile SDK that have been activated during a Privacy OPT_IN state, are executed PRIOR to Privacy OPT_OUT being activated.