Lede Docs

How Newsletters Are Represented in Beehiiv

Overview

Beehiiv is the email service provider that powers newsletter delivery for the Lede platform. Each newsletter that you manage in the Publisher App is represented in Beehiiv as a custom field on each subscriber’s profile. This article explains how that mapping works.

Custom Fields for Newsletters

For each newsletter you create in the Publisher App, a corresponding boolean custom field is automatically created in your Beehiiv publication. The field follows this naming convention:

Newsletter: [Display Name]

For example, if you have a newsletter with the display name “Daily Briefing,” the custom field in Beehiiv will be named Newsletter: Daily Briefing.

The value of this field is a simple true or false:

  • true — the subscriber is opted into the newsletter.
  • false — the subscriber is opted out of the newsletter.

These fields are created automatically when your publication is first set up in Beehiiv, and whenever you add a new newsletter through the Publisher App.

Other Custom Fields

In addition to newsletter subscription fields, the Lede platform also syncs a number of other subscriber data points to Beehiiv as custom fields. These include:

  • customer_status — the subscriber’s account status (e.g., active, verified).
  • product_name — the name of the subscriber’s current subscription product.
  • order_interval — whether the subscription is monthly or annual.
  • order_expiration — the expiration date of the current subscription.
  • order_canceled — whether the subscription has been canceled.
  • donor — whether the subscriber has made a donation.
  • last_login — the date and time of the subscriber’s most recent login.

These fields are useful for building segments in Beehiiv to target specific subscriber groups. See Sending to Newsletters: Segments in Beehiiv for more details.

How Field Matching Works

When the Lede platform syncs data to and from Beehiiv, field names are matched in a case-insensitive manner. This means that “Newsletter: Daily Briefing” and “newsletter: daily briefing” are treated as the same field. This prevents accidental duplication if field names vary slightly in capitalization.

Was this article helpful?