Release Notes

When you create emails, Design Studio is now the default editor. Seamlessly switch between a block-based and code editor to build and fine tune your message. Set branding once in Styles so you always start with the right fonts, colors, and more.

Experiments are the next generation of testing in Customer.io. Test messages or whole multi-step pathways in an automation, then track results and pick a winner without leaving your workflow.

Dynamic senders let you send one SMS message to your whole audience from the right number for each person's country. You set up a dynamic sender once, with a sender for each group of countries, and then pick it in any message like you would a phone number.

The new Click heatmap feature shows your emails with each tracked link marked by how many clicks it got, so you can see which links people use. You'll find it on the metrics page for automation, broadcast, one-time send, and transactional emails.

Provide guidelines like tone, style, and word choices to improve how auto-translate works for each language in your workspace.

The new Query Objects action finds the objects that match your conditions, like courses or accounts, and saves them to a journey or profile attribute. Later steps in the automation can reference the results with liquid.

We've made some updates to our Collections feature, making it easier for you to work with data stored independently of people or events. You can now connect a bucket in Amazon S3, Google Cloud Storage, or Azure Blob Storage, and load files from it into your collections on a schedule. We've increased our size limits and you can also add, update, and delete individual rows in a collection without uploading the whole collection.

Build a sign-up form and show it in your app, on any web page, or on a page that Customer.io hosts for you—all with little to no code. When people submit your form, Customer.io adds them to (or updates them in) your workspace so you can easily engage with people interested in your business.

The new Object trigger starts a journey when a person, their relationship, and the related object meet all of your conditions, in any order. Learn more about the new trigger and how it improves upon the classic triggers.

Now you don't have to juggle site IDs, Track API keys, and App API keys to use our APIs. Now, you generate a key based on where your code runs: a public key for browsers and mobile apps, or a private key for your servers. One private key works with every Customer.io API, so a server integration doesn't need different sets of credentials for different purposes.

Our mobile SDKs can now register Firebase Installation IDs (FIDs) instead of FCM registration tokens. Migrating is optional, so you can move each app when you're ready.

Geofences now support 'dwell times': you can choose how long people need to stay inside a geofence before you message them, and see how long each visit lasted when people leave a geofence.

When you add data-in integrations in the Customer.io UI, the setup screen now has a prompt written for that integration that you can paste into your AI coding agent.

Snapshot segments enable you to track audience membership on your schedule and create a more robust audience for one-time sends. You no longer need to exclusively rely on data-driven segments to group people based on shared conditions.

You can now take an email through its whole lifecycle with the Design Studio API: create it from your own HTML, review and test it, link it to a workflow, and publish changes later.

Customer.io now keeps a history of every time a person opts in to or out of your messages: when it happened, what it applied to, and where the change came from. Now you don't just know your audience's current message preferences, you can keep a history of their choices for compliance purposes.

Now you can import data from Databricks into Customer.io. Connect your Databricks instance, write queries against your data, and sync the results into Customer.io as people, events, and objects (like accounts, companies, etc).

Now you can draw geofences as polygons that follow the shape of the locations you care about rather than just circles that roughly map to your campuses, venues, or other places your audience spends time.

Design Studio just got a major AI upgrade, helping you produce messages with less setup, output that's true to your brand, and done faster than ever before.

Recipients for a one-time send can now be built by uploading a CSV. This helps you send your message to an externally defined audience with the simplicity of a one-time send. Available both in-app and programmatically via API.

Generate real screenshots of your email from specific clients and devices, like the Gmail app on iPhone 16 or Pixel 9. This helps you catch styling issues that only appear in certain email clients.

The Customer.io agent (and associated CLI and MCP tools) can now analyze your workspace's messaging and behavioral data, providing more advanced reports than our UI alone. You can ask for custom reports ranking your automations, comparing inbox providers, tracking conversions, or reporting on site traffic and audience growth.

The Wait Until action now supports one or more delays including time windows, and lets you combine conditions within a path using And, Or, and nested groups.

You can now trigger one-to-one WhatsApp messages—like order confirmations, appointment reminders, and verification codes—from your application using the transactional API.

If you have multiple mobile apps with overlapping audiences, you can support both apps in the same workspace. When you send an in-app message, you can choose the apps and platforms you want to show your in-app message on—no more page-rule workarounds or separate workspaces to keep messages out of the wrong app.

The Customer.io AI agent now works in Slack. You can @Customer.io in a thread to ask it questions about your data and workspace. Or you can message it directly and give it work—without opening Customer.io.

Edit your components more intuitively with slash commands to add blocks, shortcuts to navigate and resize elements, and the ability to click and drag items from any part of the component, not just the handle.

You can now add a rate limit per channel for each of your automations and API-triggered broadcasts. You might add a rate limit to protect your email sender reputation or to prevent overwhelming your downstream systems.

You can now bring your own provider for SMS messages! Previously, you could only integrate with Twilio or work with Customer.io to set up sending with SMS. You can integrate with one or more providers per workspace to make it easier to message people across different regions or subaccounts.

You can now trigger workflows when a person enters or exits a physical location, like a store, a parking lot, a venue, and engage them across any of your message channels. Geofencing helps you send timely, location-aware messages without building custom location logic or relying on a third-party geofencing integration.

You can now attach a file, a Google Drive doc, or query recent events as a knowledge source and reuse it across LLM actions, instead of pasting the same text into every prompt. Reference the knowledge source name in the prompt to tell the LLM how to use it.

This summer, we released more than ten new features, including geofences, live notifications, an in-app notification inbox, and expanded support for SMS providers. Read on for an overview of everything that's new.

We're starting to enable support for multiple mobile apps per platform so you no longer need to duplicate or split audiences across workspaces. You can register each app with its own credentials, send pushes through a specific app, and create segments to group people by the apps they use.

Live notifications let you push real-time, continuously updated notifications to your customers' devices, like a delivery tracker or a countdown to an event. On iOS, they render as Live Activities on the Lock Screen and in the Dynamic Island; on Android, they appear in the notification shade with Android 16's Live Updates treatment.

You can now trigger an automation off a date attribute on a custom object. This means you can send messages relative to a date stored on an object, like trigger reminder automations based on reservations or membership renewals, and avoid storing duplicate data on each person!

When you send a push notification, you can now add a copy of it to your notification inbox. This way, people can revisit the message after dismissing the push or still receive your message if they don't have a device that can receive it.

When you merge people, the primary profile's settings take precedence over the secondary profile's settings. However, now you can update your workspace merge settings to preserve unsubscribe preferences no matter which profile is primary. This helps prevent you from messaging people who opted out.

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.

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.

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.

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.

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 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.

People can now exit your automations early when they meet segment or event conditions. This means you no longer have to depend on conversion criteria to end journeys early. You can define segment or event conditions that match or differ from your automation's goal.

Use the review panel to find errors that could prevent your email from sending, audit your images, validate your links, and see how you score against SpamAssassin to improve the quality of your message.

You can now set separate dark mode values for color properties in in-app messages—like fills, text, and borders—in your in-app messages. This feature is now available for our JavaScript web integration and our iOS and Android SDKs.

Auto-archive is an optional, workspace-level setting that archives unused dynamic segments. This helps you keep your list of segments up-to-date and relevant to your current workflows.

Use our converter tool to migrate emails made in the classic drag-and-drop editor to Design Studio, where you have access to more features like global styles and templates!

We've made it easy to set up a notification inbox for your website, complete with messages styled to match your brand's look and feel. You can do it all without a developer.

You can now save more than one branded look for a global component, then switch between these variants as you build on-brand messages. We also added images and sections to global components so you can set their default styling in one place!

You can now reference snippets ({{snippets.example}}) in anonymous in-app messages, and reuse shared content like a logo or URL across messages.

You can now show or hide which navigation items appear on your left-hand sidebar. This helps you navigate faster and reduces clutter when you don't use certain features.

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.

We now offer an in-app debugger to help you test and troubleshoot your in-app messages and implementation. Add cio_debug_session=true to any page on your site to see the SDK's live state—the workspace it's connected to, the person it's identified, the route it's on, and every message that's active or queued—right on your own site.

You can now add plain text fields in anonymous messages to collect feedback from visitors you haven't identified yet. This can help you gather feedback from users who might not be comfortable providing their name or email addresses.

You can now create custom skills for the agent so it can do things that you and your team do regularly in Customer.io. You might add skills to help the agent enforce your brand voice, review automation drafts, or report metrics in a specific format.

