Customer.io
Behavioral messaging triggered by what users actually do.
The Customer.io Webflow integration turns your site's native forms into a behavioral messaging engine. Each submission identifies a person, captures an event, and can trigger a journey across email, SMS, push, and in-app channels — without middleware like Zapier. For SaaS and product-led growth sites where the right message depends on what a user actually did, this direct connection is the main reason to choose Customer.io Webflow integration over a simpler broadcast tool.
What Customer.io does that Mailchimp can't
- Event-driven journeys, not list broadcasts. Any product event — a form submit, a feature click, a plan change — can kick off a multi-branch workflow with waits, conditions, and splits, instead of Mailchimp's list-and-segment model.
- True multi-channel orchestration. Email, SMS, push, in-app, WhatsApp, and LINE sit inside one builder, so a single journey can escalate from email to SMS based on behavior.
- Identify and event model. A Webflow form submit runs an identify call that creates or updates a profile, then logs a typed event you can trigger on, filter by, or branch around.
- Custom objects and attributes. Beyond flat profiles, you can model accounts, companies, and custom objects, which Mailchimp's audience-plus-merge-field structure cannot represent.
- Built for SaaS and PLG. Developer-first APIs, a data-warehouse sync, and ad-audience destinations make it the default for product teams that need messaging tied to app state.
- Granular segmentation and an AI segment builder. Build segments from any combination of event history and attributes, with AI-assisted suggestions that Mailchimp's rule sets do not match.
How Customer.io's Webflow forms connection works
The connection rests on a small but important distinction: Customer.io provides two separate JavaScript snippets, and the forms one is mandatory. A site-wide tracking snippet logs page views and custom events for known visitors, but it cannot capture form submissions. The custom-forms snippet is the one that turns a Webflow form into a Customer.io event.
The flow is an identify-plus-event model. When a visitor submits your form, the snippet sends an identify call containing the mapped attributes — first name, email, company, anything you mapped — which creates the person if they are new or updates them if they exist. It then records the submission itself as an event, which any journey can listen for. Mapping is driven by the HTML name attribute on each field, and both attribute names and values are case-sensitive, so first_name and firstName are not interchangeable. The URL scanner in Customer.io reads your live page and suggests mappings, but scanning only configures the form — the snippet is still required to actually capture submissions.
How to connect Webflow forms to Customer.io
- In Customer.io, open Integrations → Directory, select the Forms integration, choose Custom, and click Connect form.
- Paste the Webflow page URL that hosts your form and click Scan for Forms. Customer.io reads the page and lists every form it finds.
- Pick the form you want and give it a recognizable name. If the same form appears on multiple pages, it counts as one form as long as the snippet is present everywhere.
- Map each Webflow field to a Customer.io attribute, keeping in mind that names are case-sensitive. Adjust any snake_case defaults to camelCase if your workspace expects that format.
- Click Set Up Form, then open the Settings tab of the Forms integration, choose JS Snippet, select your credentials, and copy it.
- In Webflow, open Pages, edit the target page's settings, scroll to Custom Code, and paste the snippet into either Inside
<head>tag or Before</body>tag — Customer.io confirms either placement works. - Save, publish the page, then submit a dummy entry to confirm the profile appears and the event fires your journey.
Customer.io vs. Mailchimp vs. Kit for Webflow
The three tools overlap on the surface — all three can capture a Webflow form submission — but they optimize for different buyers. Customer.io is a behavioral messaging platform for product teams. Mailchimp is a general-purpose marketing suite for small businesses. Kit (formerly ConvertKit) is a creator-focused tool built around subscribers, tags, and sequences.
| Dimension | Customer.io | Mailchimp | Kit |
|---|---|---|---|
| Best for | SaaS, PLG, event-driven messaging | Small-business broadcast marketing | Creators, newsletters, courses |
| Trigger model | Any event or attribute | List membership, segments | Tags and sequences |
| Channels | Email, SMS, push, in-app, WhatsApp | Email, ads, basic automations | Email (with paid add-ons) |
| Webflow connection | Custom-forms JS snippet | Form action URL POST | Form action URL or Zapier |
| Starting price | ~$100/mo (5,000 profiles) | ~$13/mo (Essentials) | Free to ~$29/mo (Creator) |
| Free tier | Startup program only | Yes (250 contacts) | Yes (10,000 subscribers) |
Pick Customer.io when messaging must react to behavior, Mailchimp when you need a cheap all-rounder, and Kit when your audience is subscribers rather than product users.
Best Customer.io + Webflow use cases
Welcome nurture from lead magnets
A visitor submits a Webflow form to download a guide. Customer.io identifies them, tags the source page, and drops them into a multi-step welcome sequence that branches on role or company size, then hands off to sales when engagement signals hit a threshold.
Demo-request follow-up
Demo and contact-sales forms trigger an immediate event. A journey sends a confirmation email, fires an SMS reminder ten minutes later, and notifies the account owner in Slack or your CRM — all within seconds of the submit, while the lead is still warm.
Behavioral onboarding
When a sign-up form captures product context (plan, role, goal), Customer.io builds an onboarding journey tailored to that profile. Each subsequent event from your app can advance, branch, or exit the user from the sequence, so messaging stays relevant rather than generic.
Re-engagement campaigns
A known profile revisits your site and submits a second form. Customer.io updates their attributes and enrolls them in a re-engagement flow that references their previous activity, dramatically improving reply rates over a cold blast.
Segmented product launches
New-feature announcements route only to profiles whose attributes match the target segment — by plan, industry, or activity. The same Webflow form can feed multiple segments, so one capture point powers many tailored launches.
Limitations to know
- A paid Webflow plan is required. Custom Code is unavailable on the free tier, so the snippet cannot be installed without a paid site plan.
- The forms snippet is distinct. The standard Customer.io JS snippet does not capture form submissions; you must install the custom-forms snippet specifically.
- Scanning does not capture. The URL scanner reads and maps fields but does not collect submissions — the snippet is mandatory for any data to flow.
- Pricing scales with profile count. Each uniquely identified person counts toward your limit, and you are billed on peak profiles during the cycle, so costs can climb faster than a flat-fee tool.
Related Webflow integrations
- Mailchimp — the broadcast-focused, lower-cost alternative for small businesses.
- Kit — the creator-focused alternative for newsletters and sequences.
- Zapier — a no-code bridge when the snippet is not an option.
- Blog: 20 Best Webflow Integrations to Use in 2026.
Frequently asked questions
Yes. Customer.io ships a dedicated Webflow connection inside its Forms integration. You paste a JavaScript snippet into your Webflow page's custom code, then point it at the forms you want to capture. Each submission identifies a person in Customer.io and can fire an event that triggers an email, SMS, push, or in-app journey. The integration is not a Webflow marketplace app; it runs through the custom-forms snippet rather than a one-click install.
Open Customer.io, go to Integrations, then Directory, then Forms, pick Custom, and click Connect form. Enter your Webflow page URL, click Scan for Forms, choose the form, and map each field to a Customer.io attribute, remembering names are case-sensitive. Copy the JS Snippet from the Forms Settings tab. In Webflow, open Pages, edit the page settings, scroll to Custom Code, and paste the snippet inside the head tag or before the closing body tag. Save, publish, and submit a test.
Pick Customer.io when messaging should react to product behavior and user events, because it triggers multi-branch journeys across email, SMS, push, and in-app from any event. Pick Mailchimp for broadcast newsletters, list-based segments, and a cheaper entry point with a small free tier. Customer.io is built for SaaS and product-led growth teams; Mailchimp suits traditional small-business marketing. Customer.io starts at $100 per month, while Mailchimp Essentials starts around $13 per month.
No. Customer.io has no permanent free plan. The Essentials tier starts at $100 per month for 5,000 profiles and up to one million emails, with overage around $0.009 per additional profile. Premium begins near $1,000 per month billed yearly and adds advanced reporting, higher limits, and AI features. A startup program offers a free year for companies that have raised under $10M, which is the closest thing to a no-cost entry point.
Yes, but only when you install a Customer.io JavaScript snippet. The forms snippet captures form submissions as events and identifies people by their submitted attributes. A separate site-wide tracking snippet can log page views and custom events for known visitors. Webflow alone does not send behavioral data to Customer.io; the snippet must be present on the page, and you must publish the page after adding it for tracking to take effect.
Launch faster with Webflow templates
Every template is CMS-ready and integration-friendly — connect your tools and ship.
