Release Notes

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.

While in beta, we’ve made some major improvements to our in-app solution:

• We’ve improved our UI, making it a little easier to compose in-app messages
• Lowered response times for in-app messages, ensuring that your audience receives messages when they’re most relevant.
• Removed the need for an organization_id in integrations, so it’s easier to get started with in-app messages.

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.

In the improved editor, you can:

• See all the settings in a block without having to “reveal” or “hide” things.
• See how your padding and font changes affect your message in real time.
• See a list of available font and color settings with examples.
• Rename blocks and cards in your template so it’s easier to explain what each block or group of blocks does.

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 campaigns! This makes it easy to onboard new people when they join a company, sign up for a new course, and so on!

We’re committed to supporting one-to-many, and eventually many-to-many, relationships using objects. Stay tuned for updates as we continue working on this new feature!

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!

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.

This helps you maintain a better understanding of your audience’s devices, so you know which devices are relevant and can get a real device count—without having to clean up old devices yourself.

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’re committed to releasing, maintaining, and supporting Flutter. Try out our new SDK and let us know what you think. Your feedback helps us understand your needs, so that we build our SDK(s) and associated features to fit your needs.

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 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, we had a complicated recipe to perform holdout tests, but it involved sending real messages to a black hole address, which wasn’t ideal. Now you can set up holdout tests with a simple checkbox!

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.

Now, we attempt to perform sync operations on your exact interval without regard to the time it takes to complete an import operation; if we’re still importing from your database on a sync interval, we’ll skip it (showing a skipped status in our UI), and try again at the next interval. This adds predictability to your database sync integrations, so you’ll always know when you can expect to see your data in Customer.io.

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.

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.

See our Amplitude and Mixpanel pages for more information about these integrations.

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.

With this feature, you can use a path beginning with a set of characters (begin*), ending with a set of characters (*end), or in a path (https//example.com/*/billing).

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!

As a part of this release, we’ve also changed the default expiration period from 365 days to 30 days.

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 a campaign conversion, you can now compare your conversion event to your trigger event. This is a great way to determine the success of your campaigns based on related events.

For example, imagine that you start a campaign when someone begins an educational course; maybe your event is called course_started, and it has a course_id that you use to identify different courses you offer. Your campaign’s goal is to help someone finish the exercise, so you need to look for an event called course_completed with the same course_id. That kind of comparison is now possible, and you can use it to your advantage to pinpoint highly-specific conversion criteria!

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.

See the Delivery Content schema for information about the new table in v4. Go to the documentation link below for help updating to v4.

In the past, if you wanted to reuse a newsletter or broadcast 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 and broadcasts to other workspaces!

When you go to create a campaign, you’ll notice some changes to our campaign Trigger page. We’ve redesigned this step in the campaign 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.

This feature also adds the ability to export a list of devices. You might export devices to clean up bounced or suppressed devices.

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’re rolling the new rich push editor out to accounts over the next week. Contact product@customer.io if you want to start using it today.

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.

For example, if people enter your campaign when they create an appointment, you might send them a reminder before their appointment. You can use an event parameter-based wait condition to make sure that someone hasn’t cancelled their appointment before you send the reminder!

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

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 Twilio SMS messages to increase engagement with your mobile audiences in the United States and Canada.

When you set up an SMS message, you can add the URL of a JPEG, PNG, and GIF image. You can send images up to 1.5MB to people with phone numbers in the United States and Canada. In general, we recommend that you limit images to 1MB or less, so that everybody in your audience can see them regardless of their connection speed.

Earlier this month, we added the ability to track conversions for Campaigns 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.

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.

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

Click in the upper right of the workflow to export your workflow as an image.

We’ve updated our Wait until… campaign 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 campaign. 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 campaign until it’s time to send them follow-up reminders!

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

When you write messages in your campaign, you’ll set up a default message and click Add language to set up localizations of your message. When people enter your campaign, they’ll receive messages matching their language attribute. People who don’t match a language in your newsletter receive the default message.

Localized items in your workflow show the icon.

This makes it easier to localize messages in your campaigns, and generates unified metrics from localized messages, making it easier for you to tell how your message perform with your audience.

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.

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

• The Processing Queue automatically queues and batches requests, saving your audience’s battery life and automatically handling errors for you.
• The SDK now automatically captures a set of Device Attributes and grants you the ability to set your own, custom attributes for each device you register with Customer.io. You can use these properties in segmentsA segment is a group of people in your audience that you want to target with campaigns, messages, etc. You can join groups of people manually, or by attribues and event data., helping you target members of your audience.

If you use a previous version of our SDK, this release introduces breaking changes. See the our migration documentation for help updating your integration.

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

Like other form integrations, this feature also lets you trigger campaigns when people fill out your form, so you can automatically respond to your audience with information relevant to the forms they submit.

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

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.

For example, where you might have checked if a variable existed by writing a complicated Liquid if statement, you can now write simple JavaScript instead!

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

Our SDKs gather these attributes automatically, but you can also set them when you add and update devices using our API. The last_status attribute is set automatically based on the delivery status of the last message sent to the device—sent, bounced, suppressed, or an empty string if the device hasn’t received a push notification before.

We’ve updated our Data & Integrations > 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.

If you’re currently integrated with “beta-api” endpoints, you can continue to use those routes, but we encourage you to update your integration to use the new https://api.customer.io/v1/ paths. Beta API endpoints will continue to work, but we may eventually deprecate and remove them in the future (with advanced notice).

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 campaign workflow. You can also update someone other than the person currently in the campaign 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 Campaign

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 campaigns, helping you narrow your scope when you look for a message. Go to Content > Message Library to search through your messages.

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

This release also makes it easier to add properties to your events, letting you click to select the values that you want your event to include so you don’t have to write liquid.

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.

We developed and tested Wordpress form support with the WPForms plugin. You may be able to capture forms from other form plugins in Wordpress, but we cannot guarantee that they’ll work. Let us know if you use a different plugin and run into compatibility issues. We’ll do our best to support your use case.

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.

In workspaces created before today, if you use both email and id to identify people, you needed to use cio_id to change either value—a value that you might not have available to your integration. This setting lets you change email values with id, making it easier to modify your audience without preventing you from identifying people by their email address.

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.

When you set up a sync, you provide a query determining the information that you want to reflect as attributes on people in Customer.io. You’ll also set the frequency of import operations from your Redshift instance. On each interval, you’ll import and/or update people in your workspace from your Redshift database!

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.

When you set up a sync, you provide a query determining exactly what information you want to reflect as attributes on people in Customer.io. You’ll also set the frequency of import operations from your Microsoft SQL instance, helping you keep your workspace up to date.

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 Data & Integrations > Integrations > Jotform. Copy the personalized webhook URL, add it to your Jotform, and you’re all set!

Now you can segment people by device platform, if you want to start campaigns 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.

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

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.

Campaigns, 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, campaign, and newsletter changes.

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 Data & Integrations > 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”!

As campaign workflows become larger and more complicated, it can become challenging to read campaign 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 segment people based on messages in individual campaigns. This helps you see which individual people opened a message, or received a specific message in a campaign split.

When you create a segment, select the message type under Message Data. Then you can click Any , and search for the campaigns or individual messages that you want to segment on by name.

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

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 campaigns and broadcasts to find them. Go to Content > Message Library to search through your messages.

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!

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.

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!