Now you can set your color scheme in Customer.io: your system preference (the default), light mode, or dark mode.

We've made it easier to integrate your HubSpot data and activate it in Customer.io. Our HubSpot integration now includes templates for contacts and companies—the most common data types you'll want to bring into Customer.io. These templates automatically map common fields to Customer.io and you can use AI to suggest additional fields based on your goals.

You can now independently control whether MCP connections can edit live data and access sensitive profile attributes. By default, both settings are off, ensuring that your external AI tools using our MCP connections can't inadvertently expose sensitive data to AI tools or touch things like live segments and automations unless you explicitly let them.

You can now generate global styles in Design Studio from a website link you provide. Previously, you could only generate from one of your sending domains. To get started, go to Design Studio > Styles!

Universal search now covers even more data, including templates, people, product documentation, and newsletters. You can even preview results without leaving your current page.

You can now log into multiple Customer.io accounts and switch between them without logging out.

You can now use Reset message content to quickly change the email editor you're using and start from scratch. This means you no longer have to delete email blocks in automations or switch message types in newsletters to start over and change email editors!

Previously, if you created an automation and later realized you needed a different trigger type, you'd have to create a new automation. Now, you can change your trigger type in your existing automation!

You can now programmatically create and send newsletters from our API! This can help streamline your workflow if you create content outside Customer.io.

If you've used our AI assistant in the past, you'll notice it's had a glow-up. It's now called the agent and it can act as your coworker in Customer.io.

Go to the Workspace Performance dashboard to check the status of your workspace and monitor incoming data and outgoing messages. Use this dashboard to locate and troubleshoot performance issues.

LLM actions let you prompt an AI model and store the output as attributes for use later in an automation. They use AI credits, a new currency in your account.

We've released eight new capabilities—AI-powered intelligence, outcome-first measurement, a redesigned experience, and expanded channel reach—that don't just expand what you can do, but change what's possible.

Your workspace has a new look and feel! You'll see a revamped Home dashboard and a more organized navigation menu.

Now it's easier to find what you need in Customer.io without clicking through menus. Press ⌘K (or Ctrl+K on Windows/Linux) from anywhere in your workspace to instantly search for automations, segments, templates, broadcasts, and more. AI-enhanced ranking surfaces the most relevant results—even if you don't type an exact match.

Your audience can now subscribe or unsubscribe from individual messaging channels—like email, SMS, or push notifications—independent of topic preferences. Now people can choose not just the kinds of messages they want to receive, but also the channels they want to receive them on, so they're less likely to unsubscribe all together.

You can now set a daily ramp period when rate limiting newsletters, which gradually increases your send volume over multiple days to warm up your sending domain.

Our new Live Preview makes it easy to see and adjust your in-app messages in real time, so you can make sure they look and behave the way you want them to before you send them to your audience.

We've added a new Tooltip display type for Web-based in-app messages that anchors your message to a specific element on a page, like a button, menu item, or feature you want to draw attention to. With tooltips, you can provide contextual help, educate your audience about new features, and help orient new users.

Our new Automatic setup option makes it easy to set up your email domains in Customer.io. Powered by Entri, automatic setup connects to your DNS provider and configures your records for you, so you don't have to go through the hassle of manually copying records to your DNS provider.

You can now add up to 10 custom short link domains per workspace for SMS and WhatsApp messages. Now you can use different, branded links depending on the kind of message you want to send.

We've removed a long-standing pain point that prevented you from limiting the send rate for translated newsletters!

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.

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.

You can now preview what your email will look like when Google apps or Outlook force dark mode styles. This helps you see how colors invert in clients that don't support your dark mode styles.

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

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

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.

In object or relationship-triggered automations, you can now hold people in Wait Until blocks based on relationships to any object, not just the triggering object. This gives you more flexibility when crafting your workflow logic.

Design Studio now supports multi-lingual messaging and AI-powered translations! When you add a language to your email, you can auto-translate your content without leaving the editor.

You can now create and update temporary attributes in an automation using a new workflow action—Set journey attributes.

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.

In the past, you had to sign up for third party to send WhatsApp messages through Customer.io, even if you already had a WhatsApp-approved Facebook Business Account. Now you can send WhatsApp messages from Customer.io using your Facebook Business Account without a third-party!

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.

You can capture feedback from your audience directly through Customer.io—without using a third-party form provider. We support forms with plain-text inputs and plan to add support for other inputs in the future—like checkboxes and radio buttons.

You can now optimize images when you upload them through Design Studio to reduce file size and maintain quality—without using third-party tools. This helps reduce friction that can hurt engagement in your automations.

You can now store collection data as journey attributes, which expire at the end of a person’s journey. Journey attributes are available throughout your workflow: reference them in messages, create branch conditions, and more!

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.

In Design Studio and our Drag-and-drop editor, create on-brand subject lines faster with AI. We generate the subject based on your message content and your workspace's AI business context.

You can now move and style multiple components at once in Design Studio emails and our in-app message editor. This can help you more quickly make a change across your entire message.

Configure webhooks once in Workspace Settings, and reuse them across automations and broadcasts—without exposing API credentials to your whole team.

You can now use Wait Until to hold a journey until a condition on the object—or a relationship to the object—that triggered an automation is true. This makes it easy to align messages and other workflow actions to object states or times for things like orders, subscriptions, appointments, and more.

We've redesigned the Help & Support sidebar to make it easier to find resources and get help when you need it!

You can temporarily store data from a webhook on journey attributes, which expire at the end of a person’s journey. Journey attributes are available throughout your workflow: you can reference them in messages, create branch conditions, and more!

Our new Audit Logs give you visibility into team actions across automations, integrations, data exports, and security events so you can debug production incidents faster, meet compliance requirements, and maintain accountability across your team. Now you can see who makes changes to messages, automations, and other data in your account.

We're moved the display and position settings from the message envelope to the right sidebar when you select the background of your message. This lets you change these settings for each step in a message, and is our first change in supporting complex in-app message flows like product tours.

You no longer need to generate custom push payloads to control message priority. Now you can set message priority for push notifications in the push composer. This update helps you balance message delivery speed with battery optimization on recipient devices and does not require you to update your SDKs. It just works out of the box!

No more guessing which login method to use when you log out or your session expires: we now show a Last used badge on the login option you used most recently, so it's easy for you to get back into Customer.io!

If you’re on a Premium or Enterprise plan, you can now customize roles to ensure secure, tailored access to your workspace.

You can now hold people in randomized delays in automations. This can help you avoid overloading API endpoints with webhook requests.

Sticky notes got even stickier! Now you can attach notes to actions in workflows. When you move things around your workflow, your notes move with them. This makes it easy to document automations and broadcasts for your fellow team members and ensures that your important notes don't get lost in the shuffle when you work on workflows.

Our AI Assistant and MCP server can now fetch detailed conditions for segments, automations, and templates, helping you better understand segment conditions and analyze automation performance.

If you send messages relating to healthcare in the United States, you may need to be HIPAA compliant. You can now send secure, HIPAA-compliant messages from Customer.io, safeguarding communications for your patients, members, and customers. Talk to your Customer.io representative about a or Business Associate Agreement (BAA) to get started.

Our Random Cohort feature lets you test different messages or actions in an automation by randomly distributing people down different paths. But this could result in different experiences for people related to the same account, company, or other object, which might your audience. Now, you can use the Cohort by setting so everybody in the same account, company, or other group gets the same automation experience.

Our Recommended Send Time feature uses AI to help you schedule messages at the best times for your audience based on the content of your message and your audience's time zones. You can use our recommendations engage your audience at the right times.

Our new Automatic Geolocation Data Collection feature captures geolocation and time zone data for people based on their IP addresses when you identify them. This data makes it easy to segment your audience by location and send messages at the right times for each member of your audience using our recommended send time feature and time zone match features.

You can now filter incoming Salesforce data to only bring in the data you need to use in Customer.io. In the past, if you didn't want to use all of your Salesforce contacts, accounts, and other data types in Customer.io, you had to bring all of that data into Customer.io and clean it up later. This helps you avoid sending unnecessary data into Customer.io so you can focus on the data you really want to use.

The Assistant can parse information in your images and answer questions about them. This can help you get more useful responses over the course of your conversation.

