---
updatedAt: 2026-09-10T07:40:48.000Z
agentTools:
  projectIndex: https://dev.cleverbridge.com/llms.txt
---

# Notifications Overview

You can use notifications to upload data exports of transactional data on a regular basis for use in your internal systems. In other words, we send you the purchase-related information we have accumulated through notifications, thereby synchronizing our system with yours. For example, if a new order is placed using an offline <Glossary>payment method</Glossary>, such as a wire transfer, Cleverbridge generates the  Awaiting Offline Payment event, which is synced with your internal systems. For more information on the various notifications and events, see [Notifications Types](https://dev.cleverbridge.com/docs/notification-types).

Use the **Add Notification** button in our <Anchor target="_blank" href="https://subcomm.cleverbridge.com/all/tools/notifications">web admin tool</Anchor> to configure and add notifications.

You can choose to receive notifications for particular events, configure notification delivery to as many contacts as necessary, and define how often this upload takes place you receive these notifications, ranging from real-time for every transaction to monthly for multiple transactions. You can also trigger notifications manually.

Based on how notifications are triggered, they fall into two categories: automated and manual.

<Table align={["left","left"]}>
  <thead>
    <tr>
      <th>
        Automated
      </th>

      <th>
        Manual
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        Automated Notifications are sent instantly or summarized daily, weekly, or monthly. You can set the interval in **Settings** section of Notifications portal. For more information, see [Manage Notifications](https://dev.cleverbridge.com/docs/manage-notifications).

        * \*Real-Time\*\* Notifications are sent immediately with one notification per event, customizable in the Notification Events section. Real Time Notification type corresponds to triggering event.
        * \*Summary\*\* Notifications are grouped by current purchase status in summaries sent daily, weekly, or monthly. Summaries are automatic and grouped by data transmission format.

        If a notification is undelivered, Cleverbridge automatically retries for 48 hours until it is delivered or 24 attempts are completed.
      </td>

      <td>
        Manual notifications are notifications triggered by your click in the **Purchases**search area of the Commerce Assistant. This feature is only available for products and events for which you have configured an automated notification in the **Notifications**portal of the Cleverbridge platform. All automated notifications configured in the Notifications portal are stored and can be resent as manual notifications if necessary.

        There is only one notification per event. The notification type is chosen based on the current purchase status, which means: If the purchase status has changed since the automated notification was sent, the manual notification reflects the most recent purchase status.
      </td>
    </tr>
  </tbody>
</Table>

<Callout icon="🚧" theme="warn">
  ### Important

  By default, data sent in notifications no longer contains the following PII (Personally Identifiable Information):

  * Physical Address Information
  * Remote Host Information
  * Last digits of Remote IP Addresses

  If you currently receive this data in notifications, and you want us to discontinue sending it, contact [Client Experience](mailto:ce@cleverbridge.com).

  For more information about these changes, see [Ensure Global Compliance](https://docs.cleverbridge.com/docs/category/ensure-global-compliance/).
</Callout>

<Callout icon="👍" theme="okay">
  ### Tip

  If you experience issues with managing notifications, see [Troubleshooting Notifications](https://dev.cleverbridge.com/docs/troubleshooting-notifications).
</Callout>

<Callout icon="📘" theme="info">
  ### Note

  The file name used for the notification upload includes a time stamp so files are not overwritten.
</Callout>