> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pocketsflow.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Paid newsletter

> Lock posts behind a monthly or yearly subscription and earn recurring revenue from your newsletter.

A **paid newsletter** connects your email list to your subscription offers.
Readers who subscribe become **paid subscribers**; you choose, post by post,
whether everyone, free subscribers only, or paid subscribers only can read it.
Free subscribers see the start of a paid post and a button to subscribe.

<Note>
  The paid newsletter is part of the **Growth** plan and above. You can read
  its settings and numbers on any plan; turning it on and sending paid posts
  need Growth.
</Note>

## Set it up

<Steps>
  <Step title="Create the membership offers">
    In **Subscriptions**, create the offer readers pay for: a monthly price, a
    yearly price, or both (for example $9/month and $90/year). They are normal
    subscription offers, so checkout, receipts and the subscriber portal work
    as usual.
  </Step>

  <Step title="Turn on the paid newsletter">
    Go to **Posts → Paid newsletter**, pick the monthly and/or yearly offer,
    give the newsletter a name, and switch it on.
  </Step>

  <Step title="Write a paid post">
    In the post editor, drag the **Paywall** block to where the free preview
    should end. In the **Audience** step, choose **Paid subscribers only**.
  </Step>
</Steps>

## Who is a paid subscriber

Anyone with a live subscription to one of the membership offers — active, in
a free trial, in a payment retry window, or paused — is a paid subscriber.
Paid subscribers carry the `paid` tag in **Subscribers**.

The tag updates on its own:

* when someone subscribes, renews, fails a payment, pauses, cancels or is
  refunded;
* when you change the membership offers;
* right before every paid post is sent.

A new paid subscriber who wasn't on your list yet is added to it (they paid
for the newsletter). Someone who unsubscribed stays unsubscribed.

## Post audiences

| Audience | Paid subscribers get | Free subscribers get |
| - | - | - |
| **Everyone** | The whole post | The whole post |
| **Free subscribers** | Nothing | The whole post |
| **Paid subscribers only** | The whole post | The preview above the paywall and a **Subscribe to keep reading** button (or nothing, if you turn off previews) |

The audience works on top of who you already send to (everyone, a product's
buyers, a tag, or hand-picked people).

<Tip>
  No paywall block in a paid post? Free subscribers get only the subject, the
  preview line and the subscribe button — never the body.
</Tip>

In your own HTML (for example through the API), mark the paywall with
`{{paywall}}` or any element with a `data-pf-paywall` attribute.

## The public archive

Turn on **Show on your newsletter page** for a post and, once it is sent, it
appears on `https://<your-subdomain>.pocketsflow.com/newsletter`.

* Everyone and free posts are readable by anyone.
* Paid posts show the preview and a paywall with your subscribe buttons. The
  rest of the post is never sent to the reader's browser.
* Paid subscribers enter their email on the paywall and get a **reading
  link**. It opens every paid post on that browser for 30 days, and stops
  working as soon as their subscription ends.
* If your plan drops below Growth, the archive stays up **read-only** (the
  same rule as memberships): your current paid subscribers keep reading
  every post with their link, the subscribe buttons are hidden, and no new
  paid post can be sent until you upgrade again.

## Your numbers

**Posts → Paid newsletter** shows:

* **Paid subscribers** — and how many joined or canceled in the last 30 days.
* **MRR** — monthly recurring revenue from the membership (yearly plans count
  one twelfth).
* **Free → paid** — paid subscribers out of everyone on your list.
* **Free subscribers** — the people your next upgrade CTA reaches.

## API and AI agents

Everything above is in the public API and the MCP server: see
[Paid newsletter API](/api-reference/paid-newsletter).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.