If you use collections, you're probably used to finding them in the Content menu. We've moved them—under Configure data, click More > Collections. They're much more like data you use programmatically than your typical message content, layouts, image assets, and so on. Don't worry: we haven't changed anything besides moving Collections to a friendlier location in our menu.

Historically you've had to identify someone in your app before you could send them messages—they had to log in or provide their email address. But now you can send in-app messages to anonymous users in your app, and provide offers that entice users to sign up or sign in.

We've upgraded the Assistant so it can answer high-level questions about your automation and broadcast metrics! You can also retrieve metrics through our MCP server.

In the past, if you wanted to securely track links, you had to set up your own SSL certificate and proxy through a service like Cloudflare or tool like NGINX. Now, we'll do all of that for you, making it easy to set up link tracking just like you'd set up an email sending domain.

We've added a drag-and-drop Lead Form component for anonymous messages so you can collect names and emails of anonymous visitors and convert them into identified users.

Translate messages across channels by leveraging AI. We automatically translate your message with AI unless you clear the Auto-translate option when selecting locales. Remember that AI can make mistakes; make sure someone who knows the language reviews the translation.

Analyze your content to help you catch typos, improve tone, and strengthen your message before sending. While editing an email in an automation, broadcast, or transactional message, click Analyze email content for feedback.

Providing context to our AI tools generates better results. By reviewing and updating the business context we auto-generate from your domain, you can ensure you're getting the most out of Customer.io. Go to Workspace settings > AI business context to get started!

Ask the Assistant questions to learn about the platform and your workspace data.

You can now schedule automations which eliminates the need for manual automation activation and gives you the flexibility to plan and execute time-bound marketing initiatives, like limited-time offers or seasonal automations.

Text messaging is a truly bi-directional channel. Often times you want your audience to reply to, and engage with, your messages using a keyword. Now you can handle these replies in Customer.io.

You can now schedule broadcasts to send in users' timezones AND apply a rate limit. This helps ensure the best deliverability for your messages. Keep in mind, this could lead to some users receiving your message after the scheduled time.

Our AI features often rely on the descriptions you provide for your data. These descriptions tell us about your attributes and events so we make accurate suggestions for things like segments. But describing all your data can be a lot of work. Now you can use AI to generate descriptions for your data!

You can now use your own branded domain (like example.com) for shortened links in SMS and WhatsApp messages. That means stronger brand consistency, higher click-through rates, and compliance with evolving regulations.

In-app surveys can be a great way to collect feedback from your users, but it can be tough to analyze the results and determine your next steps. Our Analyze Survey feature uses AI to provide you with actionable insights from in-app surveys and other in-app messages that capture responses.

Chances are that if you've built in-app messages in Customer.io, you've already used our new, visual in-app editor! To continue delivering a more user-friendly, flexible in-app messaging experience, we're ending support for our legacy in-app editor January 1, 2026. If you haven't made the switch yet, now's the perfect time to start using the new in-app editor, designed to help you build better in-app experiences.

You can now create segments and conditions that target when people have opened or clicked on emails. This means you can trigger automations based on human data and avoid messaging people who may have never engaged with previous messages.

Inline messages help you deliver relevant content like onboarding tips, feature announcements, and promotions exactly where users need them—without interrupting them as they use your app.

Understanding email deliverability used to mean juggling multiple reports, subscribing to expensive third-party tools, or relying on generic industry benchmarks that didn't reflect your real audience.

With transactional messaging available for SMS and WhatsApp, you can send important, timely one-to-one messages like two-factor authentication (2FA) codes and one-time passwords (OTP). Now, when your customers need an immediate response, you can send them messages over whatever channel they prefer—email, push, and now SMS or WhatsApp.

Build a segment with AI to help you get up and running quickly and find gaps in your current conditions. Generate a segment from a brief prompt or choose from our suggested segments. Make sure you review the conditions and insights before you save the segment to ensure you're targeting the right people. Go to Segments to get started!

It’s now easier to show in-app messages on the exact pages where you want them to appear. Instead of writing complex regular expressions or listing every page you want to show your in-app message on, you can now use exclusion rules. These let you set up rules like 'show a message on all pages except…'.

Setting up in-app messaging for your website used to mean finding your Site ID (which was buried in our UI) and asking your development team to update the JavaScript snippet on your website.

Have you ever wanted to onboard users with a brief explanation of your app, highlight new features for existing users, or respond to people who answer your surveys? Now you can with multi-step in-app messages—in-app messages that contain sub-messages or steps.

We're in the process of rolling out Design Studio, a flexible email design system that helps you create beautiful, responsive emails faster than ever before. Use components to create a block-based email from scratch, and set global styles to create a consistent brand across your messages made in Design Studio. No longer do you have to decide between a visual or code-based editor; you can use both!

It’s now easier to track engagement with SMS and WhatsApp messages. SMS and WhatsApp messages previously required you to manually add inline liquid syntax to track links. Now we’ll automatically shorten and track your links by default so you can see when recipients engage with your messages. You can also enable or disable link tracking with a single toggle, just like in your emails.

For a while, you've had the ability to A/B-test newsletters. But for any newsletter that wasn't an email, you had to monitor the results manually. Now we'll automatically detect which version of your SMS or push notification performed best, helping you optimize these messages without the extra work.

You can now track human vs machine email engagement trends in your automations, broadcasts, and transactional messages. Our new Human opened and Human clicked metrics exclude machine interactions from user bot agents, security scanners, and more so you know how people engage with your messages.

Account admins and workspace admins can now mark profile attributes as sensitive in the Data Index then hide this data from specific authors or viewers. This helps you ensure that sensitive data is only visible to the right people in your workspace.

You can now create automations by defining profile attribute conditions in the trigger. In the past, you had to create segments to trigger based on profile attributes, but now you only create segments when you need them. You can continue to define segment membership alongside attribute conditions for maximum flexibility.

Send in-app messages like banners or surveys to unidentified visitors on your website or app to encourage them to sign up and convert. This is available to all Premium and Enterprise customers. Go to Anonymous Messages to get started.

Build a segment with AI to help you get up and running quickly and find gaps in your current conditions. Generate a segment from a brief prompt or choose from our suggested segments. Make sure you review the conditions and insights before you save the segment to ensure you're targeting the right people. Go to Segments to get started.

Now that our Expo plugin supports all of the features of our React Native SDK, we’re excited to announce its first official release!

This change makes us compliant with Twilio's WhatsApp sending guidelines, and makes it easier to use your WhatsApp templates in Customer.io. If you already send WhatsApp messages, you'll need to upgrade your current WhatsApp templates to content templates in Twilio before April 1st, 2025.

You can now enable link shortening for SMS and WhatsApp notifications! This will shorten both tracked and untracked links to help you stay within characters limits and streamline your messages.

You can now add descriptions to attributes to ensure all of your teammates understand your data. Go to your workspace's Data Index to get started. This is available for profile attributes, not event attributes currently.

Your website might display different kinds of in-app messages that aren't always easy to dismiss. Now you can set up messages to dismiss when users click outside of them. This is a common pattern that internet-users are used to seeing and helps you create messages consistent with users' expectations, like banners or other informational messages that don't require user interaction.

You now have more flexibility over who enters object and relationship-triggered automations! Previously, you could only trigger these automations for people who matched your trigger after the automation started. Now you can trigger these automations for people who already match your automation trigger when the automation starts. For instance, if you trigger an automation when the plan of an Account object changes to premium, you can now include people who are already related to Accounts with premium plans.

Before now, you weren't able to take advantage of our JavaScript source integration if you used Segment.com's analytics.js client. Now, you can use the two together. If you're a Segment user and want to take advantage of Customer.io's native web integration, you'll call Customer.io from the cioanalytics variable and avoid conflicts with Segment's analytics variable.

Where most in-app messages let you message your audience, inline in-app messages provide a way to send content to your app without requiring an app update. Now, with version 3.8 or later of our native iOS SDK, you can use our in-app features to send messages that don't look like messages! Inline in-app messages let you send content that looks and feels like a part of your app—like personalized coupons, articles that might interest your users, events they might be interested in, and other things that apply to individual app users.

If you use Cloudflare or JumpCloud as your SSO identity provider (IdP), you can now enable SCIM 2.0 to auto-provision access for team members. After enabling this, just add or remove users from your IdP, and they'll be automatically added or removed from Customer.io. You must be an Account Admin in Customer.io to modify SSO settings. Go to your Account Settings to get started.

