sales-beehiiv

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Beehiiv Platform Help

Beehiiv平台帮助

Step 1 — Gather context

步骤1 — 收集上下文

references/learnings.md

exists, read it first for accumulated platform knowledge.

Ask the user:

What area of beehiiv do you need help with?
- A) Publishing — editor, templates, scheduling, content
- B) Audience growth — Boosts, referral program, recommendations, subscribe forms
- C) Monetization — Ad Network, paid subscriptions, sponsorship storefront, digital products
- D) Automations — email flows, segments, triggers
- E) Website — builder, custom domains, SEO, landing pages
- F) Analytics — campaign stats, subscriber metrics, A/B testing
- G) Integrations — Zapier, Make, webhooks, API
- H) Account — pricing, plan features, billing, teams
- I) Something else — describe it
What plan are you on?
- A) Launch (free — up to 2,500 subscribers)
- B) Scale ($43/mo — up to 100K subscribers)
- C) Max ($96/mo — up to 100K subscribers)
- D) Enterprise (custom — 100K+ subscribers)
- E) Not sure
What are you trying to accomplish? (describe your specific goal or question)

Skip-ahead rule: if the user's prompt already contains enough context, skip to Step 2.

如果

references/learnings.md

文件存在，请先阅读该文件以获取积累的平台知识。

向用户询问：

你需要Beehiiv哪个领域的帮助？
- A) 发布 — 编辑器、模板、排期、内容
- B) 受众增长 — Boosts、推荐计划、推荐内容、订阅表单
- C) 变现 — 广告网络、付费订阅、赞助商店、数字产品
- D) 自动化 — 邮件流、细分群体、触发条件
- E) 网站 — 构建器、自定义域名、SEO、着陆页
- F) 分析 — 活动统计、订阅者指标、A/B测试
- G) 集成 — Zapier、Make、webhooks、API
- H) 账户 — 定价、计划功能、账单、团队
- I) 其他 — 请描述
你使用的是哪个套餐？
- A) Launch（免费版 — 最多2500名订阅者）
- B) Scale（每月43美元 — 最多10万名订阅者）
- C) Max（每月96美元 — 最多10万名订阅者）
- D) Enterprise（定制版 — 10万名以上订阅者）
- E) 不确定
你想要达成什么目标？（描述你的具体目标或问题）

跳过规则：如果用户的提示已经包含足够的上下文，直接进入步骤2。

Step 2 — Route or answer directly

步骤2 — 转介或直接解答

If the request maps to a strategy skill, route:

Newsletter monetization strategy → "This is a monetization strategy question — run:
```
/sales-newsletter {your question}
```
"
Growing subscriber list strategy → "This is an audience growth question — run:
```
/sales-audience-growth {your question}
```
"
Email marketing strategy (sequences, segmentation) → "This is an email marketing question — run:
```
/sales-email-marketing {your question}
```
"
Email deliverability / SPF / DKIM → "This is a deliverability question — run:
```
/sales-deliverability {your question}
```
"
Selling digital products → "This is a digital products question — run:
```
/sales-digital-products {your question}
```
"

If the request is beehiiv-specific (platform config, feature questions, troubleshooting), continue to Step 3.

如果请求属于策略类技能，进行转介：

新闻通讯变现策略 → "这是一个变现策略问题，请运行：
```
/sales-newsletter {你的问题}
```
"
订阅者列表增长策略 → "这是一个受众增长问题，请运行：
```
/sales-audience-growth {你的问题}
```
"
邮件营销策略（序列、细分） → "这是一个邮件营销问题，请运行：
```
/sales-email-marketing {你的问题}
```
"
邮件送达率 / SPF / DKIM → "这是一个送达率问题，请运行：
```
/sales-deliverability {你的问题}
```
"
销售数字产品 → "这是一个数字产品问题，请运行：
```
/sales-digital-products {你的问题}
```
"

如果请求是Beehiiv平台特有的（平台配置、功能问题、故障排查），继续步骤3。

Step 3 — Beehiiv platform reference

步骤3 — Beehiiv平台参考资料

