> For the complete documentation index, see [llms.txt](https://documentation.pushly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.pushly.com/faq/release-notes.md).

# Release Notes

{% updates format="full" %}
{% update date="2026-06-22" tags="improvement" %}

## AI Variant Selection Tracking

Pushly now tracks how AI-generated content is adopted by platform users. When a user accepts a Pushly AI variant or a Page Analyzer suggestion, the system records which generation produced the content, which variant was chosen, and whether the content was edited after acceptance.

**Content Source labeling:** wherever Content Source is displayed — notification details, mobile details, summary cards, and Insights reporting — the label now appends **(Edited)** when the user modified AI-suggested content after accepting it (e.g. *Pushly AI* becomes *Pushly AI (Edited)*).

No action required. Existing notifications and the notification template API are unchanged; attribution columns default to empty for historical rows.
{% endupdate %}

{% update date="2026-06-22" tags="improvement" %}

## Notification Icon & Image Macros and Liquid Template Editor

Notification icons and images can now be driven by a per-subscriber Liquid macro, so a single notification can display a different logo or image for each subscriber based on their profile properties. Previously the icon was limited to the domain default or a single static upload.

**New source selector for Icon and Image:**

* **Icon:** Default (domain icon) · Custom (upload) · Macro (per-subscriber dynamic) · None
* **Image:** Custom (upload) · Catalog item type (where applicable) · Macro · None

**Dynamic icons and images:** selecting Macro lets you set the icon or image from a Liquid expression (e.g. `{{ profile.custom_icon_url }}`), a URL with an embedded macro (e.g. `https://example.com/logos/{{ profile.market }}.png`), or a `remote_fetch` tag. The value resolves per subscriber at send time. If a macro resolves to nothing, the subscriber receives no icon or image for that notification.

**Liquid template editor:** Title, Body, Landing URL, and the new icon/image macro fields now include an expand button that opens a full-screen Liquid editor with syntax highlighting, line numbers, a one-click macro insert panel, and a Format action for multi-line templates. Publishers managing multiple brands, regions, or verticals under a single domain can now deliver personalized notification branding at scale without duplicating notifications or managing separate sends per audience.

Existing static icons and images are fully backward compatible and unchanged.
{% endupdate %}

{% update date="2026-06-17" tags="improvement" %}

## Separate AI vs Page Analysis Field Settings

Domain Field Settings for notification automation can now be configured independently for **Content Suggestions** (Page Analysis) and **AI Recommendations** (Pushly AI). Previously, a single setting controlled which fields (Title, Body, Image, Keywords) were auto-populated by both sources — making it impossible to configure them separately.

**What changed:**

* **Content Suggestion Fields** — controls which fields Page Analysis populates when analyzing a Landing URL
* **AI Recommendation Fields** — controls which fields Pushly AI populates when generating notification variants
* AI recommendation results are now filtered server-side to allowed fields (previously this was browser-only)

Manage both settings under **Domain Settings > Notifications > Automation Settings > Edit**.

**Backward compatible:** existing domains are automatically migrated — prior field settings carry over to Content Suggestion Fields, and AI Recommendation Fields default to all fields enabled.

{% endupdate %}

{% update date="2026-06-08" tags="improvement" %}

## Mobile Experience Refresh

The Pushly platform's mobile experience has been completely redesigned. This release replaces the previous mobile view with an expanded, modernized implementation available to all platform users with no setup required.

**What's new:**

* **KPI Dashboard:** three summary cards (Push Subscribers, Clicks, CTR) with trend indicators and 7-day sparklines replace the single "Clicks Yesterday" metric
* **Drafts tab:** manage saved drafts directly from mobile with archive, edit, and duplicate actions
* **Swipe actions:** swipe left on any notification card to reveal Edit, Duplicate, Cancel, or Archive. No more tapping to expand inline
* **Quick View:** tap any card to open a bottom sheet with full notification details and action buttons
* **Notification Detail page:** full-screen view with content, performance stats (Impressions, Clicks, CTR), and delivery metadata. Entirely new to mobile
* **Insights:** dedicated analytics view with date presets, interactive charts, and top-performing notifications. Entirely new to mobile
* **Improved Domain Switching:** pinned domains, recents, and organization grouping, matching the desktop experience

Compose and Edit continue to use the shared notification builder, optimized for mobile with non-essential panels hidden and Save as Draft supported.
{% endupdate %}

{% update date="2026-06-02" tags="improvement" %}

## Session Timeout and Refresh Token Handling

Active users will no longer be interrupted mid-task by unexpected session expiration. The platform now silently refreshes sessions in the background while you are actively working — only genuine user interactions such as clicks, form inputs, and navigation keep the session alive.

**Two prompts handle cases where a session does need to end:**

1. **Inactivity warning ("Stay signed in?"):** appears when you have been idle and your session is about to expire. Shows a countdown timer with two options: Stay signed in (resets the countdown) or Sign out. If the countdown reaches zero with no action, you are signed out automatically.
2. **Maximum-duration warning ("Sign in again to keep working"):** appears as you approach the hard session lifetime cap. This prompt has no extend option — the maximum duration is a fixed security cap. Save your work and sign back in to continue.

**Session timeout settings (configurable per organization):**

| Setting          | Default Value | Description                               |
| ---------------- | ------------- | ----------------------------------------- |
| Idle timeout     | 10 hours      | Session ends after this much idle time    |
| Absolute timeout | 10 hours      | Maximum total session lifetime from login |

This release builds on and extends the Session Heartbeat and Expiration UX improvements introduced on February 11, 2026.
{% endupdate %}

{% update date="2026-05-27" tags="improvement" %}

## Notification Save: Landing URL Validation

When saving or scheduling a notification through the notification builder, Pushly now automatically performs a server-side health check on the Landing URL before the notification is queued for delivery. This helps catch broken, misconfigured, or malformed URLs before they reach subscribers.

If the URL returns a non-200 response, a warning step is added to the Delivery Confirmations modal showing:

* The specific HTTP status code returned (e.g., 404 Not Found, 500 Server Error)
* A clickable link to the Landing URL for direct verification
* The final redirect destination if the URL redirected

The check is **advisory and non-blocking** — users can acknowledge the warning and choose to proceed. Supported warning scenarios include non-200 HTTP responses, DNS failures, connection timeouts, SSL errors, and malformed protocols.

**What is not affected:** feed sends and API sends bypass this check entirely.

The check is **disabled by default** per domain. Enable it under **Domain Settings > Notifications > General Settings > Edit > Delivery > Landing URL Validation**.

**Documentation:** [Landing URL Validation](https://documentation.pushly.com/platform/notifications/landing-url-validation)
{% endupdate %}

{% update date="2026-05-21" tags="improvement" %}

## WordPress Plugin 2.3.0

WordPress Plugin 2.3.0 is a stability, compatibility, and security release. There are no new user-facing features and no configuration changes required. Publishers can safely upgrade to WordPress 7.0 and to plugin version 2.3.0 in any order.

**WordPress 7.0 Compatibility:** the full integration test suite (66 tests, 222 assertions) passed cleanly against WordPress 7.0. The "Tested up to" header has been updated to 7.0.

**PHP Compatibility:** tested and passing on PHP 7.4, 8.3, and 8.4. Minimum PHP requirement remains 7.4.

Update via WordPress admin — no manual steps required.

**Documentation:** [WordPress Plugin Integration Guide](https://documentation.pushly.com/integration/web-browser-push/wordpress-plugin)
{% endupdate %}

{% update date="2026-05-13" tags="new-feature" %}

## Item Catalog Browser

A new Catalog section is now available in the Pushly platform's left navigation, giving publishers a direct, searchable view of all their catalog items without leaving the platform.

The Catalog Browser displays items in a paginated table that automatically adapts its columns to the domain's configured catalog type:

* **Recipes:** Image, Name, Category, Cuisine, Keywords
* **Events:** Image, Name, Genre, Performer, Location, Availability

**Key capabilities:**

* **Full catalog visibility:** browse all indexed items with thumbnail previews and catalog-type-specific metadata
* **Server-side search:** search across items by name, URL, or other properties — handled server-side for accuracy and performance
* **Availability and status indicators:** clear item-state indicators at a glance
* **Direct item links:** item names link to their canonical URLs and open in a new tab

The section label in the navigation adapts to the domain's catalog type (e.g., "Recipe Catalog" or "Event Catalog"). The view is read-only for all users.
{% endupdate %}

{% update date="2026-05-13" tags="new-feature" %}

## Event Webhooks

Event Webhooks are a new real-time data delivery system that sends structured notification engagement data to customer-defined endpoints the moment subscriber interactions occur. When a subscriber sees or clicks a notification, Pushly immediately delivers a cryptographically signed POST request to the customer's configured URL.

**Supported events (v1):**

* Notification Displayed: fires when a subscriber's device renders a push notification
* Notification Clicked: fires when a subscriber taps or clicks a push notification

**Each payload includes:**

* Subscriber identity: Pushly subscriber ID and external ID
* Device context: platform, OS, browser, device type, timezone, and geolocation
* Notification details: title, body, keywords, source, delivery type, associated segments and campaign
* Event metadata: unique event ID for deduplication, precise timestamp, domain context

**Key capabilities:**

* Cryptographically signed requests for authenticity verification
* Automatic retries with increasing delays on failure
* High throughput processing (thousands of events per second)
* Secret management for authentication headers

**Key use cases:** real-time analytics pipelines, CDP and CRM integration, marketing automation triggers, attribution and conversion tracking, internal alerting and monitoring.

Configure webhooks under **Domain Settings > Event Webhooks**.

**Documentation:** [Event Webhooks](https://documentation.pushly.com/platform/event-webhooks)
{% endupdate %}

{% update date="2026-05-11" tags="improvement" %}

## Replacement Behavior: Details and Insights

Building on the Notification Replacement Behavior feature released on April 21, publishers can now view and report on the resolved replacement behavior for any notification — not just at the point of authoring.

**Replacement Behavior on Notification Details:** the Delivery section now shows a Replacement Behavior field (Stack, Replace All, or Replacement Group: \[key]) for every sent notification, regardless of source.

**Replacement Behavior on A/B Test Details:** each variant's preview card in the Notifications tab now displays its own Replacement Behavior value, making it easy to compare strategies across variants.

**Replacement Behavior in Insights Reporting:** available as a selectable dimension column and as a filter in notification-level reports. Included in CSV and XLSX exports when selected.

{% endupdate %}

{% update date="2026-04-25" tags="improvement" %}

## Platform UI Refresh

The platform has been updated with a modernized look and feel across every page. All existing workflows, layouts, navigation, and features remain exactly the same.

#### Redesigned Sidebar and Domain Switcher

* **Search:** type to find any domain instantly
* **Favorites:** star frequently used domains so they always appear at the top
* **Recents:** recently visited domains are surfaced automatically
* **Keyboard navigation:** arrow keys to navigate, Enter to select, P to toggle a favorite
* Virtualized rendering for smooth performance with large domain lists

#### Standardized Filter Bar

All list views — Notifications, App Messages, Segments, Campaigns, and Reporting — now share a consistent inline tag-based filter bar supporting date, date range, number, and single or multi-select dropdown filters.

#### Other Improvements

* **Unified Status Badges:** consistent icons and color treatment for statuses across all entity types
* **Improved Cards and Panels:** collapsible sections, dividers, smoother loading states, consistent padding
* **Streamlined Tables:** consistent modern table layout throughout; Journeys migrated to the new table style
* **Journey and Campaign Views:** tabbed layout for easier navigation between configuration, summary, and notifications
* **Accessibility:** better screen reader support, keyboard navigation improvements, WCAG 2.0 AA scanning across 42 routes
* **Dark Mode (Internal Preview):** available for internal team members via the theme toggle in sidebar settings
  {% endupdate %}

{% update date="2026-04-21" tags="new-feature" %}

## New Replacement Behavior for Notifications

Publishers can now configure Notification Replacement Behavior on a per-notification basis when creating manual notifications or building journey steps. This controls how a notification behaves in a subscriber's device notification tray when multiple notifications have been delivered.

Three options are available:

* **Stack** (default): each notification appears independently in the tray. Notifications accumulate until the subscriber dismisses them. This is the existing behavior and is fully backward compatible.
* **Replace All:** each new notification replaces all previous notifications in the tray. Subscribers always see only the most recent notification. Best suited for frequently updating content such as breaking news alerts, weather forecasts, or live scores.
* **Replacement Group:** notifications are grouped by a custom label. A new notification replaces only the prior notification sharing the same group label, leaving other groups unaffected. Ideal for multi-category publishers who want each content category to maintain its own independent notification thread.

The setting is available under the **Behavior** section in the notification creation form.

**Documentation:** [Notification Replacement Behavior](https://documentation.pushly.com/platform/notifications/notification-replacement-behavior)
{% endupdate %}

{% update date="2026-04-02" tags="new-feature" %}

## Notification Builder Enhancements: Page Analyzer and A/B Testing Flow, and Item Engagement Events

#### Notification Builder: Page Analyzer and A/B Testing Flow

When triggering content recommendations in the Notification builder, users are now presented with two options:

* **Autofill Content:** automatically populates the notification's title and body fields with content extracted from the landing page
* **Review Content Suggestions:** opens the side-panel review flow to evaluate suggestions and manually apply preferred options

The A/B testing setup flow has been refreshed with a more streamlined variant creation experience within the notification builder. The Notification View summary section has also been updated with a cleaner layout showing delivery status, channel, targeting, engagement metrics (impressions, clicks, CTR), a Performance Breakdown by Channel visualization, and a rendered device preview.

#### Item Engagement Events: Completion and Rating Support

Pushly now supports two new catalog item interaction events:

* **Complete Item:** tracks when a subscriber has completed or made a catalog item (e.g., cooked a recipe). Available in Journeys, Segments, and SDK event collection. A new "Made or Completed Item" Journey action is available alongside existing item actions.
* **Rate Item:** tracks when a subscriber has rated a catalog item on a scale of 0 to 100.

Two new segmentation attributes are now available under **E-Commerce / Catalog:**

* **Made / Completed Item Count:** build segments based on how many items a subscriber has made or completed
* **Rated Item Count:** build segments based on how many items a subscriber has rated

Both support configurable time windows (1, 7, 14, 30, 60, 90 days) and full AND/OR logic with existing segment conditions.
{% endupdate %}

{% update date="2026-04-02" tags="new-feature" %}

## Journeys: A Complete Rebuild of the Campaign Experience

Campaigns has been fully rebuilt and renamed to Journeys. The journey builder features a new visual canvas, a proper multi-path A/B/n branching model, significantly improved reporting, and a modernized list and summary experience. All existing campaign data, configurations, and permissions are fully preserved. Existing `/campaigns` URLs automatically redirect to `/journeys`.

#### A/B/n Split Testing

Add a Split Test step anywhere in a journey to divide the incoming subscriber audience into 2 to 4 named variant branches, each with a configurable percentage of traffic. Each branch is fully independent and can contain its own sequence of delays, notifications, and nested split tests. All variant branches automatically converge at a downstream join point.

#### New Visual Canvas

The journey canvas has been rebuilt with a professional automatic layout engine featuring clean orthogonal edge routing, symmetric branch layouts, and dynamic viewport sizing.

#### Placeholder Steps and Add Step Panel

New journeys start with a visible placeholder step to guide first step insertion. The step insertion UI has been redesigned as a descriptive floating panel with step names, descriptions, and logical categories.

#### Unsaved Changes Protection

Navigating away while changes are pending triggers a browser confirmation dialog. The Save button label updates dynamically to "Save Changes" when unsaved edits are present.

#### Journeys List and Summary Improvements

The Journeys list is now paginated with sticky filters, inline audience segment information, and inline performance metrics. The journey summary page includes a collapsible modern header, a performance graph with custom date range selection and grouping, and a new Insights tab with Notification, Step, and Split Test Variant performance breakdowns.

#### Auto-Generated Step Names and Reporting

Journey steps receive auto-generated human-readable names (e.g., "Variant A > Notification #1"). Insights now supports breakdowns by Step, Split Test, and Split Test Variant.

Documentation: [Journeys](https://documentation.pushly.com/platform/journeys)
{% endupdate %}

{% update date="2026-02-25" tags="improvement" %}

## Campaign Step Selection Panel

A new step selection panel has been added to the Campaign Builder. Steps are now organized into logical categories with visual icons and descriptive labels, replacing the previous small unlabeled icons.

**Available step types:**

**Timing:**

* Wait: pause the campaign for a configured amount of time before the next step executes

**Notifications:**

* Custom Notification: create and send a fully customized push notification
* Abandoned Cart: send a reminder about items left in a subscriber's cart
* Saved Item Reminder: send a reminder for items a subscriber has saved
* Recently Viewed Item: follow up on catalog items the subscriber has recently viewed
* Trending Item: send top-performing catalog items based on recent activity
* Personalized Recommendation: send AI-selected personalized items (currently powered by BlueConic)

**Documentation:** [Journeys](https://documentation.pushly.com/platform/journeys)
{% endupdate %}

{% update date="2026-02-11" tags="improvement" %}

## Session Heartbeat and Expiration UX and App Message Preview Window

#### Session Heartbeat and Expiration UX

The platform now includes a lightweight session heartbeat that tracks expiration state in the client and handles it proactively, replacing the previous experience of ambiguous 403 errors and abrupt logouts.

* **Session Expiration Warning:** a visible warning notification appears 5 minutes before a session expires, giving users time to save work and re-authenticate.
* **Dedicated session-expired screen:** once a session expires, a dedicated screen is displayed with a Sign In button. After signing in, the platform redirects back to the last page the user was on.

#### App Message Preview Window

A new App Message Previews window is now available from the App Message builder, rendering messages in realistic device frames with support for:

* **Device Type:** Phone or Tablet
* **Orientation:** Portrait or Landscape
* **Theme:** Light or Dark
* **Platform filtering:** e.g., Apple/iOS

This makes it faster to catch layout issues such as text truncation, button crowding, and dark mode contrast problems before publishing.

**Documentation:** [App Messages](https://documentation.pushly.com/platform/app-messages)
{% endupdate %}

{% update date="2025-12-10" tags="new-feature" %}

## Organization-Level Insights Reporting

Enterprise customers managing multiple domains can now access a unified Insights view that aggregates notification and subscriber acquisition performance across all their properties in one report.

Users with organizational-level access will see a new Insights section in the navigation. V1.0 includes two report types:

* **Notification Report:** delivery and engagement metrics across all domains, with a new Organization Notification Group concept that links each notification group to its corresponding domain-level performance when a domain breakdown is applied.
* **Acquisition Report:** subscriber acquisition trends and channel performance across all domains.

A domain-level filter allows users to narrow any org-level report to one or more specific domains for comparison. The reporting table component has been updated with column resizing and improved layout stability for large data sets.

**Documentation:** [Insights](https://documentation.pushly.com/platform/insights)
{% endupdate %}

{% update date="2025-11-11" tags="improvement" %}

## Campaign Builder UX Improvements and Expanded Click Look-Back Windows

#### Campaign Builder UX Improvements

* **Unsaved changes awareness:** the interface now clearly indicates that there are unsaved changes when edits are made in the Campaign Builder. Attempting to navigate away while changes are pending shows a visible warning.
* **Tab navigation protection:** switching to a tab that would discard unsaved changes is blocked while pending edits are present.
* **Improved layout and visibility:** the Visual Builder canvas height is now capped at 900px so that the Save button remains visible on most screen sizes without excessive scrolling.
* **Campaign TTL persistence fix:** Notification Lifespan (TTL) values now save correctly for all campaign action steps.
* **Notification form data integrity fix:** notification form values now remain stable whenever a form is reloaded or revisited, across schedules, templates, and campaign actions.

#### Expanded Click Look-Back Windows for Seasonal Retargeting

* **Keyword Click** look-back windows now extend up to **120 days** (previously capped at 90 days)
* **Notification Click** look-back windows now extend up to **365 days** for eligible domains (previously capped at 90 days)

This makes it possible to build audiences like "clicked a Prime Day notification in July" when planning a Black Friday campaign in November. All shorter look-back windows remain available.
{% endupdate %}

{% update date="2025-10-08" tags="improvement" %}

## Notification Schedule Overlap Confirmation and Real-Time Audience Size Sync

#### Notification Schedule Overlap Confirmation

When creating or scheduling a notification, the platform now automatically checks for other upcoming sends targeting the same audience within a configurable time window. If a potential overlap is detected, a confirmation step is added to the delivery flow showing the conflicting notification's ID, send time, and audience overlap details. Publishers can then choose to confirm and continue or cancel.

Configure the overlap window under **Domain Settings > Notifications > Confirmation Window**.

As part of this release, all delivery confirmation steps have been consolidated into a single unified wizard flow. The three steps are:

1. **Audience Conflict:** warns if the same audience and landing URL were recently targeted within the last 7 days
2. **Notification Schedule Overlap:** detects overlapping scheduled sends for the same audience within the configured window
3. **Confirm Scheduled / Immediate Send:** final verification before delivery is confirmed

#### Real-Time Audience Size Sync for Segments

Segment audience sizes now update in real-time and remain consistent between the Segment List View and the Edit Segment View. Previously, list view counts were only refreshed once per day. The segment list now loads immediately and sizes update in the background, so the numbers teams rely on for campaign targeting are always current and accurate across both views.
{% endupdate %}

{% update date="2025-09-22" tags="new-feature" %}

## Segment Filtering for Notifications, Segment Data in Subscriber Sends, and E-Commerce Settings

#### Segment Filtering for Notifications

Editorial teams can now filter the Notification List page by one or more audience segments directly from the toolbar. This makes it easy to see all upcoming and scheduled notifications targeting a specific segment before adding another send, helping publishers avoid over-messaging the same audience and reducing scheduling conflicts.

Selecting multiple segments applies an OR filter, showing any notification that targets at least one of the selected segments. Filter selections persist per user profile across sessions until cleared.

#### Segment Data in Subscriber Sends

The `segment_names` macro is now hydrated for Subscriber sends that are part of a campaign, bringing them to parity with Standard sends. Downstream services and notification personalization that rely on segment context will now work consistently regardless of send type.
{% endupdate %}

{% update date="2025-09-05" tags="new-feature,improvement" %}

## BlueConic Integration and Workflow Enhancements, Segment Selection Improvements, and remote\_fetch for Dynamic Content

#### BlueConic Integration and Workflow Enhancements

Campaign steps within the Journey builder now open in a View-Only format by default, preventing accidental edits when reviewing a step that has already been configured. An explicit Edit button is required to enter edit mode. An Edit Campaign action has been added directly to the Campaign Details page, eliminating the need to navigate back to the builder to make changes. All Journey Step drawer headers now clearly display their current state — Edit, View, or Create.

#### Segment Selection Improvements

The segment selection dropdown now shows a "Recently Targeted" group at the top, listing the five most recently used segments for the domain (based on last targeted date). All segments are organized into clearly labeled groups below, making it easier to scan for the right audience. A bug that caused System Segments to inaccurately reflect active channels for a domain has also been resolved.

#### New: remote\_fetch for Dynamic Content

A new `remote_fetch` content source type is now available for technical publishers who need truly real-time, personalized notification content. When a notification is being prepared for delivery, `remote_fetch` makes a secure server-side request to a publisher-defined URL and uses the response to populate notification fields at send time — so each recipient gets content that reflects their unique context at the exact moment the notification is sent.

Use cases include: current weather conditions, a subscriber's loyalty points balance, live sports scores, personalized product recommendations, or any data that changes frequently and should not be pre-populated at authoring time. If the external data source is unavailable at delivery time, the notification still sends using a configured default fallback message.
{% endupdate %}

{% update date="2025-08-25" tags="new-feature" %}

## BlueConic Content Recommendations Integration

Pushly now integrates with the BlueConic Customer Data Platform (CDP) to power personalized content recommendations inside web push notifications. This integration allows publishers to connect their BlueConic instance once and then use it as a dynamic content source across all future campaigns.

Once the integration is configured, the Pushly notification builder can pull recommended article or product items from a subscriber's individual BlueConic profile. These recommendations are injected as dynamic content blocks inside notifications, so each subscriber receives content specifically chosen for them based on their interests and past behavior.

**Key capabilities:**

* **One-Time Setup:** configure the integration once from Platform Integrations > BlueConic. Map BlueConic listener profiles to Pushly subscriber segments to establish the data connection.
* **Intelligent Recommendations:** leverage BlueConic recommendation algorithms directly from within Pushly to automatically generate personalized notification content based on individual subscriber activity.
* **Advanced Filtering:** use included items, excluded items, and product filters to fine-tune recommendations, ensuring the most relevant content reaches the right audiences.
* **Multiple Configurations:** create and manage multiple recommendation algorithm configurations per organization, allowing different strategies to be applied to different campaigns or audience segments.

**Documentation:**

* [BlueConic Integration](https://documentation.pushly.com/platform/platform-integrations/blueconic)
* [Using BlueConic in Campaigns](https://documentation.pushly.com/platform/platform-integrations/blueconic/using-blueconic-in-campaigns)
  {% endupdate %}

{% update date="2025-07-29" tags="improvement" %}

## Bulk Feed Actions and Prompts Editor Refresh

#### Bulk Feed Actions

Publishers can now select multiple feeds at once and perform bulk operations directly from the Feeds list in both the Platform and Halo. A new row selection column appears on the left of the table, and a "Bulk Actions" dropdown appears in the table header when one or more feeds are selected.

The menu is context-aware: if all selected feeds share the same status (all Enabled or all Disabled), only the opposite action is shown. If feeds with mixed statuses are selected, both Enable and Disable actions are shown and apply to all selected feeds simultaneously. Archive is always available regardless of the current feed status. This change also unifies the Feeds list code between Platform and Halo, meaning future improvements will roll out consistently to both interfaces. In Halo, the Create Feed button has been moved to the top-right corner to align with the Platform UX.

#### Updates to Prompts Editor

The Platform Prompts Editor has been visually refreshed to match the design language used in Notifications and App Messages. The Bell Prompt option has been removed as it was previously deprecated and no longer supported. The Prompt Preview has been fully redesigned to more accurately reflect how a prompt appears in a live environment, including a new Safari-specific preview so publishers can see exactly what subscribers will see across different browsers.
{% endupdate %}
{% endupdates %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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/faq/release-notes.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.