Our new automation builder has all the same features and functionality as before, but now you can modify settings, trigger data, and your workflow from one place! Modify automation settings in the top-left menu, and click + Build at the bottom to drag messages and actions onto your workflow. You'll automatically have the new experience the next time you log in; no action is needed on your part. All your existing automations will continue to work as expected.

We've updated our Expo SDK, adding CDP features so you can seamlessly integrate with destinations beyond Customer.io—like your analytics platform, CRM, or data warehouse. Customer.io can be your customer data platform (CDP) for free!

You can now duplicate automations within a workspace to preserve automation settings like triggers, goals, and exit criteria in addition to workflow actions. Previously, you could only copy workflow items across automations.

Attio is a Customer Relationship Management (CRM) tool that helps you manage your customers and their relationships. With this integration, you'll send records—the people and companies you identify—to Attio, where you maintain a holistic view of your customers and their activities. This means you can add new people and companies to Attio or enrich records in your CRM with attributes from Customer.io

You can relate people to non-people data called objects - like companies, accounts, and online courses - and trigger automations based on this data. Previously, you could only use object and relationship attributes in branches within object and relationship-triggered automations. Now, you can use this data to split people in your workflows across all automation types - segment-triggered, event-triggered, etc. Check out how you can use this functionality to personalize onboarding, drive feature adoption, and more!

We've updated our Flutter SDK, and it now has features that help you seamlessly integrate with destinations beyond Customer.io—like your analytics platform, CRM, or data warehouse. Customer.io can be your customer data platform (CDP) for free!

If you've exported Customer.io data to a data warehouse, you might have noticed that while we exported information about people and automations, it might be hard to figure out what automations and messages people received because we exported IDs for those things. We're fixing that problem with new outputs, so you can resolve automations, messages, and object-relationships to the right data with new Automation Metadata and Object exports.

We've updated our React Native SDK, adding CDP features so you can seamlessly integrate with destinations beyond Customer.io—like your analytics platform, CRM, or data warehouse. Customer.io can be your customer data platform (CDP) for free!

Firebase is a core dependency for many mobile apps and version 11 produced significant changes for Firebase users. Now we support the latest major Firebase release with our iOS-compatible SDKs. To take advantage of Firebase 11 in your Customer.io-integrated app, upgrade to the SDK versions below (or later):

Our Salesforce integrations were available in early access for the past few months while we polished the feature. Now we're excited to announce our Salesforce integration is available to everyone on premium or enterprise plans. By syncing your Salesforce data with Customer.io, you'll be able to nurture leads, keep up with your contacts, and activate all the complex relationships that you normally store in your enterprise CRM.

In the past, you not only had to know who you wanted to send your in-app message to, but how you identified them—by email or ID. Now, you can send in-app messages to your audience without needing to know how you identified them. Whenever and however you identify people, they'll get your message.

You can now pause a newsletter, fix a typo or other information in your message, then resume sending. You can pause a newsletter using any message channel - email, in-app, etc. You must have Workspace Admin or Author permissions to pause and resume a newsletter.

The latest version of our Android SDK is out, helping you support seamless integrations with both Customer.io and your data to downstream destinations—like your analytics platform, CRM, or data warehouse. This release also adds support for anonymous users.

While we've supported in-app messages for a while, we knew that our initial in-app message editor was clunky and hard to use. We've rebuilt it from the ground up, so you can create in-app messages with a drag-and-drop editor. Now you can easily build in-app messages that look and feel like parts of your app or website. With this release, we even added support for video in in-app messages!

You can now send emails to a team member before verifying your domain so you can test them without delay. Admins and Workspace Admins can manage message sending and who receives test emails from General Workspace Settings.

You can now export attribute and event data by going to Data Index in your workspace. You must be a Workspace Admin to export your data index.

We've added a new account-level role, Member, so you can grant read-only access to account settings. You can also grant Members the ability to manage account info and billing, manage API credentials, or enable access for Customer.io support teams. Everyone who was a Workspace Admin, Author, or Viewer now also has a Member role to reflect the account-level permissions they already had. No one's access to your account has changed. We did not grant or remove permissions from any team member.

In the past, you could only assign a single role to each team member then limit which workspaces they had access to. Now, you can specify a different role for each workspace they have access to. This gives you more control over what your team members can manage across workspaces.

We now support SAML for many single-sign on (SSO) providers, so you can use your identity provider (IdP) with Customer.io—including Cloudflare, Jumpcloud, and more. Go to Account Settings > Security > Enable Single Sign-On (SSO) to get started. You must have the Admin role to configure SSO.

Salesforce is great at storing and organizing relationships with your customers. Customer.io is great at activating those relationships. Now, if you're on a premium or enterprise plan, you can use the two together and send your Salesforce data to Customer.io where you'll send messages to your contacts, nurture leads, and more. With this native, two-way integration, you can even send your Salesforce data to other downstream destinations, like your analytics platform or data warehouse.

Along with all the other great features in our iOS 3.0 SDK release, we also added support for Apple's visionOS. You're no longer limited to phones and tablets; now you can engage with your Apple Vision Pro users in augmented reality too, sending personalized push notifications and tracking behavioral activity like you would from your mobile apps.

CSS pre-processing converts your CSS styles to inline attributes in your emails. Disabling this means we won’t change the code of your template, ensuring it stays exactly as you designed it. We've added a workspace setting so you can disable CSS pre-processing for emails created in the code editor. In the past, you could only disable this on an email. Now, you can also disable this for all new messages made with the code editor. Go to Workspace Settings then click Email > Default Email Settings to change this setting.

Beginning May 1, 2024, Apple's App Store requires mobile apps and the SDKs you use to build your app to include privacy manifests. This includes Customer.io's SDKs. We've updated our SDKs to include privacy manifests. Update your app to one of the versions listed below (or later) before May 1st, 2024 to ensure that your apps meet Apple's requirements and aren't rejected from the App Store.

You can now add a person to or remove them from a manual segment through their profile page. Go to a person's profile then click the Segments tab. Go to the tab Doesn't Belong To then click Add to segment beside any manual segment so they join it. Or, under Belongs To, click Remove from segment so they leave it. Keep in mind, after you remove people from or add them to manual segments, they may trigger automations.

The latest version of our iOS SDK is out, providing a seamless integration with Customer.io Data Pipelines. This update makes it easier to support both Customer.io and your data to downstream destinations—like your analytics platform, CRM, or data warehouse—and lets you track anonymous users.

This applies to accounts created before Nov 28, 2023; all other accounts use our latest liquid version. You can now upgrade your workspace so that all new messages moving forward use our latest liquid version. The latest liquid version offers improved filters (e.g. default filter), faster rendering, and better tools for troubleshooting liquid syntax. Take a look at the differences between our latest and legacy versions of liquid to see if you're ready to make the switch. Then go to General Workspace Settings to upgrade. Keep in mind, you will still have to manually upgrade existing messages. If you run into unexpected syntax issues with the latest liquid, use our fallback logic.

As an Admin, you can now download your billing invoice from Account Settings > Plans & Billing > Billing History. Click Download invoice beside any billing period for a PDF.

We now check your DMARC policy when verifying your email sending domains to enforce Gmail and Yahoo's new sending requirements. Visit your Workspace Settings and click Show Records to check the state of your DMARC policy and whether we recommend you update it. These requirements are designed to help prevent email spoofing and phishing attacks.

If your account was created before Nov 28, 2023, you now have the ability to upgrade to our latest liquid version, which provides faster rendering and new functionality. Check out what's new and deprecated with the latest version. You can update a message through the Actions dropdown while editing.

A couple of weeks ago, we changed the file size limit from 3MB to 1MB to scale our file storage and follow best practices for email. But after considerable feedback, we're changing it back to 3MB to better support your needs. We'll continue looking for solutions to storage and deliverability optimization.

We've released updates for our iOS-supporting SDKs, so they'll automatically register device tokens and capture opened metrics for push notifications. Now that we handle these things, you can remove some code, simplifying your integration and improving reliability when you update our SDKs in the future.

We've made two updates to enhance your reverse ETL integrations. First, we added a setting that allows you to decide how imports handle suppressed people. Second, we updated our import logic such that all reverse ETL imports start at a predictable time based on when your imports first started and your interval setting. For more information and examples, go to your database's documentation. For more on our suppressed person setting, go to Add a sync > Step 4. For more on interval calculation, go to Sync intervals and skipped syncs.

