Home/Connectors/Customer.io

Send Framer Form Signups to Customer.io

CRM & Sales • Native Edge Sync

Create and update people in Customer.io. Connect your native Framer forms to Customer.io in 30 seconds with zero client-side API key leaks.

Visual Field Mapping Pipeline
0 Code Required
Framer Form Inputs
name"Alex Rivera"
email"alex@co.com"
message"Inquiry..."
FramerSend VaultAPI Keys EncryptedZero-Retention • Spam Filter
Customer.io Destination
contact.email
sync_attributes
status200 OK
Ready to route • Copy 1 URL to your Framer form

Framer forms to Customer.io: what it does

Customer.io runs messaging off people and their attributes: segments decide who gets a campaign, and attributes fill in the personal details. FramerSend makes a Framer form a source of those people. Each submission is sent to the Track API as an identify call for one person, with every answer from the form stored as an attribute.

The person is addressed by an id field when the form has one, otherwise by the email address, so the same visitor submitting twice is sent to the same person. How Customer.io treats an email in that position depends on your workspace's identifier settings, so check them before going live. Your Site ID and API key stay on FramerSend's server, and EU workspaces are supported through the regional Track API host. The connector identifies people only; it does not send events, so build the follow-up on segments that use the attributes the form sets.

What gets created: A Customer.io person, created or updated with PUT /api/v1/customers/{identifier} on track.customer.io, or track-eu.customer.io for the EU region. The identifier is an id or userId field when the form has one, otherwise the email address.

What FramerSend sends to Customer.io

Framer form fieldCustomer.io
email (also Email, E-mail, work_email…)email attribute, and the identifier when there is no idTrimmed, with common domain typos such as gmail.con corrected first. Sent once as email, not also under the original field name.
id or userIdIdentifierUsed instead of the email when a field has exactly this name, for example a hidden field carrying your app's user ID.
name or full_namename, firstName, lastNameThe full name is kept in name and also split at the first space into firstName and lastName.
phone, company, message, city, state, countryLowercase attributes with those namesReplace the original field: a field called Phone number arrives once, as phone.
Every other fieldAttribute with the same nameSent under the Framer field name, or the name you set in Field Mapping.
No email and no idNot sentThe submission fails with a clear error instead of creating an anonymous person, so make the email field required.

