Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Configuring push notification treatments

Updated on August 4, 2022

A push notification treatment represents the message which you want to communicate to your customer through a notification message in an app that you own. It is typically displayed on the lock screen of a mobile device where the app is installed. Opening a push notification brings the user to the app that sent the message.

Pega Customer Decision Hub
  1. Optional: If the default list of fields available on the push treatment form does not contain a property which you require, edit the Decision Data rule form used by push notification treatments.
    1. On the Treatments landing page, click Manage treatments.
    2. On the Decision Data: Push Treatments rule form, click the Form tab.
    3. In the Form fields section, review the list of properties which are available as fields on the Push notification treatment form.
      • To add a field, click the Add field button.
      • To remove a field, click the Remove property icon.
    Any new properties you add to the form are automatically available for all previously created treatments.
  2. On the Treatments landing page, click CreatePush.
  3. Enter a unique name and a description for the treatment.
  4. Specify when the treatment is active.
    • Always
    • Never
    • Within a defined time period
  5. In the Push Message field, provide the text that should be displayed in the push notification.
    Tip: Push Notification shape in the action flow should be configured to reference .OfferData.PushMessage to display the Push Message.
  6. Click Create.
Result: The treatment you created is now available for use in actions.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us