We changed the limit for image uploads from 3MB to 1MB. This helps us control the scale of file storage and follows best practices for image sizes in emails.

We revamped our automation creation experience so that it is easier for you to find and refine the triggers you need. Go to Automations in the left hand navigation and click Create Automation in the top right to get started.

Your toolbox in Customer.io just expanded! You can now trigger automations based on an update to an object, an update to a relationship, or the addition of a relationship to an object. This is helpful when, for instance, you want to send a person through a journey when an account object they're a manager of is updated or when their role at the account has changed. Go to Automations in the left hand navigation and click Create Automation in the top right to get started.

You can now import a CSV of objects or relationships through our UI or API. This is helpful if the data is not available through an integration or you are just getting started and need to quickly backfill data. To import objects or relationships through our UI, under Configure data, click More > Imports. To import them through our API, use our import endpoint. Note: the people and objects referenced in your relationship CSV must already exist in your workspace for the import to succeed. Also, keep in mind that importing objects and relationships can trigger automations! Check that your CSV is correct before initiating import.

You can now retrieve and update translations of messages using our App API. This includes automations, newsletters, API-triggered broadcasts, and transactional messages.

You can now export object and relationship data from the people or object summary pages as well as from individual people and object pages. This gives you flexibility to share this data with your colleagues that do not have access to Customer.io.

By default, our in-app messages have a maximum width of 414px—a common breakpoint for mobile design. But that might be too narrow for non-mobile mediums, like your desktop website. Now you can set a custom max width for in-app messages, expanding your message on larger screens while still being responsive when your message appears on screens smaller than the max-width value.

By default, we display modal in-app messages on top of a background overlay colored black with 20% opacity. Now you can customize the modal overlay color and opacity to better fit your brand and ensure that your messages are accessible to all of your users.

You can now hide attributes and event data from team members with the Author role to limit who has access to personal information in your workspace. Admins can manage this setting in Account Settings > Team Members. When creating or editing a team member with the Author role, toggle on the setting that prevents them from viewing attributes and event data. Authors with reduced access cannot manage segments, objects and relationships, or webhooks. They also cannot edit people or attribute conditions for broadcasts.

Now you can set up multiple page rules for an in-app message, making it easy to show your message on any page relevant to your message and audience.

The Zendesk destination helps you identify your users, so you can keep a record of your users and can easily identify the people and organizations who ask you for help.

You can now keep banners and messages on your web or mobile app until a set expiration date. This option is perfect for announcing upcoming conferences, webinars, promotions, and more.

If you use outgoing webhooks to trigger messages from a third-party provider that is not natively integrated with Customer.io, you can send incoming calls to our Track metrics API to capture metrics in Customer.io. This allows you to see delivery metrics for all of your messages in one place.

You can now retrieve a list of all workspaces and high-level data, like people and object counts, through our App API. This is useful if you need to track usage outside of Customer.io.

You can now hide attributes and event data from team members with the Viewer role. Admins can manage this setting in Account Settings > Team Members. When creating or editing a team member with the Viewer role, toggle on the setting that prevents them from viewing attributes and event data.

The Google Tag Manager (GTM) destination helps you take advantage of GTM in Customer.io. You won't have to drop in the GTM snippet or call gtag directly.

Following our last update, we've made it even easier to build in-app messages. Now you can drag-and-and drop components. This gives you the flexibility to build your message in any order and reorganize it later—you can simply change your layout and move elements to the right places at any time.

You can now enable your subscription center faster by assigning a topic to multiple automations and broadcasts simultaneously. Note, to enable your subscription center, all your running automations, API-triggered broadcasts, and scheduled newsletters need a topic. To identify which message workflows still need a topic, go to Workspace Settings > Subscription center. Then go to the Topics table and click Review.

In-app messages often contain groups of nested components, which can make it hard to find the part of the message you want to edit. That's why we added a new panel to our in-app message creator: to help you easily find and jump to the parts of your message you want to edit.

In-app messages are a great way to connect with people who are already engaged with your app, but it hasn't always been easy in Customer.io to build or track in-app messages with multiple choices. With our new Microsurvey components, we've made it easier to send messages with quick, recognizable calls to action. This release also adds the ability to track responses to your in-app messages and surveys.

You can now view unsubscribe rates for subscription center topics when viewing Performance & Delivery Metrics or Message Metrics for automations and API-triggered broadcasts within the Metrics tab. For newsletters, go to the Overview tab. You can also compare metrics through your Analysis Dashboard. This data can help you determine subscription topic interest by monitoring unsubscribe rates.

React Native SDK v3 is live! Automatically update native SDK releases and integrate rich push easier. Follow our migration document (you only need to modify your Podfile) to upgrade, today.

You can now add pre-built blocks to your in-app messages to save time constructing message frames, buttons, and rounded images! Select from the component dropdown to get started.

You can now override a subscription topic at the message level. Within an automation, select an email then select a different topic from the Subscription Preference dropdown. This way, you can target different audiences within a single automation.

We've made a series of improvements to our in-app message editor that make it easier to build and preview your message.

You can now create your own, custom subscription preferences page by fetching preferences from our App API and updating them through our Track APIs. This gives you full control over the branding, formatting, and location of your subscription preferences page.

We now support SSO with providers that are compliant with OpenID Connect. This includes but is not limited to OneLogin and Auth0. Go to Account Settings > Security > Enable Single Sign-On (SSO) to get started. You must have the Admin role to configure SSO.

You can now change the order of your subscription center topics through Workspace Settings > Subscription center > Edit on the Topics table. This can be useful when you add or remove topics or want to rearrange them to reflect a hierarchy of importance.

We've added functions to all of our SDKs to manually dismiss in-app messages. This is especially helpful in handling custom actions, so you can dismiss messages after your audience interacts with a custom button or link. You can listen for message interactions and then perform dismissals based on the actions users take in your messages.

You can now add and delete relationships between objects and people in the UI, which allows you to explore objects without engineering. You can use relationships to segment users and to personalize messages with object data.

You can now translate your subscription center topics and headers for your audience. You can add translations for 29 languages and decide when to make them live to your users. Go to Workspace settings > Subscription center > Settings to get started.

You can now verify webhook requests sent through our Send and receive data actions using a key that is separate from your reporting webhooks. To find the signing key in your workspace, go to Settings > Workspace Settings > API & webhook credentials and select the Webhook Signing Key tab. Users with the Admin, Manager, and Author roles can view this key. You can continue to find the key for your reporting webhooks in Integrations > Reporting webhooks.

We now support single sign-on (SSO) with Azure AD. Go to Account Settings > Security > Enable Single Sign-On (SSO) to get started. You must have the Admin role to configure SSO.

You can now create more object types in your workspace! Personalize messages across multiple relationships between your customers and groups they belong to like companies, courses, and events.

You can now update the branding of your global unsubscribe page! Go to Settings > Workspace Settings > Subscription Center to add a logo and/or update the background color of your Unsubscribe button. If you have not enabled our Subscription Center, your users will see this page after selecting Unsubscribe.

Easily create, personalize, and measure your transactional push notifications with our Transactional Push API. Need to add an image or deep link or send in multiple languages? No problem — make updates to your transactional messages without changing a single line of code.

To protect accounts on our platform, we've enabled two-factor authentication (2FA) for all accounts that do not use SSO. If you've already enabled 2FA via authenticator app, there will be no change to your sign-in pattern. If you have not enabled 2FA via auth app and do not use SSO, you will now verify your log-in attempt through an email from us here at Customer.io. Just make sure you click the emailed link on the same browser and device on which you attempted to sign-in, and you'll be good to go!

You now have more flexibility when setting preferences for subscription topics. You can update some topic preferences for people, while preserving those set for other topics, using JSON dot notation. This applies to CSV import, our create/update person action, and our Track API.

Our Flutter SDK has been in beta for the past couple of months. Now that we've smoothed out the rough edges, our 1.0 release is ready for use in your production apps.

When you use our SDKs, you can now send push notifications to iOS devices that use the default system sound, alerting your audience when they get a new message. This affects all of our SDKs that support iOS, including React Native, Flutter, and our Expo plugin.

We've added support for AMP components to our email code editor! Validate AMP and send test emails from within your workspace.

