Release Notes

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

You can only modify the trigger type when the campaign is in a draft or stopped state. This ensures you have time to review and update any workflow items impacted by a change to your trigger.

If you need to make changes before you start the campaign, you’ll see warnings under each action block needing attention.

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

You can create and send a newsletter in a single request, or use the Send a newsletter and Schedule a newsletter endpoints when a draft is ready. You can pass optional rate limits on both calls.

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

From the Home dashboard, you can see message performance at a glance and take action on your workspace. Pick up where you last left off or select a suggested action to get started.

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.

In the past, our AI Assistant was limited to specific tools. But the new agent can do just about anything you can do in Customer.io. It can create campaigns, draft emails, analyze campaign performance, and more. It can even learn from you and get better over time!

You can also set up Routines to automate recurring tasks—things like checking your deliverability, auditing segments, and more.

And while we’ve expanded the agent’s capabilities, we’ve also given it guardrails to make sure it works safely. It’s limited to your permissions, and it has approval flows to make sure it doesn’t do things you don’t want it to do.

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 campaigns, segments, templates, broadcasts, and more. AI-enhanced ranking surfaces the most relevant results—even if you don’t type an exact match.

Note that this feature does not search for people, objects, or their data. To find people, you’ll continue to use the activity log, people page, or segments.

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.

You can also use this dashboard to optimize your workspace before issues arise! Go to > Workspace performance to get started.

Goals let you define specific outcomes you’re optimizing for—a purchase, a subscription upgrade, etc.—and measure achievement across campaigns and broadcasts.

Unlike campaign-specific conversion goals, you can now track outcomes that span multiple workflows to help you more holistically strategize around your messaging and data.

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

You can use LLM actions to personalize messages, enrich data, and create conditions to help you reach the right audience.

Each time an LLM action runs, it uses AI credits. Learn more in Billing.

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

Channel preferences add a new layer of subscription control to your subscription center. Where topic preferences let people choose what they hear about, channel preferences let them choose how they receive messages.

You can set up channel-based subscription preferences for any messaging channel you have enabled in your workspace.

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.

Click Live Preview when working on your in-app message to get started. We’ll open your website in a new window where you can see and adjust your message in real time.

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.

Previously, you could only set a fixed send rate for newsletters—a consistent number of messages per minute, hour, or day. If you needed to warm up a domain, you had to manually create separate newsletters for each period of your warm-up schedule. Now, domain warming is less manual and easier to set up!

We’ve also increased the maximum newsletter send time to 60 days to give you more room for gradual warming and large sends.

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.

Entri supports over 50 DNS providers, including GoDaddy, Namecheap, Cloudflare, and Amazon Route 53.

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.

This is especially useful if you manage multiple brands, want to rotate domains, or want to separate domains by message type.

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

Rate limiting lets you control how quickly your newsletters go out, which can help reduce the load on your downstream systems and maintain deliverability, so we want to make sure you can limit sends when it makes sense for your business.

On the Review step of a newsletter, you can now turn on the toggle Limit send rate when your newsletter has multiple language variants.

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 withoout manual copy/paste. It also enables you to programmatically add email translations.

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

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

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

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

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

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

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

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

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

Location tracking is available in all our mobile SDKs:

• iOS
• Android
• React Native
• Flutter
• Expo

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.

Learn more about these preview settings and how to make your design more consistent in email clients that don’t support dark mode styles.

These preview settings are available in our latest email editor, Design Studio, and our Code-only editor.

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

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

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

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

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

You’ll also see a few other enhancements:

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

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.

Multi-lingual messaging is essential for global markets, and now Design Studio can help you reach them without cumbersome branching in campaigns. Reduce time spent copying content between tools, and scale personalized messaging with less overhead.

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

You might use this to set static data, like a discount code, that only applies while your customers are in the campaign.

This means you can now set journey attributes based on webhook data, collection queries, and a workflow action designed specifically for journey attributes.

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!

WhatsApp messages are based on templates approved by Meta. You’ll create templates in your Facebook/WhatsApp Business Account and then use them to send messages from Customer.io.

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

Large assets cause emails to load slowly, impacting success of your campaigns. With optimization, you can ensure graphics appear quickly (even on poor mobile connections) to prevent drop-off from blank screens and protect click-through rates.

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!

This means you can now temporarily store data from both collections and webhooks to keep your customers’ profiles as lean as possible.

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

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

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

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.

For best results, generate subject lines after your email content is complete!

This feature only applies to subject lines, not preheader/preview text.

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.