Read
references/platform-guide.md
for the full platform reference — modules, pricing, integrations, data model, workflows.

Answer the user's question using only the relevant section. Don't dump the full reference.

If the question involves the API, also read
references/beehiiv-api-reference.md
for endpoint details.

**阅读

references/platform-guide.md

**获取完整的平台参考资料——模块、定价、集成、数据模型、工作流。

仅使用相关部分解答用户的问题，不要输出完整的参考资料。

如果问题涉及API，还需**阅读

references/beehiiv-api-reference.md

**获取端点详情。

Step 4 — Actionable guidance

步骤4 — 可落地的指导

You no longer need the platform guide — focus on the user's specific situation.

Provide step-by-step guidance tailored to their plan tier:

Check if the feature they need is available on their plan (many features are Scale+ only)
If they're on Launch and need a paid feature, explain the upgrade path
For API questions, provide example requests with their publication context
For growth questions, recommend the beehiiv-native approach first, then third-party alternatives

If you discover a gotcha, workaround, or tip not covered in

references/learnings.md

, append it there.

此时无需再查阅平台指南——专注于用户的具体情况。

根据用户的套餐层级提供分步指导：

检查用户需要的功能是否在其套餐中可用（许多功能仅Scale及以上套餐支持）
如果用户使用Launch免费版但需要付费功能，说明升级路径
对于API问题，结合用户的发布上下文提供示例请求
对于增长类问题，优先推荐Beehiiv原生方案，再提供第三方替代方案

如果发现

references/learnings.md

中未涵盖的陷阱、变通方法或技巧，将其添加到该文件中。

Gotchas

注意事项

Best-effort from research — review these, especially items about plan-gated features and integration gotchas that may be outdated.

Shared IP deliverability — all beehiiv users share sending infrastructure. If deliverability drops, it may not be your fault. Custom domains help, but dedicated IPs require Enterprise plan.
Automations are limited — email automations can only look back 30 days. You can't import complex flows from other platforms that use longer time windows.
Scale plan required for monetization — Ad Network, Boosts, paid subscriptions, and digital products all require Scale ($43/mo) or higher. The free Launch plan has no monetization features.
Webhooks require Scale plan — can't receive real-time events on the free plan.
Send API is Enterprise-only — programmatic email sending requires the Enterprise plan. The regular API (subscriptions, posts, publications) is available on all plans.
Post creation API is beta and Enterprise-only — POST /posts endpoint requires Enterprise plan access.
Subscriber pricing scales steeply — Scale and Max both cap at 100K subscribers. Beyond that, you must upgrade to Enterprise (custom pricing). The jump can be significant.
Open rate concerns — some users report beehiiv open rates appear higher than expected compared to other platforms. Use click rates as a more reliable engagement metric.

基于研究的最佳实践——请仔细查看这些内容，尤其是关于套餐限制功能和集成陷阱的可能过时信息。

共享IP送达率——所有Beehiiv用户共享发送基础设施。如果送达率下降，可能并非你的问题。自定义域名有所帮助，但专属IP需要Enterprise套餐。
自动化功能受限——邮件自动化只能回溯30天的数据。你无法从其他平台导入使用更长时间窗口的复杂流程。
变现功能需Scale套餐——广告网络、Boosts、付费订阅和数字产品均需要Scale（每月43美元）或更高套餐。免费Launch版无任何变现功能。
Webhooks需Scale套餐——免费版无法接收实时事件。
发送API仅限Enterprise版——程序化邮件发送需要Enterprise套餐。常规API（订阅、帖子、发布）所有套餐均可用。
帖子创建API处于测试阶段且仅限Enterprise版——POST /posts端点需要Enterprise套餐权限。
订阅者定价涨幅较大——Scale和Max套餐均限制最多10万名订阅者。超过该数量必须升级到Enterprise版（定制定价），费用涨幅可能很大。
打开率问题——部分用户反馈Beehiiv的打开率看起来比其他平台高。建议将点击率作为更可靠的参与度指标。

Related skills

Examples

示例

Example 1: Monetization not working