Now you can sync objects (like companies, accounts, or online classes) and relationships as a part of our Reverse ETL database integrations—MySQL, BigQuery, Snowflake, and so on. Now you can easily add objects and relate them to people on a regular interval based on business logic and data that you store outside of Customer.io.

We've had our in-app solution in beta for a while now, while we smoothed out some rough edges. Now, it's ready for everybody.

We moved in-app message templates and branding settings under the Content menu, so you can get there in fewer clicks. But that's not all. In this release, we also improved the in-app message editor, so that it's easier to craft your messages.

We've added the ability to rename messages for their intended purpose as you determine your messaging strategy and find specific uses for different kinds of in-app messages. In the near future, we'll also add the ability to delete in-app message templates!

Now you can set your primary brand color and add a logo to your subscription center page, so it looks like a part of your brand and website. Branding your subscription center gives people confidence in their preferences, so they know that they're on a page associated with your brand.

We recently released objects—a feature that lets you set relationships between people and groups like accounts, companies, online courses, and so on. As a part of that release, you could create segments based on relationships between objects and people, but you could only use those segments with newsletters. Now you can use these kinds of segments to trigger automations! This makes it easy to onboard new people when they join a company, sign up for a new course, and so on!

Message limits help you make sure that you don't over-message and annoy your audience. But, previously, messages that went over the limit—Undeliverable messages—could pile up in your workspace. Now you can set an auto-retry interval for messages that hit the limit, and automatically retry messages up to 24 hours after they hit your message limit. This helps you make sure that time-sensitive messages don't go undelivered!

We now support objects—non-people data that you can relate to people, like accounts that people belong to, flights they've booked, online courses they've enrolled in, and so on. This release is only the beginning. Support in this release is limited to a single object type and they're limited to Newsletters, but we're actively working on this feature to add support for more objects, automations, and object-to-object relationships.

We've added a subscription center feature that can help you manage your audience's subscription preferences without having to manage a complicated set of preferences on your own. This feature makes it easy to set up your subscription topics, apply those topics to automations or broadcasts, and let your audience decide what topics they want to subscribe to.

People login and out of mobile apps all the time, causing device tokens for mobile push services to change. Rather than letting those tokens stack up in your workspace, we've started automatically removing 'devices' when they're no longer able to receive push notifications—beginning January 31, 2023.

With our original Track API, you're limited to a single request per person, and a host of different endpoints. Today we're releasing our v2 Track API, which lets you send groups of requests for different people, and different kinds of actions, to our /v2/batch/ endpoint. Now you don't have to maintain different calls for different actions; you can just modify your payload to fit different request cases and send requests in batches.

In our quest to support your mobile apps, no matter what platform you build them on, we've released an alpha version of our Flutter SDK! While this is an alpha, the SDK contains all of the features of our other SDKs, including support for rich push and in-app messages. The alpha label simply means that we've been limited to internal testing, and we need your help to make sure that it performs the way you expect it to.

We've made page rules for in-app messages easier to use! Before this update, you needed to set up a complicated workaround to limit an in-app message to your website or mobile app. Now, when you select your web, iOS, and/or Android channels, we'll automatically limit messages to the platforms you select. If you don't select any platforms, your message will appear on whichever platform the person visits first.

A holdout test is a type of A/B Test that lets test whether a message is useful or not. In a holdout test, some members of your audience receive a message and some don't—but we still calculate conversions for the message, helping you see whether your message affects your conversion rate.

In the past, you needed to hunt down the ID of a transactional message before you could use it and actually send messages to your audience. Now you can set a friendly, case-insensitive Trigger Name, and use it to send messages. The Trigger Name makes it easier to find the message you want to send. It can also make your integration more human-readable if you use triggers that represent the kinds of messages you send—like password reset or order confirmation

In the past, our database sync integrations ran on an interval plus the time it took to complete an import from your database. So if a minute to sync your database and you set your sync interval to an hour, you effectively had a sync interval of 61 minutes, causing your expected sync interval to drift over time.

We now have direct integrations with Amplitude and Mixpanel, so you can export your audience engagement data to your analytics platform without needing a middle layer like Segment.com.

We've extended multi-language support to our transactional API, so you can easily send transactional messages to your audience in their preferred languages. When you create a transactional message, you can add languages—versions of your email that are localized for different members of your audience. When you send your message, we'll match your audience's language attribute to the languages in your message, and people will receive the localized message that best represents them.

You no longer need to upload the same image multiple times to reuse it across messages, nor do you need to host your own images! With our new Asset Library, you can upload images and reuse them across different messages.

When you send an in-app message, you can set a page rule determining the page a person needs to visit to see your message. Now you can use the * wildcard in page rules, so you can load a message containing a word or under a set path. This makes it easier to control where your in-app messages appear, so your audience receives your message on any relevant screens or pages.

In-app messages support an expiry value, so that you only show messages to your audience when they're relevant. But, in the past, we only allowed you to set expiration values in days. Now you can set messages to expire in hours or minutes, helping you send highly relevant, time-sensitive messages to your audience. It can also make it easier to test your SDK integrations with us!

Our first official release of our React Native SDK is now available. With our React Native SDK, you can take advantage of Customer.io in your mobile apps without having to maintain separate native platforms for iOS and Android. Implement our SDK in your React Native app to identify your mobile users, send rich push notifications, and send in-app messages—all without writing your own integration from scratch.

When you set up an automation conversion, you can now compare your conversion event to your trigger event. This is a great way to determine the success of your automations based on related events.

We've updated our data warehouse integrations to version 4, including a new Delivery Content schema containing message contents—so you can maintain a history of the text and images you sent your audience. When you upgrade to the latest version, you'll be able to export message contents and confirm the bodies and subjects of messages that were rendered and sent to individual users.

In the past, if you wanted to reuse a newsletter in another workspace, you had to create it from scratch. Now you don't need to do all that work, you can simply copy your newsletters to other workspaces!

When you go to create an automation, you'll notice some changes to our automation Trigger page. We've redesigned this step in the automation setup process to make it easier to understand how each trigger works and when you should use them.

Have you ever found people with the same email address or phone number in your workspace, and accidentally sent duplicate notifications? Now you can export a list of people who have the same attribute, making it easy to find and deduplicate people or attributes in your workspace.

We're updating our push editor, so you can send rich push notifications containing images, links, and even custom key-value pairs without writing complicated custom JSON payloads. With this update, push previews also update to include images, helping you visualize your push notifications.

We recently updated our Wait Until action to support different conditions—including waiting until a person performed an event. Now you can set event properties in wait conditions, helping you wait until a person performs an event matching very specific parameters.

In a previous release, we exposed the ability to use JSON dot notation to access nested attributes and event properties in segments, filters, etc. But what if you're not a developer or familiar with JSON? This update adds some simple options that can help folks traverse nested attributes without needing a deep understanding of JSON and related terms!

You can now install and use a React Native version of our SDKs—including rich push and in-app features. We're confident in the core features and we don't expect to introduce breaking changes before we officially release it. But, we have a bit more work to do, a few questions to answer, and we need your help to make sure that we build the SDK to fit your needs. Start using it today and send us your feedback!

This release makes it easier to add people to your workspace without making identify calls for each individual person. Now you can use our App API's new /v1/imports endpoints to import a CSV where each row represents a person, letting you add and update a large number of people with a single operation.

We've added a preview function for messages in your automation and broadcast workflows. You can hover over a message action in your workflow to see a preview, so you can always find the right message without clicking into message after message to find the one you really want.

We've been testing our in-app solution for a few months now in a closed beta, and now it's ready for a wider audience. You can now send in-app messages to mobile apps and web users! Start using it today and send us feedback to help guide our product roadmap.

A few weeks ago, we enabled Parcel's code editor for email as an experimental feature. It's been so successful that we've enabled it for everybody. When you write emails using the code editor, you can now preview your output, take advantage of focus and inspect modes, test your message for responsiveness, and more!

Now that Customer.io has acquired the best coding platform for email, we've started integrating it into our platform—beginning with our email code editor. Enable the Parcel Editor experimental feature to take advantage of syntax-aware autocomplete, responsive previews, and focus mode that helps you zero-in on the elements you want to edit.

A standard SMS text message is limited to 160 characters, but a picture is worth a thousand words. Now you can send images in your SMS messages to increase engagement with your mobile audiences in the United States and Canada.

Earlier this month, we added the ability to track conversions for Automations and Broadcasts when someone in your audience performs an event. Now you can do the same with Newsletters. Setting an event-based goal for your newsletters can help you accurately determine how effective your message is based on your audience's behaviors after they receive your message. You can track conversions over time to improve your messaging strategy.