While message creation requires fine-tuning, it shouldn’t interrupt your creative flow. Previously, refining Design Studio emails or in-apps—like the padding on four different buttons—required you to go through a cycle of repetitive, manual adjustments. Now you can do this in a single, fluid motion: click, drag, and change your styles.

To make edits across multiple components, click and drag your cursor on the canvas to select multiple components.

Learn more about editing multiple components in Design Studio and in-app messages.

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

Why it matters:

• Less repetitive work & fewer errors. Define your webhook URL, headers, and auth details once, and reference them in any campaign.
• Updates at scale. When an API endpoint or auth header changes, update the configuration in one place and all referencing campaigns pick up the change automatically.
• Tighter security. Team members can select pre-configured webhooks without ever seeing sensitive data like API keys, auth tokens, or headers.

Only Account and Workspace admins can configure reusable webhooks.

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

• Help & Support now available everywhere: The Need Help? option was missing on some pages. Now it’s available on every page.
• Simplified support form: We’ve made the Get Help form easier to find and use—now it’s a single screen rather than four separate pages. You can even generate the form’s subject line with AI!
• Featured videos: We’ve added videos to help you learn more about Customer.io.
• Better organization: Resources, education, and support options are grouped into clear categories.
• Improved support access: You can now set the duration of support access to your workspace (3-180 days), and we’ll show you the exact date that support access expires.

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!

This means you no longer have to store webhook data important to a person’s journey on their profile, which doesn’t expire and could clutter up your workspace.

Our new Audit Logs give you visibility into team actions across campaigns, 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, campaigns, and other data in your account.

You must be an Account Admin to access Audit Logs.

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!

Under normal priority, Android devices in standby mode might not wake up long enough to send delivery metrics back to Customer.io, so you might not see messages as delivered until your users open your app. Setting High priority tells the recipient’s device to wake up to properly report delivery metrics!

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.

Create roles in Account Settings to give external partners, developers, or marketers just the access they need, nothing more.

You must be an Account Admin to create and assign custom roles.

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

This can help you greatly simplify workflows if you’ve added branches with a variety of time delays to achieve the same effect.

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

To link sticky notes to workflow items: Click the icon on the note and drag it to the workflow item you want to attach it to.

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

You can ask our assistant about:

• Segment conditions: “When do people enter my Onboarding segment?”
• Campaign performance: “What’s the click-to-open rate for my Onboarding campaign and how does that compare to my Welcome campaign?”
• Email template/content analysis: “Are there any issues with my email template that might affect performance with my audience?”

You can combine these things as well. For example, you might request information about a campaign and then ask the assistant to analyze the emails in the campaign for issues that might affect performance or deliverability.

Our Random Cohort feature lets you test different messages or actions in a campaign 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 campaign 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.

This feature works great with our other new feature: Automatic Geolocation Data Collection. This helps you gather your audience’s time zone data, which you can use to produce better send time recommendations!

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.

Our JavaScript client and mobile SDKs automatically capture IP addresses for you, making geolocation easy.

If you use our backend libraries (like our Node.JS or Go SDKs) or our Pipelines API, you’ll need to:

1. Go to your integration’s Settings tab and turn on the Enable Geolocation setting.
2. Capture the IP address yourself and pass it in the context.ip field in your identify requests.

This setting is on by default for workspaces in our US data center and off by default for workspaces in our EU data center. If you’re in the EU data center, you’ll need to enable it under Workspace Settings > Time Zone & Geolocation Settings.

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.

While Salesforce filters typically require a SQL syntax, we’ve included a handy AI box, where you can describe the data you want to bring into Customer.io and we’ll generate a filter for you.

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.

Here are some examples of how you could use this feature:

• Upload an image for your emails and request the Assistant generate alt text.
• Upload charts from a third-party analytics tool and request it come up with recommendations based on the data.

If you use collections, you’re probably used to finding them in Content menu. We’ve moved them to Data & Integrations > Collections because they’re much more like 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.

If you haven’t used collections before, now’s a great time to start! Collections let you store data that you want to use in campaigns but isn’t necessarily associated with people or objectsAn object is a non-person entity that you can associate with one or more people—like a company, account, or online course.. These could be things like available promotions/coupons or upcoming events your audience might be interested in.

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.

You can even use inline content to populate your app for users who haven’t signed up or logged in. This helps you show default content to people who use your app but aren’t identified yet.