示例1：变现功能无效

User says: "I set up the ad network on beehiiv but I'm barely making any money" Skill does: Checks plan tier (must be Scale+), reviews subscriber count and engagement metrics, explains how ad network revenue scales with list size and niche, suggests optimizing content for higher engagement, recommends trying Boosts alongside ads, and provides realistic revenue benchmarks Result: User understands ad network expectations and has concrete steps to increase revenue

用户提问："我在Beehiiv上设置了广告网络，但几乎赚不到钱" 技能处理：检查套餐层级（必须是Scale及以上），查看订阅者数量和参与度指标，解释广告网络收入如何随列表规模和细分领域增长，建议优化内容以提高参与度，推荐搭配Boosts和广告一起使用，并提供实际的收入基准结果：用户了解广告网络的预期，并获得提高收入的具体步骤

Example 2: Migration from another platform

示例2：从其他平台迁移

User says: "I'm moving from Substack to beehiiv — what do I need to know?" Skill does: Walks through subscriber import process, content migration, custom domain setup, differences in monetization (Substack 10% fee vs beehiiv 0%), feature comparison (automations, referral program, analytics), and gotchas (automation limitations, plan-gated features) Result: User has a complete migration plan with platform-specific considerations

用户提问："我要从Substack迁移到Beehiiv——需要注意什么？" 技能处理：引导完成订阅者导入流程、内容迁移、自定义域名设置，对比变现差异（Substack收取10%手续费vs Beehiiv 0%），功能对比（自动化、推荐计划、分析），以及注意事项（自动化限制、套餐专属功能）结果：用户获得包含平台特定注意事项的完整迁移计划

Example 3: API integration

示例3：API集成

User says: "I want to automatically create subscribers in beehiiv when someone fills out a Typeform" Skill does: Explains the POST /subscriptions endpoint, provides example request with required fields, shows webhook/Zapier alternatives for no-code, notes that API access is available on all plans, and covers custom fields for additional data Result: User has working API integration code or a Zapier workflow

用户提问："我想在有人填写Typeform时自动在Beehiiv中创建订阅者" 技能处理：解释POST /subscriptions端点，提供包含必填字段的示例请求，展示无代码的webhook/Zapier替代方案，说明所有套餐均支持API访问，并介绍用于附加数据的自定义字段结果：用户获得可用的API集成代码或Zapier工作流

Troubleshooting

故障排查

Emails going to spam

邮件进入垃圾邮件

Symptom: Subscribers report newsletters landing in spam/promotions Cause: Shared IP infrastructure, missing custom domain, low engagement dragging reputation Solution: Set up a custom sending domain. Ask engaged subscribers to move emails to primary inbox and reply. Clean inactive subscribers regularly. If persistent, contact beehiiv support — it may be a platform-wide issue. Dedicated IPs require Enterprise plan.

症状：订阅者反馈新闻通讯进入垃圾邮件/促销邮件文件夹原因：共享IP基础设施、缺少自定义域名、低参与度影响信誉 解决方案：设置自定义发送域名。请求活跃订阅者将邮件移至主收件箱并回复。定期清理不活跃的订阅者。如果问题持续，联系Beehiiv支持——可能是平台范围的问题。专属IP需要Enterprise套餐。

Paid subscriptions not working

付费订阅无法正常工作

Symptom: Stripe payments failing, subscribers can't upgrade, paywall not showing Cause: Stripe connection issues, plan limitations, or misconfigured premium tiers Solution: Verify Stripe is properly connected (Settings > Payments). Check you're on Scale+ plan. Ensure premium tier is configured with correct pricing. Test in incognito mode. Check beehiiv support article on troubleshooting paid subscriptions.

症状：Stripe支付失败、订阅者无法升级、付费墙未显示原因：Stripe连接问题、套餐限制或高级层级配置错误 解决方案：验证Stripe是否正确连接（设置 > 支付）。检查是否使用Scale及以上套餐。确保高级层级配置了正确的定价。在隐身模式下测试。查看Beehiiv关于付费订阅故障排查的支持文章。