We are trying to get In-App messages working using the documentation on
enabling basic lifecycle triggering (device open), but no messages are
being displayed on devices despite send being executed correctly from
ACS.We have Lifecycle enabled in the device codeWe have In-app tracking
enabled within LaunchSDK and Launch and ACS are configured correctly so
Push notifications and Push tracking are working correctly. Just In-App
not working. We are only trying to target all devices, so no specific
a...
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.
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 f...
You need to run a technical workflow to see the app in ACS. It should be
scheduled to run every 15 minutes but the workflow may not be
started.Workflow is called syncWithLaunchAfter that, if you can't see
the app in the dropdown when creating a push it's because you need at
least one application certificate/token in the app config.
Thanks for the clarification. I don't think the logic for this is
correct. Once the ECID is cleared then no further updates can be made to
Adobe Campaign, therefore the application is still contactable in Adobe
Campaign, but we lose the ability to capture any data about it,
including permissions. When we don't respond to user permissions (such
as don't contact me in preferences outside of control panel), or if
other collected data are used to personalize or target messages, then
there could be i...
If the Privacy service is set to OPT_OUT after being opted in, it
doesn’t invoke anything to Adobe Campaign Standard to remove the
registration token. Is this correct behaviour? What is the intended flow
here? Use collectPii to force a blank token before invoking OPT_OUT?
This has been accepted as a bug by Adobe. You can duplicate an OOB push
template and configure with mobile app etc.When you come to use the
template to create a push, the Associate a mobile App to a delivery is
not inherited from the push templateWhen you go back to the push
template the dropdown has disappeared from the UI
I'm a bit puzzled. I can't find anywhere to link the Mobile App being
targeted to a push delivery template. This option doesn't appear in the
template advanced configuration anywhere.The result of this is that
every time one of my users creates a new push message from any push
delivery template, they have to manually select the mobile app they're
targeting from the dropdown.I'm sure I'm just missing something. It
would be a really odd oversight to not have the functionality to
configure this in ...
Your last paragraph was the answer I was looking for thank you. It's for
beyond standard privacy and into (equally standard) permissions. I was
hoping the Profile attributes store available within the Mobile SDK
would have encryption.
https://aep-sdks.gitbook.io/docs/using-mobile-extensions/profile
I'm working with an app dev team who are capturing a preference flag
called OptIn that is being pushing to Adobe Campaign Standard via
collectPii.The developers want to be able to retrieve this flag so they
can show the current status on a preference screen in app.I believe that
they need to store locally on the device to do this. I pointed them
towards using Profile to store this attribute locally and they have
asked how data stored in the local Profile is kept secure?I can't find
any detail in...
It turned out there were 2 issues causing this same end result. 1 was
front end (dev), 1 seems to be an Adobe back end issue. 1 - Front
endDeveloper forgot to put the lifecycle start code into their
app...@Overridepublic void onResume() { super.onResume();
MobileCore.setApplication(getApplication());
MobileCore.lifecycleStart(null);}@Overridepublic void onPause() {
super.onPause(); MobileCore.lifecyclePause();}When lifecycle start was
included the device was registered correctly. 2 - Back end is...
The collectPii workaround has been disabled now that the backend
problems have been resolved and the Launch rule disabled passing token
via contextData.
I'm working with multiple app dev teams and some of them are reporting
that some Android devices being registered target platform Apple. I
believe this is something code related because my application registers
fine on the same Launch property, but I wondered if anyone with
technical knowledge of this process might be able to explain what might
be the issue here. See top line below...
Can someone clarify what impact setting the privacy flag has on data
passed to Adobe Campaign Standard?It is entirely missing from the
expected behaviour grid:
https://aep-sdks.gitbook.io/docs/resources/privacy-and-gdprIs this an
oversight, or intentional?
