# Connect Beehiiv

You'll recognize newsletter readers on your website and save their answers to Beehiiv, so you can use what they tell you in your follow-up.

Available on the Grow, Scale, and Pro plans.

Connect Beehiiv to save what readers tell you to their subscriber records. When they arrive from an identifying newsletter link, you can also use their existing custom fields to personalize your website.

## Connect Beehiiv

You'll need permission to edit your RightMessage project, access to Beehiiv API V2 credentials, and your publication's ID. The ID starts with `pub_`.

A RightMessage project connects to one email platform or CRM at a time. Review where you use an existing connection before replacing it.

1. In Beehiiv's API settings, obtain an API V2 key and copy the ID of the publication you want to use.
2. In RightMessage, open your project's settings and select **Integration**.
3. Under **Email platforms & CRMs**, select **Beehiiv**.
4. Enter the key in **API Key** and the publication's ID in **Publication ID**.
5. Click **Connect**.

![Beehiiv connection controls in RightMessage, with no credentials entered](https://rightmessage.com/help/screens/integrations-beehiiv-connection.light.webp)

Check connection health in **Overview**. This reads the publication's custom-field catalog. You'll test subscriber lookup and saved answers below. Use a test subscriber from the connected publication, since the connection only accesses that publication. If you change credentials, click **Save Changes**.

[Install the RightMessage snippet](https://rightmessage.com/help/everything-you-need-to-know-about-your-rightmessage-tracking-script) on the website you want to personalize. Connecting Beehiiv doesn't install the snippet on Beehiiv-hosted pages or give you script access where your website platform doesn't allow it.

## Recognize subscribers from email links

Add Beehiiv's email merge tag to the `email` parameter on your website links. For example, a link to [WorkForge](https://workforge.rightmessage.com) could be:

```text
https://workforge.rightmessage.com/solutions.html?email={{email}}
```

Use your own page URL, then test it:

1. Edit a newsletter link to a page containing the RightMessage snippet.
2. Append `?email={{email}}`, or `&email={{email}}` if the URL already has query parameters. Put it before any `#` fragment.
3. Send to a test subscriber and inspect the delivered link. `{{email}}` must become their email. Make sure it's URL-encoded, especially for addresses containing `+`.
4. Open the link in a fresh browser session. RightMessage looks up the subscriber's API subscription ID in the connected publication.

Beehiiv documents the double-brace `{{email}}` merge tag in its [reserved fields guide](https://www.beehiiv.com/support/article/7606088263191). Don't copy the single-brace `{email}` syntax.

### If you use subscription IDs in links

RightMessage also accepts `rm_bh`, but its value must be the API subscription ID, not an email address. Beehiiv's `{{api_subscription_id}}` tag supplies it:

```text
https://workforge.rightmessage.com/solutions.html?rm_bh={{api_subscription_id}}
```

Use one identification method for your test. Don't substitute another Beehiiv subscriber or subscription identifier for the API subscription ID. An explicit `rm_bh` value takes precedence over email lookup.

The `email` parameter works when RightMessage has no remembered subscriber ID. Use a fresh browser session to test a different subscriber. Keep identifying links private, since a forwarded link can identify its original recipient.

A configured RightMessage Email question or form can identify someone too. An anonymous visit doesn't identify a person just because they subscribe to your newsletter. Another browser or device needs its own identification.

## Choose what to sync

Use **Custom Field** mapping for choice answers and segment groups. Select a field that exists in the connected publication, then map values it accepts. Typed answers can also write to configured custom fields.

RightMessage recognizes string, number, boolean, and date fields. Integer and double fields appear as numbers, datetime fields as dates, and list fields as text rather than a list editor. Field and automation catalogs load in pages of 100 and continue through the available cursors. That's a page size, not a total limit.

The connection reads the identified subscriber's custom fields. There's no separate native first-name or phone-field catalog, so save those answers in custom fields. It doesn't read or sync tags, list membership, event history, or purchase history, and it has no outgoing event action. Beehiiv's segments aren't automatically imported as RightMessage segments.

### Add new subscribers to your publication

For an Email question, choose **Create/Update contact** under **Contact action**. A lead-generation form can also create or update the subscription. You don't need another list or form destination. The connected **Publication ID** supplies it.

Configure consent for your signup. Collecting an email or looking up an existing subscriber isn't permission to subscribe them.

> **Check consent before subscribing someone**
>
> RightMessage updates an existing subscription when it finds one. When creating a subscription, it sends `reactivate_existing=true` to Beehiiv. Don't use a signup action to re-enroll someone without their consent. Test previously unsubscribed contacts separately.

Automation enrollment is a separate action you configure. The destination automation needs an **Add by API** trigger. Saving a mapped answer doesn't enroll someone by itself.

Follow [Map answers to contact fields and tags](https://rightmessage.com/help/synchronizing-contact-data-with-your-email-platform-or-crm) to map your questions, then publish the changes you want visitors to use.

## Check the connection

1. Give an existing test subscriber a distinctive custom-field value in the connected publication.
2. Open their delivered newsletter link in a fresh browser session. Use RightMessage's on-site debugger to check the subscriber and field value.
3. Outside debugger mode, answer a mapped question on the live site. Check the value on that same Beehiiv subscription.
4. In another fresh session, submit a new test signup. Check that it appears in the intended publication, then check automation enrollment if you configured it.

The debugger blocks external writes, so use a live submission to test saved answers. When the right subscriber's data reaches your website and their answer reaches Beehiiv, the connection is working. If either part fails, follow [Verify an integration change](https://rightmessage.com/help/verify-an-integration-change).