Customer.io Release Notes

Messaging

Set up channel-based message limits

You can now set up channel-based message limits for email, SMS, push notifications, and webhooks. Historically, you could only set a single message limit across your message channels.

You can add per-channel or shared message limits to ensure your audience receives the right number of messages in a specific time frame. With this release, you can also set a wider time frame for your message limit. Instead of 7 days, your message limit can be up to 31 days.

You can limit the number of WhatsApp and SMS messages sent via Twilio, but not other vendors. Learn more about channel limits.

Go to the docs →

July 15, 2026

UI improvements

We've updated some navigation labels to better match how people think about marketing automation and messaging their audience: Campaigns are now Automations, and Newsletters are One-time sends.

Here’s what changed:

You used to see

You’ll now see

Campaigns

Automations

Broadcasts > Newsletters

Broadcasts > One-time sends

Analysis

Reports

Deliveries & drafts

Message activity (with Sent and Drafts tabs)

Activity logs

Profile activity

APIs and data don’t change. Endpoints, field names, and identifiers keep their names. What we now call an automation is still a campaign in the API, and a one-time send is still a newsletter. Any links you’ve bookmarked will still work; we redirect the old paths to the new ones automatically—both in the app and in our documentation.

July 13, 2026

Messaging UI improvements

See which email clients your recipients use

The new Email clients tab in the Analysis section breaks down opens and clicks by email client. This information tells you which clients you should focus on when designing emails, and how privacy proxies affect your open rates.

The Email clients tab shows each client’s share of your opens, human opens, and clicks, with charts for your overall client mix and how it changes day by day. Email client data is available from April 15, 2025 onward.

The Deliverability tab now also shows a daily send volume chart with bounce and spam complaint rates.

This feature is available to premium and enterprise accounts with access to deliverability analytics.

Go to the docs →

July 12, 2026

UI improvements

If you have multiple Customer.io accounts, you no longer need a separate login for each one. With guest access, you can sign in to your own account and switch to any account that added you as a guest. If you maintained multiple accounts yourself, you can merge them into a single login.

With guest access, you have:

• One login for all your accounts: You sign in to your main login, and you’ll see all the accounts you can access. No more inventing a new email address and password for every account.
• Invite guests like team members: As an admin, you can invite guests to your account.
• Permissions stay per account: Guests only get the permissions you decide to grant them, and everything they do is recorded in that account’s audit log.
• Partners can create client accounts: If you’re a partner, you can create client accounts and see them all in one place from the new Partner Settings page.

Go to the docs →

July 11, 2026

Messaging

We've added a way for you to honor your audience's consent to track email opens. This also helps you stay in compliance with regional regulations, like France's latest CNIL rule, which takes effect July 14, 2026.

You can now decide when to track email opens. This includes:

• A workspace setting to track opens for everyone, everyone who doesn’t explicitly opt out, or only people who opt in.
• A per-contact cio_email_tracking_consent attribute you can set through the API, imports, etc; this attribute represents consent for open tracking.
• A hosted consent page you can link to from your emails, so recipients can grant or withdraw consent themselves.

Go to the docs →

July 10, 2026

Admin & billing Messaging

Custom roles: determine who can send messages

You can now specify whether teammates can send messages and start or stop your workflows, like automations. Previously if you could create an automation or broadcast, you could also activate that automation or send that broadcast. With this change, you can give team members the ability to build and edit automations and content without letting them send things, so you can maintain strict control over who can and can't send messages.

To activate your workflows and send messages, you need the Execute permission for the workflow. To resend deliveries, retry attempted messages, or refire webhooks, you need the Send permission for Deliveries & Drafts and Edit permission for the relevant workflow.

Custom roles created before this release have the same permissions as before—unless you update the role.

Go to the docs →

July 8, 2026

Data & integrations AI

Set up your Salesforce integration in fewer steps. Sync templates for contacts, leads, and accounts come with common mappings, and Agent can suggest fields based on your goals.

Getting Salesforce data into Customer.io used to mean manually configuring identifiers, picking fields, setting filters, and choosing your Data Pipelines format for every sync. Now, sync templates handle the common cases for you.

When you connect Salesforce, you can choose templates for contacts, leads, and accounts. Each template starts with common identifiers, mappings, filters, and fields. Pick a template, review the preview, add or remove fields, and enable the sync.

• Agent-assisted field selection: Click Add fields and ask Agent to suggest fields for your goal, like “segment by company size” or “personalize onboarding emails.” Agent adds relevant fields from your Salesforce schema so you can review them before syncing.
• Preview before you enable: See the number of fields, people, or records that will sync, excluded records, and sample rows before you commit.
• Template or custom setup: Use templates for common syncs, or create a sync from scratch when you want full control over every setting.

Go to the docs →

June 11, 2026