Customer.io integration
Customer.io sends email, push, SMS and in-app messages based on what people do. It has a documented Webflow forms integration; on Astro and Next.js we use its official @customerio/cdp-analytics-browser library for events and its Forms API from a server route. We load tracking after consent and send the events your campaigns need.
| Complexity | Medium |
|---|---|
| Method |
|
| Typical setup | 1 to 2 days |
| What we do | We connect forms and key site events, load tracking after consent, and agree event names with your lifecycle team. |
| Category | Forms and email |
Setup by platform
How we set up Customer.io
Framer
- Zapier or Make
- Embed
There is no Framer integration. A Framer form webhook relays to Customer.io’s Forms API through a small server function or automation, and the tracking snippet can go in custom code.
Webflow
- Native
- Embed
Customer.io’s Webflow forms integration scans the form and installs a forms snippet once, so submissions create or update people and fire events. It is separate from the site tracking snippet.
Astro
- API
@customerio/cdp-analytics-browser loaded after consent, with page() called on view transitions, and the Forms API from an endpoint for form submissions.
Next.js
- API
The same library, which Customer.io recommends over the snippet for Next.js, with manual page() calls on route changes and server-side identify after signup.
Use cases
What teams use it for
Onboarding from signup
A website signup starts the right onboarding emails, based on plan or use case.
Form-triggered campaigns
A demo or download form creates the person and starts a campaign automatically.
Behaviour-based follow-up
Visits to pricing or docs feed segments for timely, relevant emails.
Before you add it
What to watch out for
Consent and GDPR
Buffer until consent
The library sets an ajs_anonymous_id cookie. Customer.io offers a buffered load that waits for an explicit load call, and reset clears IDs if consent is withdrawn.
Data layer
Pick the region at signup
Accounts are in the US or EU (Belgium) region, chosen at creation, with no migration later. EU accounts use the EU CDN URL.
Data layer
Name events once
Campaigns trigger on exact event names. We write them down before launch so the site and campaigns stay in sync.
FAQ
Questions about Customer.io
Does Customer.io support Webflow forms?
Yes. Customer.io documents a Webflow forms setup: scan the form, install the forms snippet once, then test a submission.
Can we move Customer.io from the US to the EU later?
No. The region is chosen when the account is created and Customer.io doesn’t support moving between data centers.
Customer.io or Mailchimp?
Mailchimp suits newsletters and simple automations. Customer.io suits product-led teams that trigger messages from events in the site and app.
You've reached the end, so now…
Tell us what you’re building.
We’ll help you map the right scope, team, timeline, and next steps.
Book a call