• Categories
  • Recent
  • Tags
  • Popular
  • Solved
  • Unsolved
  • Users
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Darkly)
  • No Skin
Collapse
brainCloud Forums

Question about identifying Notification Template on client side

Scheduled Pinned Locked Moved Unsolved General
1 Posts 1 Posters 15 Views
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • J Offline
    J Offline
    jongdae.won
    wrote last edited by
    #1

    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.

    1 Reply Last reply
    0

  • Login

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Solved
  • Unsolved
  • Users