Customer.io Release Notes

Messaging API & developers Design Studio

You can now create, update, and delete emails and components in Design Studio using the App API! This can help you migrate email templates from external tools without manual copy/paste. It also enables you to programmatically add email translations.

You’ll use our latest endpoints to manage content in Design Studio; you can’t update Design Studio content using other message-related endpoints.

You’ll also see new Assets endpoints, which you can use to create, update, or delete images and PDFs in your Asset library for use across message channels.

Keep these best practices in mind as you migrate your HTML to Design Studio!

Go to the docs →

March 13, 2026

AI Admin & billing

Add guardrails to the content AI creates

Account admins can now configure safety and compliance settings for AI embedded in Customer.io. Set guardrails for features like auto-translations, email content analysis, AI subject lines, and more in Account Settings > Privacy, Data, & AI.

Customer.io’s AI tools use Gemini models, so you’ll see Gemini Safety Settings on your Privacy page. You can filter content by four categories—Harassment, Hate Speech, Sexually Explicit, and Dangerous Content—with options ranging from Off (no filtering) to Block low and above (strictest filtering). By default, there is no filtering applied to your account.

You can also include a compliance prompt to help ensure generated content aligns with other regulatory and policy guidelines.

Go to the docs →

March 12, 2026

Mobile SDK

Our mobile SDKs now support location tracking so you can send geo-aware messages with even greater accuracy than IP-based geolocation.

Customer.io already gives you the option to enrich locations from IP addresses, but VPNs, carrier routing, and shared Wi-Fi can reduce accuracy for mobile apps. With the new location module, our SDKs can capture device coordinates and Customer.io reverse-geocodes them into cio_city, cio_state, and cio_country profile attributes. The SDK also sends Location Update events that you can use to trigger journeys and build segments.

To minimize battery usage, our SDKs limit location updates to once per day at most and only when the person has moved a meaningful distance.

Location tracking is available in all our mobile SDKs:

• iOS
• Android
• React Native
• Flutter
• Expo

Go to the docs →

March 9, 2026

Messaging Design Studio

Design Studio: edit your content without leaving your workflow

You can now navigate seamlessly between the Design Studio editor and your automation, broadcast, or transactional message!

Whether you edit the email from Design Studio or your automation, you can now directly update your content from either place.

You’ll also see a few other enhancements:

• Publish status so you know whether all changes are live
• The ability to validate links from any preview in Design Studio
• A confirmation modal when navigating away from a draft so you don’t accidentally lose your changes

Go to the docs →

March 9, 2026

Messaging

You can now reach your audience in Japan, Thailand, Taiwan, Indonesia, and other APAC markets through LINE, one of the most popular messaging platforms in the region.

LINE is the dominant messaging app in key Asian markets, with over 90 million monthly active users in Japan alone and market penetration of 70-95% in its core regions. In these markets, LINE isn’t just another channel—it’s how people communicate daily.

Now you can send LINE messages as a part of your automations and broadcasts. Send text and image messages to your LINE audience, track delivery and engagement metrics, and manage your LINE contacts alongside all your other channels.

Go to the docs →

March 3, 2026

Messaging

Notification inbox: messages your audience can revisit

Now you can send messages to a central inbox on your website or in your app. Unlike in-app messages or push notifications, which are gone when your audience dismisses them, inbox messages give your users a way to see important messages at their leisure.

With inbox messages, you can send important updates like announcements, order confirmations, or reminders to a notification inbox that people can check whenever they want.

For now, you’ll build your notification inbox yourself and invoke inbox methods to fetch and manage messages. Your messages are delivered as JSON payloads that you can render however you want, making it easy to align with your brand and app design.

But we recognize that this takes a bit of work. This is just our first release for this feature, and we plan to make it easier to support a notification inbox and messages in the future!

Go to the docs →

February 17, 2026

Messaging Design Studio

Set global styles for in-app messages

You can set colors, fonts, and more in Global Styles to ensure brand consistency across your messages. They now apply to your in-app messages, in addition to emails made in Design Studio. We're in the process of rolling this out to all accounts this week.

Moving forward, new in-app messages will automatically pull from your global styles, and you can choose to sync existing messages to align them with your current branding.

This release also introduces the concept of publishing to in-app messages. When you publish styles, you decide which emails and/or in-app messages to update. This pushes changes to your workflows (automations, broadcasts, etc) so that whether you send a test message or the automation is actively sending to people, your messages will use the current styles.

Go to the docs →

January 26, 2026

Design Studio Messaging UI improvements

Design Studio: save & edit components from the visual editor

You can now create and save custom components directly from the visual editor in Design Studio! This makes it easier for any team member to manage reusable content like headers and footers.

Build a block using components in the visual editor, and then click to save it as a new custom component file. It’s immediately accessible in the Insert menu of the visual editor for reuse across your emails.

You can also detach components from the source file if you want to make changes unique to that email.

Go to the docs →

January 16, 2026