Release Notes

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.

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

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

To use these new exports, simply go to your data warehouse integration and turn on the Campaign Metadata, Objects, and Object Attributes outputs.

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):

• iOS SDK 3.4.1 or 2.14.2
• React Native SDK 3.9.1
• Flutter: follow our instructions to update your iOS Native dependency version 2.14.2.

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.