> 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/platform/feeds.md).

# Feeds

Use Feeds to automatically ingest fresh content from your sources and power targeted, timely Notifications

Navigate to the Notifications page and click the arrow to the right of Schedule Notification. You will see an option to Create Feed

<figure><img src="https://810756845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Lry9Z27iWOZyQEGAgY7%2Fuploads%2FDXW10P6UAjcX85OTSTwK%2FScreenshot%202025-11-11%20at%201.50.16%E2%80%AFPM.png?alt=media&amp;token=0f5da5dd-8d21-4fc2-984c-cf4c7e6e07cc" alt="" width="419"><figcaption></figcaption></figure>

Name your Feed, select the appropriate **Feed Type** (RSS, JSON, or XML), and input the Feed URL where the platform will pull articles from. Make sure you set the Feed Status toggle to active so the Feed can begin processing new content. If you would not like to send notifications to your users, keep the Feed Status toggle as Inactive

<figure><img src="https://810756845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Lry9Z27iWOZyQEGAgY7%2Fuploads%2Fqk729LF05pkgPiyJEwZM%2FScreenshot%202025-11-11%20at%201.54.36%E2%80%AFPM.png?alt=media&amp;token=2732a428-91f8-4f13-831e-02d3028042d8" alt=""><figcaption></figcaption></figure>

Set the Publishing Mode to **Auto Publish** if you want Notifications created from the Feed to be automatically queued and sent when new content is available. If you prefer to review each Notification before it is sent, select **Create as Draft** so Notifications remain in a draft state until you approve them. Keep the setting at Auto Publish if you do not want to manually review and publish each Notification.

<figure><img src="https://810756845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Lry9Z27iWOZyQEGAgY7%2Fuploads%2FH2dKAHcuHPCH61BCWgmg%2Fdelivery_channel.png?alt=media&amp;token=afdc47c5-5620-42ef-a250-fc5352c1e7ec" alt=""><figcaption></figcaption></figure>

If you use Pushly for both web and app support, you will have the option to select for which channels the Feed is intended

<figure><img src="https://810756845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Lry9Z27iWOZyQEGAgY7%2Fuploads%2FASekyrJe6BSMKle08coo%2FScreenshot%202025-11-11%20at%203.30.23%E2%80%AFPM.png?alt=media&amp;token=56d37659-3a88-4a63-8473-a166d8ff95a4" alt=""><figcaption></figcaption></figure>

Select the audience Segment you want the Feed to send to. If you want the Feed to send to a specific Segment, create that Segment before configuring the Feed so it appears as an option in the dropdown. If you do not select a specific Segment, the Feed will send to **All Subscribers** by default.

<figure><img src="https://810756845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Lry9Z27iWOZyQEGAgY7%2Fuploads%2Fvhj2tNadJKlXGZPDi9Zy%2FScreenshot%202025-11-11%20at%203.33.07%E2%80%AFPM.png?alt=media&amp;token=140a0ba7-8e4c-413b-a6ba-8f3a95d329f1" alt=""><figcaption></figcaption></figure>

Set the **Delivery Strategy** to control when and how often notifications are created from the Feed

<table><thead><tr><th width="197.25">Delivery Strategy</th><th>Description</th></tr></thead><tbody><tr><td>ASAP</td><td>Create a notification every time a new article is discovered, as long as a previous notification has already been sent based on the specified send frequency.</td></tr><tr><td>Fixed Time</td><td>Schedule one notification per day at the specified Send Time in the domain time zone. If no new article is found at that time, the system continues checking for up to 1 hour after the Send Time</td></tr><tr><td>Subscriber Time Zone</td><td>Schedule a notification at the specified Send Time in each subscriber’s time zone. To support all time zones, the article is selected at least 24 hours before the Send Time</td></tr></tbody></table>

Choose the **Send Time and Send Days** to define the exact time and days of the week when notifications from this Feed should be delivered

Configure **Pre-Schedule** to determine how far in advance a notification is created before its Send Time.

* For example, if the Send Time is 2:00 PM and Pre-Schedule is set to 15 minutes, the notification is created at 1:45 PM and scheduled to deliver at 2:00 PM.

Apply **Holiday Filters** if relevant to your use case so notifications are not sent on certain holidays

