beehiiv

Rekomi's beehiiv connection does two jobs, and each has its own switch on the integration page. Sync affiliates into beehiiv adds every approved affiliate as a subscriber to your publication. Credit sales through beehiiv credits paid subscriptions to the affiliate whose link brought the reader, using the record beehiiv itself keeps of how each subscriber arrived. Both switches are on by default.

What this connection does and does not do. It syncs affiliates into beehiiv, and it names the affiliate on sales that arrive through the Stripe account beehiiv created for your paid subscriptions. It does not record those sales on its own: that Stripe account must be connected under Setup > Connect payment gateway, which is where the sale itself comes from. It cannot credit a reader who was already on your list before they clicked an affiliate link, because beehiiv writes the arrival record once, at signup (see the limits below).

Credit sales through beehiiv

How it works

1. Every affiliate link Rekomi hands out for your campaign carries two extra parameters: utm_source=rekomi and utm_campaign set to that affiliate's link slug. For example: https://newsletter.example.com?via=jane&utm_source=rekomi&utm_campaign=jane. Existing links your affiliates already shared keep working; Rekomi only adds the tags to the links it generates.
2. When a reader lands on your beehiiv site from that link and subscribes, beehiiv stores those two values on the new subscriber. beehiiv writes them once, at signup, and never overwrites them.
3. When that subscriber later pays for a Premium subscription, Stripe tells Rekomi about the sale. Rekomi first tries everything it already knows (a coupon, checkout metadata, the customer's history, an email lead it recorded itself). Only when none of those names an affiliate does it ask beehiiv for the subscriber by email, read the stored tag, and credit the affiliate the tag names. The sale then shows in your dashboard like any other, with beehiiv as the source.
4. Nothing runs in the reader's browser for any of this. No script, no cookie banner, no tag manager.

What you need

• The Stripe account beehiiv created for paid subscriptions connected under Setup > Connect payment gateway. beehiiv sets that account up under your own Stripe login, separate from any other Stripe account you use, so make sure you pick that one in the Stripe consent screen. Without it, no sale reaches Rekomi and there is nothing to credit.
• The beehiiv connection on this page with Credit sales through beehiiv on. It is on from the moment you connect.

Nothing else. The optional click-stats tag in the beehiiv install guide adds click counts and a lead the moment a reader types an email, which also covers the readers described under limits below, but it is not needed for sales to credit.

The switch and the status line

Credit sales through beehiiv sits on the integration page next to Sync affiliates into beehiiv. Under it the page shows one plain sentence of status: whether Rekomi's last check of your publication succeeded and when it ran, and how many sales have been credited through beehiiv so far. Rekomi runs that check when you connect, so the page says whether things are ready straight away instead of waiting for the first sale. A subscriber is credited only when they joined within the window shown on the page (365 days by default, counted from the signup date beehiiv stores).

Turning the switch off stops the lookups, removes the two tags from your affiliates' links, and removes the signup alerts below. Nothing else about the connection changes; affiliate sync keeps running.

Check a subscriber's email

Under the sales block, Check a subscriber's email takes one address and tells you what beehiiv has stored for it: whether the person is a subscriber, whether the arrival tag names one of your affiliates, and whether a sale from that email would be credited, in one sentence. Use it to test without a support ticket: open an affiliate link, subscribe with a fresh address, then check that address here. Plus-addressed variants of one inbox (you+test@gmail.com and you@gmail.com) are tried as the same person.

Signup alerts

When the switch is on, Rekomi also registers a webhook on your publication so a new subscriber who arrived through an affiliate link shows up as a lead under that affiliate right away, before any sale. beehiiv offers webhooks on its Scale plan and above. On other plans the integration page shows one line under the sales status saying that signup alerts need Scale or above, and sales still credit; only the early lead is missing.

Readers who pay before they subscribe

beehiiv writes the tag only through a subscribe form. A reader who goes from an affiliate link straight to the upgrade page, enters their email in beehiiv's checkout box and pays is created without a tag, so the connection alone cannot credit that sale. Switch on the checkout door in the campaign's Tracking settings for those readers; the beehiiv install page walks through the two steps. Both paths run side by side: the connection credits subscribers, the door credits checkout-first buyers.

Limits, stated plainly

• beehiiv records the arrival once, at signup. A reader who was already on your free list before they clicked an affiliate link, and later upgrades, is not credited by this connection. For those readers the optional click-stats tag from the install guide still records a lead the moment they type their email on your site after the click, and that lead credits the sale by email match.
• Only beehiiv-hosted pages store the tag. A beehiiv subscribe form embedded on another website does not record the arrival unless beehiiv's own attribution script runs on that page.
• One-time digital products sold through the same Stripe account are not credited yet. Premium subscriptions credit today; one-time products on that account credit the same way once the Rekomi app for Stripe update is live. beehiiv Boost spend and the built-in Referral Program are separate beehiiv features that Rekomi never records (see the install guide for the three side by side).

Sync affiliates into beehiiv

What syncs

When an affiliate is approved (or, optionally, when they apply), Rekomi calls POST /v2/publications/{publicationId}/subscriptions with email, reactivate_existing: true, send_welcome_email: false.

beehiiv has no list-picker concept; subscribers are publication-wide.

Platform limitation: beehiiv's subscription API has no first/last name fields, so affiliates arrive as email-only subscribers. Rekomi does fill custom fields on each affiliate: Rekomi referral link, Rekomi referral slug, Rekomi campaign and Rekomi affiliate status, created on your publication on the first sync.

Finding your API key and publication ID

In beehiiv:

1. Settings → Integrations → API Keys.
2. Generate a new API key. Copy the key.
3. The same page shows your Publication ID (starts with pub_).

Connecting beehiiv in Rekomi

1. Go to Integrations in the dashboard sidebar.
2. Click the beehiiv card.
3. Paste your API key and publication ID. Click Connect.
4. Rekomi runs a test call against GET /v2/publications/{publicationId} to verify both, then checks that it can look subscribers up, so the sales status line is filled in immediately.

Tags

beehiiv has no first-class tags concept, so Rekomi writes no tags and ignores the tags array on subscribe. It does create custom fields on your publication on the first sync, Rekomi referral link, Rekomi referral slug, Rekomi campaign and Rekomi affiliate status, and fills them on every affiliate.

Referred customers and leads (optional)

Under Sync affiliates into beehiiv, turn on Sync referred customers and leads and every sale or lead Rekomi attributes to an affiliate is written to beehiiv as well, matched on email so existing contacts are updated, not duplicated. Sales credited through beehiiv by the lookup above are included. Each one carries:

• custom fields Rekomi referral link, Rekomi campaign, Rekomi referring affiliate, Rekomi referring affiliate code, Rekomi last event, Rekomi last sale amount, created on first use
• no tags (beehiiv has none); filter on Rekomi last event instead
• Affiliates synced by the section above also get Rekomi referral link, Rekomi referral slug, Rekomi campaign and Rekomi affiliate status in the same fields, so you can merge a partner's link into your emails. The referral link written here carries the same two tags as the links Rekomi shows affiliates.

Refunded, denied and fraud-quarantined conversions are never pushed, and imported historical conversions are skipped. It is off by default. Turning this on subscribes referred customers to your publication. Leave it off if you only want affiliates in beehiiv.

When sync fires

• Default: only Approved affiliates sync.
• Optional: turn on "Include applicants before approval" to also sync Pending.

Per-campaign overrides

Each campaign can override the account-level configuration. From a campaign's detail page, open the Settings tab and scroll to the CRM sync for this campaign section.

Per-affiliate sync visibility

Open any affiliate's detail page. The CRM sync panel shows the per-CRM status. Resync clears prior jobs and re-fires the sync.

Troubleshooting

• 404 on test, Publication ID is wrong or the API key can't see that publication.
• publication_id_invalid, Publication ID doesn't match the pub_* shape. Re-copy from Settings → Integrations.
• 429, beehiiv throttles at 180 req/min. The affiliate sync honors the RateLimit-Reset header. The sales lookup shares that budget: about one read per sale, with a short per-email cache so the same buyer is not read twice in a burst, and a read that gets a 429 is tried again after two minutes.
• A test purchase shows as a purchase but not as a credited sale, Use Check a subscriber's email with the exact address you bought with. If beehiiv has no subscriber for it, the reader paid before subscribing, or subscribed on a page that is not beehiiv-hosted. If the subscriber exists but carries no tag, they were on your list before the click (see limits). If the tag is there and the sale still did not credit, confirm the Stripe account connected under Setup is the one beehiiv bills through.
• Sync fails with 401/403 after working before, The API key was revoked. Rekomi marks the integration "action needed" and emails you a reconnect prompt once per breakage. Reconnect with a fresh key, then use Resync all on the Failed tile of the integration page.

Disconnecting

From the beehiiv connect page, click Disconnect. Integration row + per-campaign overrides are deleted, and the signup webhook is removed from your publication. Sync history is preserved.

---

See the beehiiv integration overview on the marketing site for use-cases, persona fit, and unique automation patterns.