Lede Docs

Creating a New Newsletter

Overview

This article walks you through creating a new newsletter in the Publisher App. When you create a newsletter, the Lede platform automatically sets up the corresponding custom field in Beehiiv so that subscriber preferences are tracked and synced.

Step-by-Step: Creating a Newsletter

  1. Log in to your WordPress admin and navigate to the Publisher App.
  2. Click the Newsletter tab in the Publisher App.
  3. Click the Add button to open the new newsletter form.
  4. Fill in the following fields:
    • Name (required) — An internal identifier for the newsletter. This must be unique within your publication. Choose something short and descriptive (e.g., “daily-briefing” or “weekend-edition”).
    • Display Name (required) — The public-facing name that subscribers will see on your website and in Beehiiv (e.g., “Daily Briefing” or “Weekend Edition”). This is also used to name the corresponding custom field in Beehiiv as Newsletter: [Display Name].
    • Description (required) — A brief description of what the newsletter covers. This may be visible to subscribers, so write it as a reader-friendly summary.
    • Active — Toggle this on to make the newsletter available for subscriptions. If left off, the newsletter will show as “inactive” on subscriber account pages and will not accept new opt-ins.
    • Premium — Toggle this on if the newsletter should only be available to paid subscribers. Premium newsletters are automatically enabled for subscribers who purchase a subscription with the appropriate entitlement.
    • List Provider (required) — Select Beehiiv from the dropdown. (If your publication uses Subtext for SMS, that option is also available.)
  5. Name (required) — An internal identifier for the newsletter. This must be unique within your publication. Choose something short and descriptive (e.g., “daily-briefing” or “weekend-edition”).
  6. Display Name (required) — The public-facing name that subscribers will see on your website and in Beehiiv (e.g., “Daily Briefing” or “Weekend Edition”). This is also used to name the corresponding custom field in Beehiiv as Newsletter: [Display Name].
  7. Description (required) — A brief description of what the newsletter covers. This may be visible to subscribers, so write it as a reader-friendly summary.
  8. Active — Toggle this on to make the newsletter available for subscriptions. If left off, the newsletter will show as “inactive” on subscriber account pages and will not accept new opt-ins.
  9. Premium — Toggle this on if the newsletter should only be available to paid subscribers. Premium newsletters are automatically enabled for subscribers who purchase a subscription with the appropriate entitlement.
  10. List Provider (required) — Select Beehiiv from the dropdown. (If your publication uses Subtext for SMS, that option is also available.)
  11. Click Save.

After saving, the platform will automatically create the corresponding Newsletter: [Display Name] custom field in your Beehiiv publication.

After Creating a Newsletter

Once your newsletter is created, there are a few additional steps to consider:

Create a Segment in Beehiiv

To send emails to subscribers of this newsletter, you will need to create a segment in Beehiiv that filters by the new custom field. See Sending to Newsletters: Segments in Beehiiv for instructions.

Enable on the Preferences Page

If you want subscribers to be able to opt in or out of this newsletter through Beehiiv’s built-in preferences page, you will need to configure the custom field to be visible there. See Subscriber Preferences and Unsubscribe Requests for details.

Set as Default (Optional)

If this should be the newsletter that new subscribers are automatically opted into upon registration, contact Lede support to set it as your publication’s default newsletter.

Editing a Newsletter

To edit an existing newsletter, click on it in the Newsletter list view. You can update any of the fields described above. Note that if you change the Display Name, the corresponding custom field in Beehiiv will be updated to match the new name.

Was this article helpful?