Lede Docs

Customer Sync Between Lede and Beehiiv

Overview

The Lede platform automatically keeps subscriber data in sync with Beehiiv. This sync is bidirectional: changes made through your website or the Publisher App are pushed to Beehiiv, and changes made in Beehiiv (such as through subscriber preferences) are pulled back into Lede. This article explains when and how this sync occurs.

When Are Subscribers Synced to Beehiiv?

Subscriber data is synced from Lede to Beehiiv in the following situations:

1. New Subscriber Registration

When a new subscriber registers on your site and verifies their email address, they are automatically synced to Beehiiv. As part of this process:

By default, this sync waits for email verification (double opt-in). If you disable the “Require email verification before syncing new registrants” setting under Login & Profile Options in the Publisher App, new registrants are synced to Beehiiv immediately at signup instead.

  • The subscriber is created in your Beehiiv publication.
  • They are opted into your default newsletter.
  • They are added to the Beehiiv list for each newsletter they are opted into, and their custom fields (account status, subscription details) are set.

2. Email Verification

If a subscriber was created but has not yet verified their email, the sync is triggered when they complete verification. Unverified subscribers are not synced to Beehiiv unless double opt-in is disabled in your settings.

3. Newsletter Opt-In or Opt-Out

Whenever a subscriber opts into or out of a newsletter on your site, or you change their newsletters in the Publisher App, the change is immediately synced to Beehiiv by adding them to or removing them from that newsletter’s list.

4. Subscription Changes

When a subscriber purchases, upgrades, renews, or cancels a paid subscription, the platform syncs updated custom fields (such as product name, billing interval, and expiration date) and updates the subscriber’s Beehiiv tier. See Paid Subscriptions and Beehiiv Tiers for more details.

5. Subscriber Login

Each time a subscriber logs in, the platform updates their last_login and ever_logged_in custom fields in Beehiiv. Additionally, the login event triggers a reverse sync that pulls the subscriber’s current preferences from Beehiiv back into Lede. This ensures that any changes the subscriber made directly through Beehiiv’s preferences page are reflected on your site.

6. Reading Interests (Nightly)

Every night, Lede works out which categories, tags and authors each subscriber reads most on your site and syncs them to three Beehiiv custom fields: Content Categories, Content Tags and Content Authors. These fields are used for targeting segments by reading interest.

  • Each field holds up to five names, most-read first, based on the articles the subscriber has read in the last 90 days. A category, tag or author is included once they have read at least three of its articles.
  • Reading counts while the subscriber is logged in, and from a device they have logged in on.
  • The fields are updated only when a subscriber’s interests change. Subscribers who stop reading keep their last interests.
  • Only subscribers who already exist in Beehiiv are updated. This sync never adds anyone to your publication or changes their newsletters.
  • Lede manages these three fields. Edits made to them in Beehiiv are overwritten the next time the subscriber’s interests change.

Reverse Sync: Beehiiv to Lede

Changes made in Beehiiv are synced back to Lede through two mechanisms:

Webhooks

Beehiiv sends automatic notifications to the Lede platform when a subscriber joins or leaves one of your newsletter lists, or unsubscribes from your publication entirely. Lede processes these events and updates the subscriber’s newsletter preferences to match. For example, if a subscriber opts out of a newsletter on Beehiiv’s preferences page, Lede marks that newsletter as inactive for the subscriber. If they unsubscribe from all emails, Lede marks every newsletter as inactive.

Pausing a newsletter in Beehiiv does not change the subscriber’s preferences in Lede. The pause is temporary and Beehiiv resumes delivery on its own.

Login Activity

When a subscriber logs into your site, the platform records the login in Beehiiv by updating their Last Login and Ever Logged In custom fields. Logging in does not change newsletter preferences; those stay in sync through the Beehiiv webhooks described above as subscribers make changes.

Important Notes

  • Only active subscribers are synced to Beehiiv. By default they must also be verified (double opt-in); publishers who disable double opt-in sync unverified registrants as well. Inactive accounts are never synced.
  • Sync operations run in the background and do not slow down your website. There may be a brief delay (typically a few seconds) before changes appear in Beehiiv.
  • If a subscriber already exists in Beehiiv (for example, if they were imported via CSV before being added to Lede), the platform will detect and merge with their existing Beehiiv subscription rather than creating a duplicate.

Was this article helpful?