Push Notification Tracking Configuration

[sraz]

I am curious if the Adobe Campaign Classic mobile app service offers a similar feature to the "content-available" field found in the iOS configuration of Adobe Campaign Standard.
We are currently working on tracking push notifications, and the app team has requested us to enable this specific field which is necessary for tracking received notifications. However, since we are using Adobe Campaign v7, this field is not available. My question is: does Adobe Campaign v7 have any configuration options or fields that can serve the same purpose as content-available?

Below link has the information about content-available :

https://experienceleague.adobe.com/en/docs/campaign-standard/using/communication-channels/push-notif...

Thanks.

[MeitMedia]

Hi @sraz ,

In Adobe Campaign Classic (v7), there isn’t a direct equivalent to the “content-available” field used in Adobe Campaign Standard for iOS push notifications. The “content-available” field is a specific feature in iOS push notifications used to trigger background processing or silent notifications.

However, you can implement similar functionality by considering the following approaches:

1. Custom Push Notification Parameters: You can include custom parameters in the push notification payload that can be used by your app to handle specific actions or trigger background processes. Modify your push notification delivery settings to include additional fields or flags that your app can interpret as instructions for background processing.
2. Application-Specific Handling: If your app needs to perform certain actions without displaying a notification, you can use silent push notifications by sending a push message with an empty alert. This approach involves configuring your app to handle these notifications appropriately. While not exactly the same, you can configure your push notification message payloads to include the necessary data for silent notifications.

Best regards,

MEIT MEDIA (https://www.meitmedia.com)

Find us on LinkedIn

Contact Us: infomeitmedia@gmail.com

[sraz]

Thank you @MeitMedia  for your response.

I previously spoke with the app team about adding a custom parameter to the push payload. However, they mentioned that the OS won’t recognize this when the app is in the background.

Typically, the payload includes a "content-available" field that wakes the app when it’s in the background, allowing the `trackNotificationReceive` API to track that the notification was delivered to the device.

{

 "aps":{
"alert":
"body". "This is the content of my push notification",
"title". "Push Notification Title"

};
"content-available":1,
"categon.""NEW MESSAGE CATEGORY"
"badge":2,
"mutable-content":1,
"sound" "default"

};
"custom _field1":"custom_valuel",
"custom _field2":"custom_value2",

but if we place this in a custom variable, the payload structure would be like  and the OS won’t understand it or wake up the app.

{

 "aps":{
"alert":
"body". "This is the content of my push notification",
"title". "Push Notification Title"

};

"categon.""NEW MESSAGE CATEGORY"
"badge":2,
"mutable-content":1,
"sound" "default"

};
"custom _field1":"custom_valuel",
"custom _field2":"custom_value2",

"content-available":1,

Right now, we can't track if a push notification is delivered to an iOS device when the app is in the background. However, when the app is in the foreground, we can track it. We can still track when the push notification is clicked in both scenarios.

Thank You.

[MeitMedia]

Hi @sraz ,

• While the OS does not recognize custom parameters for waking the app, ensure your payload includes all required standard fields. I believe the content-available field should be included directly within the aps dictionary to be recognized by iOS.
  Example payload:

{
  "aps": {
    "alert": "This is the content of my push notification",
    "title": "Push Notification Title",
    "badge": 2,
    "sound": "default",
    "content-available": 1
  },
  "custom_field1": "custom_value1",
  "custom_field2": "custom_value2"
}

• Ensure your app is configured to handle silent notifications. Implementing silent push notifications (with an empty alert field) can allow your app to process data in the background without displaying a notification. Your app needs to handle these notifications properly to trigger the desired background processes.
• Since you're already able to track notifications when the app is in the foreground and when they are clicked, continue leveraging these tracking mechanisms. This provides valuable data on user interactions with notifications, even if background delivery tracking is limited.
• As an alternative, consider using server-side tracking methods to monitor notification delivery. This might involve implementing a server-side mechanism to confirm receipt and processing of notifications based on delivery reports from the push notification service.

Unfortunately, without native support for the content-available field, your options are constrained to these workarounds. If tracking background notifications is critical, exploring an upgrade to another push notification service that fully supports this feature might be worth considering.

Best regards,

MEIT MEDIA (https://www.meitmedia.com)

Find us on LinkedIn

Contact Us: infomeitmedia@gmail.com