Skip to main content
SR10
Level 3
August 11, 2023
Solved

RT Push notification in Adobe Campaign Classic

How mobile app push token would be validated for push via RT? Prior to sending out push notifications, does the RT push verify with the appsubscription service?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
abhinav99
abhinav99Accepted solution
Level 4
August 11, 2023

Hi @sr10 ,

The AppSubscription  service usually  checks to see if the push token is valid and belongs to a registered device or not.
If the push token is valid, the AppSubscription service usually returns a status code of 200 OK.
If the push token is invalid, the AppSubscription service returns a status code of 400 ERROR.
If the status code is 200, RT Push will send the push notification to the device.

If the AppSubscription service returns a status code of 400, RT Push will not send the push notification.

 

View in thread

3 replies

abhinav99
abhinav99Accepted solution
Level 4
August 11, 2023

Hi @sr10 ,

The AppSubscription  service usually  checks to see if the push token is valid and belongs to a registered device or not.
If the push token is valid, the AppSubscription service usually returns a status code of 200 OK.
If the push token is invalid, the AppSubscription service returns a status code of 400 ERROR.
If the status code is 200, RT Push will send the push notification to the device.

If the AppSubscription service returns a status code of 400, RT Push will not send the push notification.

 

Translate
    SR10Author
    Level 3
    August 24, 2023

    Hi @abhinav99 ,

    Thank you for your response.

     

    Can you verify this, please? In contrast to real-time emails (where email IDs don't have to be present in the ACC system for using the message center), a real-time push request must carry a valid push token from the AppSubscription Service to send real-time push notifications.

     

    Thanks

    Sankar

    Translate
    akshaaga
    Adobe Employee
    akshaagaAdobe Employee
    Adobe Employee
    August 14, 2023

    @sr10 ,

    The process of validating a mobile app push token for Real-Time (RT) push notifications involves integration with Adobe Campaign and the mobile app's push notification service.

    Here's an overview of the steps involved:

    1. *Integration Setup*: Integrate your mobile app with Adobe Campaign by configuring the necessary settings and APIs to enable push notifications. This involves setting up an integration between Adobe Campaign and the push notification service used by your mobile app (e.g., Firebase Cloud Messaging for Android or Apple Push Notification Service for iOS).

    2. *App Subscription Service*: When a user installs your mobile app, the app typically registers for push notifications with the respective push notification service (e.g., Firebase Cloud Messaging or Apple Push Notification Service). 

    3. *Token Validation*: Before sending out RT push notifications, Adobe Campaign would need to verify the validity of the push tokens. This validation process ensures that the tokens are still active and valid for sending push notifications. 

    4. *Sending RT Push Notifications*: Once the push tokens are validated, Adobe Campaign can use these tokens to send RT push notifications to the intended devices. The push notifications are then delivered via the push notification service to the respective mobile devices.

    It's important to note that the specifics of token validation and integration can vary depending on the push notification service you're using, the mobile app platform (Android or iOS), and the version of Adobe Campaign you're working with.

    Translate
      Terms & ConditionsAccessibility statement

      Loading footer...