# Notification Replacement Behavior

## Notification Replacement Behavior

The **Notification Replacement Behavior** setting gives you control over how notifications behave on a subscriber's device. You can choose whether new notifications should replace previous ones or stack alongside them.

This setting is available under the **Behavior** section when creating or updating manual notifications as well as when creating notifications within journeys and is configurable per notification.

Each notification can be configured with one of three behaviors:

* **Stack:** Each notification appears independently in the subscriber's notification tray. Notifications accumulate and remain visible until the subscriber dismisses them individually.
* **Replace All:** Each new notification replaces all previous notifications in the subscriber's tray. Subscribers always see only the most recent notification.
* **Replacement Group:** Notifications are grouped by a custom label you define. A new notification replaces only the previous notification sharing the same group — allowing different content categories to replace each other independently.

### Setting Notification Replacement Behavior

1. From the Notifications list view, click on **Schedule Notification**.
2. Scroll down to the **Behavior** section of the form.
3. Under **Display / Replacement Behavior**, choose one of the following:
   * **Stack:** notifications accumulate in the tray
   * **Replace All**: each new notification replaces all previous ones
   * **Replacement Group**: enter a custom group label to control which notifications replace each other
4. Send the notification.

If no behavior is explicitly set, notifications default to **Stack**.

### Viewing Replacement Behavior

#### Notification Details

After a notification is sent, you can see its resolved Replacement Behavior on the notification details page under the **Delivery** section. The field displays one of:

* **Stack**
* **Replace All**
* **Replacement Group: \<your group label>**

#### A/B Test Details

When viewing an A/B test, each variant's notification preview card shows its own Replacement Behavior value. This makes it easy to compare behavior across variants — particularly useful when testing different replacement strategies against each other.

#### Insights Reporting

Replacement Behavior is available as a dimension column and filter in notification-level Insights reports.

**Adding the Column**

1. Navigate to **Insights** and select a **Notification Report**.
2. In the column selector, find **Replacement Behavior** under the Dimensions group.
3. Select it to add the column to your report.

The column displays the resolved behavior for each notification row (Stack, Replace All, or Replacement Group: \<key>).

**Filtering by Replacement Behavior**

1. In the report filter bar, click **Filter** and select **Replacement Behavior**.
2. Choose one or more values: **Stack**, **Replace All**, or **Replacement Group**.
3. The report will show only notifications matching the selected behavior(s).

When filtering on **Replacement Group**, all notifications using any replacement group key are included — you don't need to specify individual group labels.

### Example Use Cases

| Scenario                                     | Recommended Setting                                                                                      |
| -------------------------------------------- | -------------------------------------------------------------------------------------------------------- |
| Weather forecast updates                     | **Replace All**: subscribers always see the latest forecast                                              |
| Breaking news alerts                         | **Replace All**: subscribers always see the most recent alert                                            |
| Multi-category feed (sports, politics, tech) | **Replacement Group**: use separate groups per category so each replaces only its own prior notification |
| Pollen or air quality alerts                 | **Replace All**: one active alert at a time                                                              |
| Product launch announcements                 | **Stack**: all announcements remain visible                                                              |

**Example:** A weather publisher sends forecast updates throughout the day. By selecting **Replace All**, each new update automatically replaces the previous one in subscribers' notification trays, ensuring they always see the latest forecast rather than a list of outdated ones.

**Example:** A publisher running an A/B test wants to compare Stack vs Replace All performance. After the test completes, they can view each variant's Replacement Behavior on the test details page and use the Insights filter to isolate performance metrics by behavior type.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://documentation.pushly.com/platform/notifications/notification-replacement-behavior.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.