Question about identifying Notification Template on client side

[jongdae.won]

Hello brainCloud Support,

We are using brainCloud Push Notifications through the Portal Notification Templates feature.

Our current use case is:

We create notification templates in the brainCloud Portal.
We send or schedule notifications from the Portal.
On the client side, when the user opens a push notification, we need to identify which notification template was used.
Currently, the payload we can see appears to only include the APNs payload, like:

{
  "aps": {
    "alert": {
      "body": "Push message"
    }
  }
}

We would like to know:

Is there any way to add custom data or a custom top-level payload field when sending notifications from Portal Notification Templates?
For example:

{
  "aps": {
    "alert": {
      "body": "Push message"
    }
  },
  "notificationTemplateId": "daily_reward_push"
}

Does brainCloud automatically include the template id, template name, or any other template identifier in the push payload received by the client?

If Portal Notification Templates do not support custom payload data, what is the recommended approach for this use case?
Should we use Cloud Code, Normalized Push Notifications, or Raw Push Notifications instead?

Our goal is to continue managing notification text/localization/scheduling from the Portal if possible, while still allowing the client to distinguish which template triggered the push.

Thank you.

[Paul Winterhalder]

Unfortunately, our notification templating system is very simple and currently only supports simple text notifications. It does not currently push a template id.

We do have plans to revamp the system on our "to-do" list - but it has not been scheduled yet.

We recommend folks use the "raw" template calls - they give devs the most control over what gets sent to the various notification systems.

Paul.