Update to one of the following versions of our SDKs to get started. You don’t have to make any changes to your app code—just update the SDK.

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 upgraded the Assistant so it can answer high-level questions about your campaign and broadcast metrics! You can also retrieve metrics through our MCP server.

Ask it questions like “Which campaign had the lowest deliverability this month?” or “What’s the average click-to-open rate for my campaigns?” and it will search our docs and your workspace to give you a relevant answer.

Click at the top of your workspace to get started!

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.

This is our first release of a component that captures form data like this, but we’re working to expand support for more complex surveys and forms in the future.

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.

You can auto-translate across all message channels, but it’s not yet available for emails made in Design Studio.

Not seeing this option? Check that Customer.io AI is enabled in Privacy, Data, & AI settings.

Analyze your content to help you catch typos, improve tone, and strengthen your message before sending. While editing an email in a campaign, 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 also create segments from the Assistant. Describe your criteria, and it will build a segment you can use to trigger campaigns or group members of your audience.

At the top of your workspace, click the message bubble to get started. Make sure Customer.io AI is enabled in Privacy, Data, & AI settings to access the full experience!

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

Any campaign with a scheduled start or stop time will show a label “Scheduled” alongside the status (Draft, Running, or Stopped).

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!

Go to your Data Index, select an attribute or event, and click in the description field to generate a description.

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!

Pro tip: add descriptions to your attributes and events to improve segment generation! Providing additional context on your data helps our segment builder better understand your data and provide more relevant results.

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.

Authors with sensitive data hidden have the same functionality as authors who can view all data, with one exception: they can’t edit people.

If you currently use our legacy “Hide all attributes” setting, your teammates will experience no change to the data and functionality they have access to.

You can now create campaigns 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.

All campaigns that use our legacy segment trigger will continue to work as expected and you’ll be able to duplicate them. For new campaigns, you’ll use the new trigger.

Note, the new trigger behaves differently than the legacy segment trigger in a few ways: filter conditions are now part of the trigger conditions, and you may need to add time-based conditions to ensure the right group of people trigger your campaigns at the correct time.

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.

You can opt out of this builder and revert to our standard experience through the toggle in the bottom right of segment creation.

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

If you’ve used a beta version of the plugin, you’ll notice that the official release includes support for Firebase Cloud Messaging (FCM) to iOS devices, and we’ve tried to slim down the workflow to make integrating even easier. Check out the changelog to see the complete list of Expo updates.

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.

Before this release, you had to copy/paste content from Twilio into Customer.io before you could send a WhatsApp message. Now, when you add a WhatsApp message to a campaign or broadcast, you can simply select your Twilio content template. We fetch the template and expose the fields you can fill in so you don’t have to leave Customer.io.

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.

Go to Workspace settings > SMS and turn on Shorten links. Shortened links use the format https://a.cx.io/lnk.abc123 (or https://e.cx.io/lnk.abc123 if you’re in our EU region), consuming between 28 and 38 characters so you have plenty of room to talk to your audience.

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 campaigns! Previously, you could only trigger these campaigns for people who matched your trigger after the campaign started. Now you can trigger these campaigns for people who already match your campaign trigger when the campaign starts. For instance, if you trigger a campaign 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.

This feature is in early access and is available only to customers who are using our iOS Native SDK. Interested in joining our early release program? Fill out this form to request access. If you have questions, please let us know.

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 campaign 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 campaign 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 campaigns will continue to work as expected.

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

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

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.

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 & Integrations > Data Index in your workspace. You must be a Workspace Admin to export your data index.

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.

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.

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

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.

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 profiles. 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 profile setting, go to Add a sync > Step 4. For more on interval calculation, go to Sync intervals and skipped syncs.

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, go to Data & Integrations > 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 campaigns! Check that your CSV is correct before initiating import.

You can now retrieve and update translations of messages using our App API. This includes campaigns, 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.

You can now hide profile and event attributes 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 Prevent this person from viewing profile and event attributes. Authors with reduced access cannot manage segments, objects and relationships, or webhooks. They also cannot edit people or attribute conditions for broadcasts.

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 hide profile and event attributes 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 Prevent this person from viewing profile and event attributes to on.

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 campaigns and broadcasts simultaneously. Note, to enable your subscription center, all your running campaigns, 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.

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.

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.

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.

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.

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 use liquid syntax to set the expiration date for an in-app message. Use event properties, profile attributes, snippets, and more. For example, if you want an in-app message to expire based when an online course is scheduled to start, you can use liquid syntax to set the expiration date to {{event.class_start_date}}.

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.