> 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/integration/web-push/wordpress-plugin/sending-notifications-from-the-post-editor.md).

# Sending Notifications from the Post Editor

How to send a push notification when you publish a WordPress post, and how to control who receives it

Once the plugin is configured, a **Pushly** panel appears in the post editor sidebar. From there you can send a push notification for the post you are publishing, change the notification's wording, and choose which subscribers receive it.

{% hint style="info" %}
The panel only appears when **Send Notifications for New Posts** is enabled on the Pushly settings page and the post type you are editing is listed under **Enabled Post Types**. See Installation & Setup.
{% endhint %}

## Send Notification

Check **Send Notification** to create a push notification when the post is published. Everything else in the panel is disabled until this box is checked.

<figure><img src="https://810756845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Lry9Z27iWOZyQEGAgY7%2Fuploads%2FaiBFrZTarIUzBwEBDuck%2FScreenshot%202026-09-04%20at%204.42.25%E2%80%AFPM.png?alt=media&amp;token=8e4adfcc-055f-4ed8-a1df-cc63da9ae1d1" alt=""><figcaption></figcaption></figure>

If **Automatic Sending** is enabled in the plugin settings, this box is checked for you on every new post, and you uncheck it for posts that should not notify.

A post sends at most one notification. Once it has sent, the panel is replaced by a notice showing the notification ID, and editing or re-publishing the post will not send another.

## Customize Content

By default the notification uses the **post title** as its title and sends no body text. The landing URL is always the post's permalink, and the featured image, tags, and categories are carried across automatically.

Check **Customize Content** to override the wording:

* **Title** — replaces the post title in the notification.
* **Body** — optional supporting line beneath the title.

Leaving Customize Content unchecked is the common case and needs no attention.

## Refine Audience

By default a notification goes to **all subscribers**. Check **Refine Audience** to narrow that, using two independent fields:

* **Targeted Segments** — who receives the notification. Leave it empty to reach all subscribers.
* **Excluded Segments** — who is held back from it. Leave it empty to exclude nobody.

Each field shows its empty behavior as placeholder text, so you can confirm the audience at a glance without sending anything.

<figure><img src="https://810756845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Lry9Z27iWOZyQEGAgY7%2Fuploads%2Fb59CuNUY3dNIo1qm5uap%2FScreenshot%202026-09-04%20at%204.43.33%E2%80%AFPM.png?alt=media&amp;token=09bbbb66-e41b-486f-bae3-1ac788a79505" alt=""><figcaption></figcaption></figure>

Excluding without targeting is the way to say "send this to everyone except…" — for example, promoting a subscription offer to every reader who is not already paying.

Both fields draw from the segments configured on your Pushly domain. Start typing to filter, or click the field to see the full list. If your domain has no segments yet, the Refine Audience option does not appear at all.

{% hint style="info" %}
Segment exclusion requires plugin version **2.4.0** or later. Earlier versions offer targeting only.
{% endhint %}

## When the Notification Sends

* **Publishing immediately** sends the notification right away.
* **Scheduling the post for a future date** creates a notification scheduled for that same time. The notification is created when you schedule the post, and delivers when the post goes live.

## Classic Editor

In the classic editor the Pushly meta box offers **Send Notification** and **Customize Content** only. Audience controls are not available there — a notification sent from the classic editor goes to all subscribers.

To target or exclude segments, use the block editor, or build the notification in the Pushly platform instead.

## Troubleshooting

If you publish a post with **Send Notification** checked and no notification appears in the Pushly platform, enable the [Activity Log](/integration/web-push/wordpress-plugin/activity-log.md) and publish again. It records each step of the send, including the exact error returned by the Pushly API.


---

# 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, and the optional `goal` query parameter:

```
GET https://documentation.pushly.com/integration/web-push/wordpress-plugin/sending-notifications-from-the-post-editor.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.