Release Notes

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.

If you already set them up with the To field, you have nothing to worry about. We’ve taken care of things for you. Your messages will go to the right person, whether you identify them by ID or email address.

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

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.

We’ve added a handy sample app to our iOS SDK, so you can see what Customer.io looks like in VR. But, if you’ve developed an app with our mobile SDK already, our visionOS support should come naturally to you.

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.

• iOS: ≥ 3.1.0 or ≥ 2.13.0
• React Native: ≥ 3.6.0
• Flutter: requires iOS ≥ 2.13.0. Follow our update instructions to update the iOS native package in Flutter.
• Expo: requires React Native ≥ 3.6.0. Install the latest React Native SDK and run expo prebuild --clean.

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 Manage Domain 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 know that liquid is complicated, even moreso when you need to reference objects, relationships, and people in the same message. To make things easier, we built a tool that uses AI to generate your message and liquid for you.

Because AI features are tricky, we’ve made this an Experimental feature so you can use it if you’re comfortable taking advantage of AI-style features. To enable the feature, go to the icon in the upper right corner and click Experimental Features. From here, you can enable Email Content for Object Campaigns.

Then, in campaigns triggered by objects or relationships, you can click Generate with AI to generate messages and associated liquid. The AI tool works like most AI-chat applications, so you can continually refine your prompt to get the results you want. Then copy the results into your message and you’re ready to go.

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 appreciate your feedback and are always looking for ways to improve our product—whether by adding new features or fixing recent changes! If you have feedback on this or any other feature, please let us know.

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.

This release updates the platforms below. We’ve linked to upgrade documentation for each SDK, highlighting the code you can remove from your app when you upgrade:

• iOS 2.11
• React Native 3.4
• Flutter (affects iOS native SDK)
• Expo: Upgrade to 1.0.0-beta.14 and run expo prebuild --clean.

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.

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.

Your toolbox in Customer.io just expanded! You can now trigger campaigns 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 Campaigns in the left hand navigation and click Create Campaign in the top right to get started.

We revamped our campaign creation experience so that it is easier for you to find and refine the triggers you need. Go to Campaigns in the left hand navigation and click Create Campaign 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, 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.

Until now, if you wanted to take full advantage of Data Pipelines and send in-app messages to your web audience, you may have had to use both our Data Pipelines JavaScript SDK and our Journeys Web SDK. Handling multiple SDKs for the same platform can be a pain, so we’ve added in-app support to our Data Pipelines JavaScript snippet. Now you can do everything in Customer.io with a single JavaScript SDK.

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