Where can I see explicit Push Notification opt-out status in AJO/AEP?

[ShushmitPa]

Hi Everyone, excited to be part of this awesome community.

I have my first question:

I need to confirm if a user has explicitly opted out of push notifications (either via device settings or an in-app preference center). Especially after sending a Push campaign

Where exactly in the Adobe Experience Platform (AEP) or Adobe Journey Optimizer (AJO) interface can I check a profile's current push opt-out status?

• Is it seen as a specific field/attribute on the individual customer profile (and if so, what is the attribute name)?

• Or is it only reflected in the Push Notification failure/bounce metrics in the Journey reporting?

[SashankaBi1]

Our Push Notification Setup and Consent Handling

We’ve successfully configured push notifications in our systems using Adobe Journey Optimizer (AJO) and Adobe Experience Platform (AEP). Here’s how it works today:

• Whenever a guest logs into our app and enables push notifications on their device, the push token flows automatically into AEP through our configured Push Profile data stream.

         

• These tokens are linked to the guest’s profile using their CRM ID, which means if the same guest logs into multiple devices and enables push, all those devices become addressable for push communications.
• If the guest disables push notifications on any device, the token for that device is removed from the profile. As a result, AJO will not send push communications to that device. This ensures we only target devices where push is actively enabled.

Why We Currently Rely on Token Presence

Our current approach uses token presence as the indicator for addressability and implicit consent. This works well because:

• If a token exists, the device is reachable.
• If the token is removed, the device is effectively opted out.

However, if your organization requires explicit consent tracking for compliance (GDPR, CCPA, etc.), relying only on token presence may not be enough.

Adding a Push Consent Flag for Compliance

If compliance or governance requires explicit consent, you can configure the consents.marketing.push.val attribute in the profile schema. This would allow you to store values like:

• "y" → user has opted in globally for push
• "n" → user has opted out globally for push

Device-Level vs Global Consent

Push is inherently device-specific because OS settings apply per device. Our current approach ensures:

• Push is sent only to devices with valid tokens.
• If a user opts out on one device, that device stops receiving push.

If we add a global consent flag, we can combine it with token presence for targeting:

• If global consent = “n”, suppress push across all devices.
• If global consent = “y”, send only to devices with valid tokens.

---

Summary

We’ve configured push notifications to respect device-level opt-outs automatically. For organizations that need explicit consent tracking, adding the push consent flag is straightforward and ensures compliance while maintaining our current logic for device-level addressability.

[ShushmitPa]

Hi @SashankaBi1 Thanks for the detailed explanation, this makes sense and this aligns with what we need.

So to confirm my understanding:

• Right now, push addressability is fully driven by token presence in AEP, which already handles device-level opt-ins and opt-outs automatically.

• If a user disables push on a device, the token is removed and AJO stops sending to that device, no extra logic needed.

• If we require explicit consent for compliance, we can introduce the consents.marketing.push.val flag to store a global opt-in/opt-out.

• In that model, the global consent value would work together with device-level token presence (e.g., global = “y” + token present = allowed to send).

Thanks so much again for all the help 🙂

[SatheeskannaK · Accepted solution]

@ShushmitPa If mobileSDK is implemented to capture the consent, it should be part of this OOTB Consent & Preferences field group.

https://experienceleague.adobe.com/en/docs/platform-learn/implement-mobile-sdk/app-implementation/co...

https://developer.adobe.com/client-sdks/edge/consent-for-edge-network/

NOTE

While Journey Optimizer provides ways of managing opt-out in emails and SMS messages, push notifications do not require any action on your side, as recipients can unsubscribe through their devices themselves. For example, upon downloading or when using your app, they can select to stop notifications. Similarly, they can change the notification settings through the mobile operating system.

[ShushmitPa]

Thanks so much @SatheeskannaK this was very helpful