Release Notes

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.