Set up Framer to Customer.io step by step

  1. 1

    Copy your Track API credentials

    In your Customer.io workspace settings, find the Track API credentials and copy the Site ID and API Key. The Track API uses this pair; an App API key will not work here.

  2. 2

    Pick the region

    Leave Region empty for a US workspace. Enter eu if your workspace is hosted in the EU, and FramerSend sends everything to track-eu.customer.io.

  3. 3

    Connect Customer.io in the plugin or dashboard

    Search for Customer.io in the FramerSend plugin inside Framer, or use Dashboard → 2. Connect CRM. Paste the Site ID, API Key and region, then click Test. Test makes a read-only call to the Track API with your credentials and shows Customer.io connected when they are accepted.

  4. 4

    Name fields after your attributes

    Segments match attribute names exactly, so rename inputs in Dashboard → 3. Field Mapping to the names your segments use, for example "Which plan?" to plan.

  5. 5

    Paste the webhook URL into Framer

    In Framer, select the form, open Form → Send to → Add… → Webhook, paste the FramerSend webhook URL (https://www.framersend.com/api/submit/ followed by your form ID) and publish the site. Submit once and open the person in Customer.io to see the attributes.

Troubleshooting Framer to Customer.io

Customer.io rejected these credentials (HTTP 401). Check the key or token and its permissions.

Cause: Shown by Test when the Site ID and API Key do not form a valid Track API pair.

Fix: Copy both again from the Track API credentials. If they are correct, check that Region matches where the workspace is hosted.

Customer.io: could not reach the API (…). Check the domain or region.

Cause: Shown by Test when the request did not reach Customer.io at all.

Fix: Check the Region value (empty or eu) and try again.

Customer.io (HTTP …): …

Cause: Customer.io refused the identify call and its reply follows. Typical reasons are credentials that were rotated after the connection was saved, or an identifier your workspace settings do not accept.

Fix: Read the reply on the failed row in Dashboard → 4. Logs, update the connection or the identifier settings, then click Retry.

Customer.io: Email is required. The submission has no email or id field, so there is no person to create or update.

Cause: The visitor left the email empty and the form has no id field. It is treated as visitor input, so no alert email is sent.

Fix: Make the email input required in Framer.

Customer.io without Zapier vs with Zapier or Make

  • Every answer becomes an attribute. In a Zap you list each attribute you want to send. FramerSend sends the whole submission, so a new form question is available in segments without changing any automation.

  • No middle step. FramerSend makes the identify call directly from its server, and Customer.io's reply is logged with the submission.

  • No tasks per signup. Zapier counts each action as a task. FramerSend has no submission limit.

  • When an automation platform fits better. If a form should fire a Customer.io event to start an event-triggered campaign, you need another step for that. FramerSend identifies the person only.

Full comparison: FramerSend vs Zapier

How it works in 3 simple steps

Zero code or third-party plugins required

1

Connect

Authenticate Customer.io credentials in the FramerSend dashboard. We encrypt and store them securely.

2

Map Fields

Map your Framer form fields to Customer.io properties using our visual dropdown UI.

3

Go Live

Paste your webhook URL into your Framer form under Send to → Webhook and publish. Submissions flow automatically.

Every plan includes every connector

Get Customer.io Integration

Every plan includes Customer.io and 100+ other connectors. Pay monthly, yearly, or once. Try it free for 14 days, no card needed.

1 Site

For one Framer site

$5/ month
  • Customer.io and every other connector (100+)
  • 1 Framer site
  • Unlimited submissions & file uploads
  • API keys stay on our server, never in your site
  • Cancel anytime
Get 1 Site — $5/mo →

5 Sites

Popular

For freelancers and small studios

$12/ month
  • Customer.io and every other connector (100+)
  • 5 Framer sites
  • Unlimited submissions & file uploads
  • API keys stay on our server, never in your site
  • Cancel anytime
Get 5 Sites — $12/mo →

Unlimited Sites

For agencies with many client sites

$25/ month
  • Customer.io and every other connector (100+)
  • Unlimited Framer sites
  • Unlimited submissions & file uploads
  • API keys stay on our server, never in your site
  • Cancel anytime
Get Unlimited Sites — $25/mo →

14-day free trial of every connector, no card needed. Form fields and FramerSend file uploads stay free forever with a free account.

Start free
14-day refund guarantee Instant license key by email

Why teams use FramerSend for Customer.io

Encrypted API vault, real-time delivery, and unlimited submissions

Lead Capture

Automatically capture and route leads from your Framer forms.

Workflow Automation

Trigger automated workflows when form submissions arrive.

Data Centralization

Keep all your form data in one place, synced in real-time.

Frequently asked questions

Will a second submission create a duplicate person in Customer.io?

The second submission is sent with the same identifier (your id field, or the email), so it is addressed to the same person. How emails are matched depends on your workspace's identifier settings.

Does FramerSend send a Customer.io event?

No. It sends an identify call that creates or updates the person and their attributes. Trigger campaigns from segments built on those attributes.

Can I use an EU Customer.io workspace?

Yes. Enter eu in the Region field and both the Test button and deliveries use track-eu.customer.io.

Which attributes does a submission set?

Every form field under its own name, except recognised standard fields, which are sent once as email, name, firstName, lastName, phone, company, message, city, state or country.

Can I identify people by my own user ID?

Yes. Add a field named id or userId to the form; its value is used as the identifier instead of the email.

What does the Test button check?

It sends a read-only request to the Track API host for your region with the Site ID and API Key. Nothing is created in Customer.io, and a failed test says what went wrong, usually with the HTTP status.

How do I connect Framer to Customer.io?

Sign up for a FramerSend account (or log in). Go to Connections → Add Connection → Customer.io and add your credentials. They are stored server-side and never exposed in your Framer site, which only gets a public form URL.

Are my API keys safe?

Yes, all API credentials are encrypted at rest. The client-side code in Framer only exposes a public Form ID, keeping your private keys entirely secure.

Are there monthly submission limits?

No. FramerSend provides unlimited form submissions across all license tiers so your live website forms never get blocked during high-traffic spikes.