Edit in GitHubLog an issue

Set up a server key

  1. To configure the app in Google Firebase, see Firebase Console and sign in using your Google Developer credentials.

  2. Add a project and add your app under that project using the application ID that you used in the app.

    For more information, see Add Firebase to your Android project.

  3. Add the generated "google-service.json" to the project and set up the project and module level gradle files.

    For more information, see Add Firebase to your Android project.

  4. Verify that Firebase server key is configured in the Campaign instance by clicking Adobe Campaign > Administrator > Channels > Mobile App (AEP SDK).

  5. Select the mobile app from the list and verify that the push channel settings status for Android is Android key set up success.

    Server key configuration in Android

Set up the APNS server certificate

  1. Add Push Notification entitlement to your app.

    For more information, see Enable the Push Notifications Capability.

  2. To configure the APNS certificate, register the app on your Apple developer account and generate the certificate.

    For more information, see Establishing a Certificate-Based Connection to APNs.

  3. Verify that the APNS server certificate is configured in the Campaign instance by clicking Adobe Campaign > Administrator > Channels > Mobile App (AEP SDK).

  4. Select the mobile app from the list and verify that push channel settings status for iOS is iOS certificate with filename *.pem is successfully uploaded.

  5. Verify that you are using production certificate for production environment and development certificate for development environment. Configured push certificate in Campaign

Set up the Android app

  1. Create the Firebase Messaging Service and add it to the Android Manifest file.

    For more information, see Set up a Firebase Cloud Messaging client app on Android.

  2. Generate a push token for the app using FireBase Instance ID class.

  3. In the onComplete function of OnCompleteListener, set the Push identifier by calling the API MobileCore.setPushIdentifier.

    For more information, see setPushIdentifier.

Verify that the push token has successfully synced with the Experience Cloud ID service

If SDK privacy status is optedout, the push identifier will not be set.

  1. Verify the push token sync with the Experience Cloud ID service (ECID).

  2. To verify, launch your app connected to an Adobe Experience Platform Assurance session.

  3. In the list of events, verify that you have an event with type SetPushIdentifier.

  4. In the details panel on the right, verify the value of the push token for this device. The value in pushIdentifier is the same value that is sent to the ECID service. Verify SetPushIdentifier event

  5. To verify that app's push token is mapped to the correct Experience Cloud ID (ECID) in the Campaign instance, click Adobe Campaign > Administrator > Channels > Mobile App (AEP SDK).

  6. Select your app, under the mobile application subscribers verify that the Experience Cloud ID and the Registration token for the user is displayed. App subscriber list, verify mid and push token

  7. If you are using Charles, verify that the push token has successfully synced with the ECID service.

  8. Check for the demdex request, which is marked with the red line in the screenshot below.

  9. Verify the successful response(200) for this network call.

    ECID network request for push token sync

Set up the iOS app

  1. After you launch the app, call registerForRemoteNotifications to register the app and receive the APNS token.

    This API generates and returns the APNS token through the application:didRegisterForRemoteNotificationsWithDeviceToken: delegate function.

    For more information, see Registering Your App with APNs

  2. In application:didRegisterForRemoteNotificationsWithDeviceToken:, call setPushIdentifier to set the Push identifier.

    For more information, see setPushIdentifier.

Verify that the push token has successfully synced with the Experience Cloud ID service

If SDK privacy status is optedout, the push identifier will not be set.

  1. Verify the push token sync with the Experience Cloud ID service (ECID).

  2. To verify, launch your app connected to an Adobe Experience Platform Assurance session.

  3. In the list of events, verify that you have an event with type SetPushIdentifier.

  4. In the details panel on the right, verify the value of the push token for this device.

    The value in pushIdentifier is the same value that is sent to the ECID service. Verify SetPushIdentifier event

  5. To verify that app's push token is mapped to the correct Experience Cloud ID (ECID) in the Campaign instance, click Adobe Campaign > Administrator > Channels > Mobile App (AEP SDK).

  6. Select your app, under the mobile application subscribers verify that the Experience Cloud ID and the Registration token for the user is displayed. App subscriber list, verify mid and Registration token

  7. If you are using Charles, verify that the push token has successfully synced with the ECID service.

  8. Check for the demdex request, which is marked with the red line in the screenshot below.

  9. Verify the successful response (200) for this network call.

    ECID network request for push token sync

Was this helpful?
  • Privacy
  • Terms of Use
  • Do not sell or share my personal information
  • AdChoices
Copyright © 2025 Adobe. All rights reserved.