In the past, you weren't able to create segments or use complex JSON attributes (arrays, nested objects, and arrays of objects) in filters, branch conditions, etc. This forced you to flatten your attributes and events to fit the sorts of segments you wanted to create, which could take a lot of effort and planning. Now, you can use complex JSON in conditions, making it easier to use your data and segment your audience without reshaping your data.

Now you can upload events your audience performed via CSV. Whether you're just getting started with Customer.io, or just capturing new types of events on your website or in your app, this feature can help you backfill events and segment or send messages to your audience based on events they've already performed.

Conversions help you determine the efficacy of your messages and automations by recording when people respond to your call to action. We've simplified the way in which you achieve and set goals by allowing you to base conversion criteria directly on incoming events.

Now you can export your workflow as a PNG. This makes it easy to share your automations with people outside of Customer.io.

We've updated our Wait until... automation action, so you can hold people until they gain an attribute, perform an event, or wait until a timestamp in the event that triggers your automation. For example, if you send an event when a person signs up for an appointment, you can use a timestamp in the message to hold a person in your automation until it's time to send them follow-up reminders!

To localize automations or broadcasts in the past, you needed to use liquid or complicate your workflow with multi-split branches. Now, you can use your audience's language attribute to produce multi-language messages in a simple, in-line workflow.

This release adds a processing queue to the SDK and support for device attributes.

We've updated our iOS SDK to add support for device attributes—properties that you can use in segments, filters, etc. The SDK automatically gathers a series of device attributes, helping you automatically capture information about the operating system version, your app version, whether a device has push notifications enabled, etc. You can also set your own custom attributes, helping you track custom properties that are important to you and your push audience.

When you use Customer.io as a Segment Source, you're no longer limited to just email events. Now you can pipe event information for all of your message channels a Segment Destination, where you can aggregate customer data. To enable other channels, you just need to remove your integration and then add it again.

You can now click the user icon in the upper right corner and go to Experimental Features to try out new features before they're released. This gives you access to some of the things we're working on and presents you the opportunity to tell us how you feel about them. Tell us whether you like a feature or not and what might improve it, so that we build the right features for you!

Now you can sync metrics, deliveries, people data, and more to your Microsoft Azure Blob Storage bucket. We sync data up to every 15 minutes to help you keep up with your Customer.io data. Once in your Azure bucket, you can ingest data to your data warehouse and analyze your Customer.io data.

If you wanted to see how your automations and messages performed, you used to be limited to custom date ranges within the past 120 days. Now, you can check metrics using any custom date range in the past 12 months, making it easy to see how your automations and messages performed over the specific time periods that you care about.

Now you can capture HTML form submissions using your forms' action attribute. This makes it easy to gather form responses from your audience without writing code or installing our JavaScript Forms snippet.

Our new batch update action makes it easy to handle one-to-many relationships, like an account with multiple users or a product update that a group of people are interested in. With a batch update, you can associate a single incoming piece of data with, and even send messages to, a group of people.

Want to set up a database source, but not ready to import people just yet? Now you can schedule the start time of your initial database sync integrations, so you can turn your integration on at a date and time that you're comfortable with. The start time represents the beginning of your first sync operation with recurring syncs on an interval after the start time.

You can now set a series of attributes on mobile devices in Customer.io, and use these attributes to segment and filter people in automations, broadcast audiences, etc. If you use our SDKs, we capture some pre-defined device attributes—like operating system version and device model—automatically. For our SDKs, this feature is only currently available in Alpha builds, but we'll roll it out to new releases soon enough.

Now, when you click a snippet, you'll see where it's used, helping you understand the impact of changes to your snippets! You can also sort, filter, and search for your snippets, making it easier to find the snippets that you want to use or edit. This update also adds a check that prevents you from deleting snippets that are in use, making sure that you don't inadvertently change a message or automation.

Do you need to reshape your trigger data or perform calculations to reformat values? This update lets you manipulate values in Create or Update Person and Create Event actions using JavaScript return statements. If you're already familiar with JavaScript, you may have an easier time using JavaScript to convert and re-shape JSON values than you might with Liquid.

return trigger.plan_name ?? 'free_trial';

{% if trigger.plan_name != blank %}
  {{ trigger.plan_name }}
{% else %}
  free_trial
{% endif %}

You can now create segments, filters, or set automation conditions using the platform, last_used, and last_status attributes attached to your audience's devices. This update lets you use device attributes in the same way that you use people's other attributes, helping you send push notifications to a targeted audience of people with relevant devices.

We've updated our Integrations page to better reflect your active integrations and suggest integrations that might be relevant to you. The new page organizes your active integrations into Data in and Data out categories at the top of the page, showing which direction your active integrations flow.

The formerly-known Beta API is officially released! These endpoints are now available under our App API: the endpoints that you used to access with https://beta-api.customer.io/v1/api/, are now available at https://api.customer.io/v1/; if you're in the EU region, former https://beta-api-eu.customer.io/v1/api/ endpoints are now at https://api-eu.customer.io/v1. These endpoints are stable parts of the Customer.io platform and you can use them confidently.

We've replaced our attribute update action with an improved Create or update people action. This new action lets you update multiple attributes for a person with a single action in any automation workflow. You can also update someone other than the person currently in the automation journey—or create a new person if they don't exist. This is particularly useful if you're connecting data and third-party tools using a Data Automation

Now you can filter your message library by status—Sent, Drafted, etc.—and type, making it easier to find your messages. This release also lets you exclude messages from archived automations, helping you narrow your scope when you look for a message. Go to Message Library to search through your messages.

Our Create Event workflow action used to be limited to Data Automations. Now you can create an event in any automation, regardless of automation trigger, providing a handy way to trigger parallel automations and add people to segments. You can create an event for the person in your current automation, or another related person: anybody whose ID or email that you can access from the trigger event or the current person's attributes.

You can now capture form submissions from the Wordpress WPForms plugin without Zapier. To identify and capture responses from people who fill out your forms, simply add the JavaScript forms snippet to pages containing a form.

If you wanted to send multi-language messages in the past, you needed to write complicated workflow conditions or liquid logic. This release makes it much easier to send people messages in the languages that they prefer.

If your workspace identifies people by email or id, we added this setting to make it easier to change people's email addresses. Enabling this setting can help cut down on Failed Attribute Change errors and is on by default for all new workspaces.

Connect your Redshift data warehouse to Customer.io, and import or update people on a regular interval. This integration helps ensure that your workspace always reflects the latest information about your audience.

The first official release of our iOS and Android SDKs is now available. Our SDKs make it easy to identify mobile users, send events from client devices, and send rich push notifications to your mobile audiences—all without writing your own integration from scratch.

You can connect your Microsoft SQL server to Customer.io, and import or update people on a regular interval. This integration helps ensure that your workspace always reflects the latest information about your audience.

You can now capture form submissions directly from Jotform without using Zapier as an intermediary to transform data. To set up a Jotform integration, go to Integrations > Jotform. Copy the personalized webhook URL, add it to your Jotform, and you're all set!

You can connect your BigQuery data warehouse to Customer.io, and import or update people on a regular interval. This integration helps ensure that your workspace always reflects the latest information about your audience.

Data automations accept data of any shape. But, to take advantage of that data, you need to reshape it and associate it with a person in Customer.io. We've made that process easier with the new Create Event action. Use this new action to send messages and segment people based on data from services external to Customer.io!

Now you can segment people by device platform, if you want to start automations or messages based on the device platform(s) your audience uses. You might segment by device platform to let people know when a new feature or version for your app—on Android or iOS, comes out.

You can connect your Snowflake data warehouse to Customer.io, and import or update people on a regular interval. This integration helps ensure that your workspace always reflects the latest information about your audience.

You can now track and segment your audience by screen views in your mobile apps. Use the API to manually track screen views or integrate our iOS and Android SDKs to automatically track screen views.

Now you can schedule your transactional messages up to 90 days in the future, rather than having to schedule your transactional requests at the exact moment you want to send someone a message. This feature helps with things like event reminders, or letting your audience know when a product they expressed interest in will become available.

Our database import feature lets you import and update people from your MySQL or Postgres database. We've recently increased the capacity of imports from 2 million to 10 million rows, making it easier to support large audiences! As a part of this update, we also exposed error files for each sync interval; these files show which rows failed to import, which can help you refine your query or tables and provides a path to import or update people represented by errored rows.

