AJO Push Token Visible in Assurance but Not Persisting in Profile | Community
Skip to main content
S
SherinJo1
Level 2
January 21, 2026
Question

AJO Push Token Visible in Assurance but Not Persisting in Profile

  • January 21, 2026
  • 2 replies
  • 71 views

I am implementing AJO Push Notifications using AEP Mobile SDK + Edge Network and facing an issue with push profile persistence.

What is working:

  • Push token and ECID are visible in AEP Assurance → Push Debug → Client

  • Edge streaming validation is successful

  • Hits are received and processed in Assurance

  • Events are visible in AEP → Customer → Profiles

Issue:

 

All steps mentioned in the tutorial have been followed: https://experienceleague.adobe.com/en/docs/platform-learn/implement-mobile-sdk/experience-cloud/journey-optimizer/journey-optimizer-push#create-push-credentials

 

2 replies

A
AJODev
Level 4
January 21, 2026

​@SherinJo1 

  1. Check your sandbox permissions; sometimes, even though Assurance shows all required events and push tokens, you might not see them in the setup because of restricted sandbox access.
  2. Also verify the profiles or ECID to ensure that the push token is actually present on the profile before troubleshooting further.

Thanks

 

    S
    SherinJo1Author
    Level 2
    January 22, 2026

    Hi ​@AJODev 

    I do have sandbox permissions
    In AEP Assurance > Push Debug:

    • Client has both ECID and Push Token
    • Under Profiles only ECID is populated

    I was checking the assurance logs and came across the below, could this be an issue:

     

     

    Manoj_Kumar
    Community Advisor
    Manoj_KumarCommunity Advisor
    Community Advisor
    February 3, 2026

    Check if you have the AJO extension added in Launch

    Manoj  | https://themartech.pro
      arpan-garg
      Community Advisor
      arpan-gargCommunity Advisor
      Community Advisor
      February 12, 2026

      HI ​@SherinJo1  - Push token will only be shared with AEP when the consent is given, in the screenshot you sent i can clearly see consent is set to pending and i believe thats the reason the token is not yet shared with AEP. Collect should be set to ‘y’ for any details to be shared from mobilesdk to AEP.

       

      Thanks,

      Arpan

        Terms & ConditionsAccessibility statement

        Loading footer...