Offer configuration stays visible
Use Offers to decide what Customer.io receives: product, price, buyer, checkout mode, invoice, and automation context.

Integration
Plandalf integrates with Customer.io as a email, marketing, website, sdk platform.
Product surfaces
Integrations work best when the checkout surface, payment state, invoice record, and post-purchase automation all point at the same commercial object. These product screens show the Plandalf controls that should be configured before Customer.io receives checkout, payment, tax, or workflow context.
Use Offers to decide what Customer.io receives: product, price, buyer, checkout mode, invoice, and automation context.
Before Customer.io enters the stack, operators still need checkout templates, products, prices, coupons, order bumps, upsells, and branded offer content they can inspect.
Customer.io should fit into the work after checkout: fulfilment, records, CRM updates, support context, webhooks, and sequences.
Customer.io can start the sale through a hosted checkout, embedded checkout, modal, inline flow, or buy button depending on the stack.
Builder paths
Use these stack guides when a builder needs the whole path: sales surface, Plandalf offer, payment handoff, automation, fulfilment, records, and downstream integrations.
Find full stack guides that pair Customer.io with checkout, payment, automation, fulfilment, records, and downstream integrations.
Use Offers to package products, prices, checkout pages, invoices, coupons, payment options, and follow-up context.
Use hosted checkout when Customer.io should hand the buyer to a branded Plandalf checkout page.
Use SDK checkout when Customer.io belongs inside an app, custom site, or API-first stack.
Route checkout events, purchase events, payment state, invoices, and customer context into another tool.
Turn a completed checkout into access, receipts, CRM updates, support context, and records.
Customer.io is an engagement platform for lifecycle and transactional messaging. Its Campaigns product supports HTTP Request actions natively and speaks JSON, making it one of the cleanest Plandalf enrolment bridges in this list.
{{ customer.email }} passes
straight into the <img src> query string.Setup templates
Copy-paste setups for the most common ways to wire Customer.io into Plandalf.
promo · email
Paste this <img> tag into a Code block in your Customer.io
campaign. {{ customer.email }} is Customer.io's Liquid attribute
reference — it substitutes at send time.
<img
src="{{ promo.countdown_url }}?ref={{ customer.email }}"
alt="Time remaining on this offer"
/>
promo · automation
POST, URL:
{{ promo.catch_url }}
application/json, body:
{"email": "{{ customer.email }}", "ref": "{{ customer.email }}"}
Automation graph
How Customer.io participates in Plandalf sequences: what events it exposes upward, and what actions Plandalf can perform on it.
Events Plandalf can subscribe to through webhooks, API work, checkout state, payment context, and connected integrations.
customer-io.subscriber_addedcustomer-io.automation_step_reachedcustomer-io.form_submittedcustomer-io.webhookThings Plandalf sequences can do after checkout, payment, invoice, customer, or deadline events.
customer-io.add_subscribercustomer-io.tagcustomer-io.send_emailcustomer-io.start_automationcustomer-io.custom_api_callEmbeddable surfaces: Plandalf countdown image and buy button HTML · Per-recipient countdown GIF with merge-tag substitution
trigger: stripe.payment_succeeded
actions:
- customer-io.add_subscriber:
list: paying-customers
tag: tier-${plan}
- plandalf.grant_entitlement: ${product_slug}Pair it with
Platforms whose roles complement Customer.io inside a Plandalf sequence.
Customer.io + ActiveCampaign
Capture a lead on ActiveCampaign, nurture it through Customer.io.
Customer.io + beehiiv
Capture a lead on beehiiv, nurture it through Customer.io.
Customer.io + Kit (ConvertKit)
Capture a lead on Kit (ConvertKit), nurture it through Customer.io.
Customer.io + Drip
Capture a lead on Drip, nurture it through Customer.io.
Customer.io + Flodesk
Capture a lead on Flodesk, nurture it through Customer.io.
Customer.io + Klaviyo
Capture a lead on Klaviyo, nurture it through Customer.io.
Integration methods
Each method below is the minimum viable setup. Pick the one closest to how you already use Customer.io with checkout, payments, invoices, webhooks, API work, SDK checkout, and integrations.
Drop the Plandalf embed script into a Customer.io HTML block and tag any element with `data-plandalf-present` to open the configured flow on click.
<script src="https://cdn.plandalf.com/embed.js" async></script>
<button data-plandalf-present="offer_abc123">
Buy now
</button>Add an HTML block to any Customer.io email and paste the Plandalf countdown URL. Customer.io's merge tag `{{customer.email}}` substitutes per recipient so each subscriber sees a timer pegged to their own deadline.
<img
src="https://cdn.plandalf.com/timers/{TIMER_ID}.gif?ref={{customer.email}}"
alt="Time remaining on this offer"
width="600"
height="120"
/>Point a Customer.io form's webhook / POST URL at Plandalf's intake endpoint and every submission starts whatever sequence you've mapped to it.
curl -X POST https://api.plandalf.com/v1/intake/customer-io \
-H "Content-Type: application/json" \
-d '{"email": "{{ form.email }}", "source": "customer-io"}'Inside Customer.io's automation builder, add a Webhook step that POSTs the contact to a Plandalf sequence catch URL. Use this to mirror Customer.io journey logic into Plandalf without re-building the segmentation.
{
"email": "{{ contact.email }}",
"sequence": "post-signup-onboarding",
"source": "customer-io"
}For anything not covered by a native trigger, configure a Customer.io webhook to POST to Plandalf. The payload is forwarded into the sequence as `${event}`.
curl -X POST https://api.plandalf.com/v1/webhooks/customer-io \
-H "Authorization: Bearer $PLANDALF_API_KEY" \
-H "Content-Type: application/json" \
-d @event.jsonFAQ
Plandalf itself is free to connect. Customer.io's native webhook step is on its paid tiers — on the free plan, route the trigger through Zapier instead, which still works end-to-end.
Under 10 minutes. OAuth (or paste an API key), pick the lists/segments you care about, and you're live. No code unless you want it.
Yes. Disconnecting only revokes the credentials — historical events Plandalf fired stay in your sequence logs, and Customer.io's own records are untouched. You can reconnect any time and resume from the last seen event.
Plandalf stores the Customer.io contact ID and the events Plandalf fired against that contact. Email content stays in Customer.io; Plandalf doesn't mirror your audience or newsletter archive.
Use the generic `customer-io.custom_api_call` action or the inbound `customer-io.webhook` trigger. Anything Customer.io's REST API can do, a Plandalf sequence can drive.
Plandalf respects Customer.io's API rate limits and backs off on 429s. For very high-volume use cases, ask about a dedicated worker pool.
Customer.io's homepage at https://customer.io links to their developer docs. For Plandalf-side questions about the Customer.io integration, see the Plandalf docs.
Sequence
Checkout started to abandonment recovery
Recover a checkout that opened but did not complete by sending the buyer and offer context to the email or automation tool.
Sequence
Price plan changed lifecycle
Route product, price, plan, and subscription changes into lifecycle messaging and internal records.