Automations, broadcasts, newsletters, and segments now show their creation date and when they were last edited. We hope this change makes it easier to understand when you started using an asset, and helps you track down issues related to segment, automation, and newsletter changes.

This feature lets you trigger an automation with data of any shape, from any HTTPS source outside of Customer.io. You can transform your incoming data, associating it with a person (as an event), updating a person (with an identify call), or even transform it and send it to a third party.

You can now capture form submissions directly from Typeform without using Zapier as an intermediary to transform data. To set up a Typeform integration, go to Integrations > Typeform. Copy the personalized webhook URL, add it to your Typeform, and you're all set!

We added a Skip duplicate email addresses setting to email newsletters in ID only workspaces. If people in your newsletter audience have the same email attribute, prevents you from sending your email newsletter multiple times to the same address.

You can now connect your MySQL or Postgres database to Customer.io over SSL, helping you securely import data to your Customer.io workspace from external sources.

You no longer need to explicitly share Customer.io sheets with cio_share@customer.io. Now, before you import your first Google sheet, you'll authorize Customer.io to access specific files in your Google Drive. After you grant access, you can easily pick the sheets you want to share from your Google account—to add people, create segments, and update collections—without having to get individual links for each sheet that you want to share with us.

When you query a collection, you can now match against a value in an attribute containing an array of values. For example, if you store your audience's interests as an array in an attribute called interests, you can now query your collection to return data where people's interests include a specific interest—like "cooking" or "football"!

Have you ever wanted to find a Customer.io person in your CRM? Or maybe you need to search for support tickets from a person in your Customer.io workspace. Or maybe you need to call an internal service to activate or deactivate a person's account.

You can now do all of these with our new Shortcut feature.

As automation workflows become larger and more complicated, it can become challenging to read automation logic or remember what each branch, split, and message action does. Now you can leave notes for yourself and others, to help explain your workflow at a glance.

Previously, our Segment Source integration wouldn't send events for people who did not have an ID. Now, if a person has an email but does not have an id, we send events to Segment using the email address as an anonymousId. This lets you map events for leads in Customer.io to another destination.

You can now set your email or ID workspace to automatically merge duplicate profiles based on identify calls that you send to Customer.io. This feature saves you the trouble of having to identify and merge duplicates on your own.

After you start an automation, you can click the automation's Journeys tab to see the most recent journeys that started for that automation. These journeys can help you understand if your automation works the way you expect it to.

You can now segment people based on messages in individual automations. This helps you see which individual people opened a message, or received a specific message in an automation split.

We've added an API endpoint that you can use to merge duplicate people. The payload lets you identify a primary person and a secondary person. The primary person remains after the merge. The secondary person's information is merged into the primary, and then it is deleted.

We added a new message library, making it easy to search for messages in your workspace without having to click through your automations and broadcasts to find them. Go to Message Library to search through your messages.

You can now merge people together, helping you resolve duplicates and accurately represent members of your audience.

Set up a newsletter webhook, sending a request for every member of a newsletter audience. This provides a handy way to trigger in-app messages and other external services based on a segment of people in Customer.io!

You can connect your workspace to a database, providing a convenient way to import and update people on a regular interval. With this integration, you can ensure that your workspace always reflects the latest information about your audience.

Now you can edit, recategorize, and delete rows saved rows in our drag-and-drop editor. This helps you prune saved rows and prevent other members of your team from accidentally reusing stale content! Note that deleting a row does not remove it from existing messages; it only prevents you (and others) from using that row in the future.

Email clients and providers are beginning to provide their users with privacy settings to block open-tracking pixels, etc. This new setting lets you get ahead of the curve and disable email open tracking in Customer.io, both to respect your audience's privacy and hide potentially unreliable open metrics.

Now you can connect forms to your workspace without Zapier, and automatically add or update people who fill out forms on your website. When you connect a form to Customer.io, you map fields on your form to profile attributes, automatically populating information about people who submit your form.

We've reorganized and updated the Automation Overview and Metrics tabs to provide you with a better understanding of your automation's performance. Both pages now provide customizable charts, and you can copy links to your personalized charts, making it easy to share your insights with your teammates.

You can save rows of content in emails that you create in our drag-and-drop editor. This helps you save reusable content, like headers and footers, so that your messages all have the same look and feel without having to re-create message blocks every time you write an email!

In the past, we based all of our metrics on total messages sent. By default, we now base metrics for message statuses that occur after a message is sent (e.g. opened, clicked, etc) on the Delivered metric—the number of messages that actually reach your audience's inboxes. This helps provide you with a more accurate understanding of how your messages perform.

In Email or ID workspaces, you can now add people from a CSV file by email address. Previously, you could only add people from CSV files by ID.

Customer.io now automatically identify people when they click tracked links that send them to pages containing the JavaScript snippet. We append your links with a _cio_id URL parameter to identify people who click tracked links. This feature is on by default when you create new workspaces. If you want to turn this feature on in an existing workspace, go to Settings > Workspace Settings > URL Parameters and turn on the Add _cio_id URL parameter setting.

You can log events before people sign up or log into your site, app, or service. Then, when people sign up or log in, you can associate those events with people. Anonymous events help you do things like personalize your onboarding automations based on things people did before they signed up. For example, if a customer viewed a pricing plan before signing up for a trial, your onboarding automation might cover features relevant to the plan they viewed.

Our JavaScript snippet now automatically captures URL parameters in page view events, helping you retain information about the pages a person views, like filters, search queries, etc.

You can now segment your audience based on URL parameters passed in a page view event. Page view events captured by our JavaScript snippet automatically convert query parameters to event properties you can segment on.

Unsubscribe links generated by Customer.io are now untracked by default. You no longer have to worry about unsubscribe links counting as tracked clicks.

Recently, we added support for workspaces that use both email and id to identify people. Now you can enable both identifiers in your current workspace, saving you the trouble of creating a new workspace to take advantage of this new feature

You can now create workspaces that let you add and identify people by ID and/or email. This lets you incorporate leads and customers in the same workspace, and maintain a history of a person as they graduate from a lead to a customer.

When you select a person, you can now go to the attributes tab and search that person's attributes by name. This can help you find specific attributes when you associate people in your workspace with large amounts of data.

You can now count conversions from webhooks, providing a mechanism to track conversions for messages that you trigger with webhooks in services outside of Customer.io. When you set up a webhook in your automations, toggle Allow conversion from this webhook to count conversions from your webhook.

Twilio supports response keywords, letting people opt-out of SMS messages by replying with keywords like STOP or QUIT. We wrote a script you can use and a quick recipe to help you set up a Twilio workflow to send opt-outs back into Customer.io.

We added an interface for data warehouse integrations, putting you in control of the types of data you want to export and where you want to export your data.

We added the option to disable link tracking in the drag-and-drop editor, so you can exclude unsuccessful click outcomes, like custom unsubscribe clicks, and maintain an accurate click rate. To disable link tracking, just add the untracked class to the button, image, or text link that you don’t want to track.

You can search for team members in your workspace settings, making it easier to determine who has access to your workspace, especially when you have a large team.

You can now send WhatsApp messages via Twilio just like SMS messages. When WhatsApp support is enabled, you can compose WhatsApp messages with customer data, and preview the output directly in our Twilio composer.

Set up a Facebook Lead Ads integration automatically adds people to your email-based workspace when they fill out Facebook Lead Ad forms. You can also trigger automations whenever people fill out Facebook Lead Ads, automatically sending follow-up messages to nurture conversions.

We also made it easier to copy entire workflows across automations and workspaces, helping you reuse your most successful messages and workflows. You can copy entire or partial workflows to or from another workflow using the Copy to and Copy from options.

We added the ability to select, move, copy, and delete multiple workflow items so that, in just a few clicks, you can copy and move blocks while preserving their structure. The workflow builder supports both hotkeys and click-and-drag functionality, so you can select and modify items using the input method that works best for you.

Now when you A/B test your newsletters, you can create segments of recipients based on the variation of the newsletter that they received. These segments can help you tailor follow-up messages based on the test variant that each member of your audience received.

You’re probably used to identifying people by ID—a value that represents your audience as customers. Now you can identify people by their email addresses, helping you start conversations with people before they make a purchase, create an account, or subscribe to your service.