<table><thead><tr><th width="214.41796875">Holiday Selection</th><th>Description</th></tr></thead><tbody><tr><td>None</td><td>No Holidays are applied and the feed can be configured to send notifications irrespective of holiday schedule</td></tr><tr><td>Country</td><td>Select from a list of countries you would like to align the holidays from</td></tr><tr><td>Financial/ Bank</td><td><p></p><ul><li><strong>NYSE</strong>: Uses NYSE market holidays, which cover all major US exchanges including NASDAQ.</li><li><strong>European Central Bank</strong>: Uses Trans-European market holidays, which cover Euro-based exchanges.</li></ul></td></tr></tbody></table>

Set **Notification Lifespan** to control how long the system will continue attempting to deliver a notification to a subscriber

* **Domain Default**: Use the current default lifespan configured in Domain Settings.
* **Custom**: Specify a custom lifespan that applies to all notifications created by this Feed.

<figure><img src="https://810756845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Lry9Z27iWOZyQEGAgY7%2Fuploads%2Fgo2voxrMR65QOkM4mcM1%2FScreenshot%202025-11-11%20at%203.45.13%E2%80%AFPM.png?alt=media&amp;token=cf8a36ed-b857-4404-bc96-35fda6fb528d" alt=""><figcaption></figcaption></figure>

In **Notification Fields**, add or remove fields as needed and apply constraints to pull specific content from the Feed based on criteria such as Keywords, URL parameters, or other metadata. This allows you to fine tune which articles or items are eligible to generate Notifications from the Feed

The **Page Analysis** toggle, when enabled, will attempt to fetch and override the feed’s notification content from the landing URL’s metadata. This will include the **Title, Body, Image and Keywords** tagged for the landing URL

<figure><img src="https://810756845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Lry9Z27iWOZyQEGAgY7%2Fuploads%2FSdJCDoDubGir87116xeO%2FScreenshot%202025-11-11%20at%203.46.08%E2%80%AFPM.png?alt=media&amp;token=0ce58414-917f-4715-9120-d408763d975c" alt=""><figcaption></figcaption></figure>

Use **Article Constraints** to control which articles from your Feed are eligible to generate Notifications

<table><thead><tr><th width="198.51953125">Setting</th><th>Description</th></tr></thead><tbody><tr><td>Article Age</td><td>Defines the maximum age an article can be in order to be eligible for this Feed. Articles older than the specified age will not be considered</td></tr><tr><td>Required Keywords</td><td>The article must contain at least one of the specified keywords to be eligible for this Feed. Keywords are not case sensitive but must be exact matches. This field does not support regular expression pattern matching</td></tr><tr><td>Restricted Keywords</td><td>If the article contains at least one of the specified keywords it will not be eligible for this Feed. Keywords are not case sensitive but must be exact matches. This field does not support regular expression pattern matching</td></tr><tr><td>URL Allow List</td><td>The article URL must contain at least one of the specified URL patterns in order to be eligible for this Feed. Wildcard matching is supported and this field accepts regular expression syntax for more advanced pattern matching</td></tr><tr><td>URL Deny List</td><td>The article URL cannot contain any of the specified URL patterns in order to remain eligible for this Feed. Wildcard matching is supported and this field accepts regular expression syntax for more advanced pattern matching</td></tr><tr><td>Title Deny List</td><td>The article Title cannot contain any of the specified patterns in order to be eligible for this Feed. Wildcard matching is supported and this field accepts regular expression syntax for more advanced pattern matching</td></tr><tr><td>Allow Article Recycling</td><td>When enabled, the Feed can re-send previously sent articles when no unsent articles are available. Recycled articles are sent in order from the oldest previously sent article to the most recently sent</td></tr></tbody></table>

### Using a Feed in a Journey

A Feed no longer needs a schedule of its own. You can leave Delivery Strategy unset and instead add a step to a journey that sends that Feed's current eligible article whenever a subscriber reaches it, driven by journey entry, delays and split tests rather than a fixed time of day.

A Feed used this way still respects its Article Constraints (age, keywords, URL lists, and so on). An article already sent from this Feed, whether by its own schedule or by a journey, will not be sent again from either path.

Once a Feed is submitted, it will appear on the Feeds list for future use

<figure><img src="https://810756845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Lry9Z27iWOZyQEGAgY7%2Fuploads%2FfZwdgtLr6lJqCAosQq4L%2FScreenshot%202025-11-11%20at%203.54.21%E2%80%AFPM.png?alt=media&amp;token=8a5ce680-0484-4fad-b8e0-d7d9e61804f2" alt=""><figcaption></figcaption></figure>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://documentation.pushly.com/platform/feeds.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.