The offer record connects the stack
Use Offers to define the product, price, checkout mode, invoice, and automation context before Customer.io and beehiiv receive events.
Integration pair
Customer.io + beehiiv
Use Customer.io and beehiiv together with Plandalf as the layer that ties checkout, payments, invoices, integrations, and lifecycle automation together.
Common setup
Most teams use Customer.io as their email layer and beehiiv as their email layer, with Plandalf in the middle handling the checkout, Offers, invoices, integrations, and the events that fire after a purchase.
See Customer.io and beehiiv docs for connection details.
Product surfaces behind this integration
This legacy integration URL now points builders toward the same product reality as the canonical app-pair guide: Offers, payment options, invoices, integrations, Automations, API docs, and webhooks.
Purchase automation carries the details
Automations and webhooks let Customer.io and beehiiv receive buyer, product, payment, invoice, coupon, and deadline context.
Integration settings remain visible
Confirm Stripe, PayPal, TaxJar, Avalara, and test-mode routing before sending the Customer.io and beehiiv path live.
Use the richer guide from here
Keep moving from this page into canonical integration docs, platform pages, stack guides, and sequence recipes so every Customer.io or beehiiv mention has a useful next step.
Open canonical app-pair guide Use the richer Customer.io and beehiiv implementation guide. Customer.io platform page Roles, capabilities, and setup notes for Customer.io. beehiiv platform page Roles, capabilities, and setup notes for beehiiv. API-first stack SDK checkout, API keys, webhooks, payment processors, and invoices.