Release Notes
Check out the latest features and fixes for the Customer.io platform. This page covers releases beginning in 2021. Go to our blog to see a history of releases before 2021!
Want to see what we're working on? Take a look at our roadmap!
Reorganize in-app messages with drag-and-drop
Ui improvements
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.
Go to the docsJump to components in your in-app messages
Ui improvements
In-app messages often contain groups of nested components, which can make it hard to find the part of the message you want to edit. That’s why we added a new panel to our in-app message creator: to help you easily find and jump to the parts of your message you want to edit.
With the new message navigation panel, you can:
- See the structure of your message at a glance
- Click to a component to go directly to it in your message
- Hide and show components, making it easier to focus on what matters
Assign subscription topics in bulk to live campaigns and broadcasts
Ui improvements
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.
Go to the docsData Pipelines is live!
API developers Cdp
Customer Data Platforms (CDP) are a great way to get data into Customer.io, but they become expensive as you grow. We wanted everyone to be able to afford access to clean, unified data, so we built our own CDP: Data Pipelines. Now you can easily and affordably collect, transform, and send data to Customer.io, and all the other tools in your stack.
Read more
In-App Microsurveys
Messaging Ui improvements
In-app messages are a great way to connect with people who are already engaged with your app, but it hasn’t always been easy in Customer.io to build or track in-app messages with multiple choices. With our new Microsurvey components, we’ve made it easier to send messages with quick, recognizable calls to action. This release also adds the ability to track responses to your in-app messages and surveys.
Read more
Track metrics for subscription center topics
Messaging Ui improvements
You can now view unsubscribe rates for subscription center topics when viewing Performance & Delivery Metrics or Message Metrics for campaigns and API-triggered broadcasts within the Metrics tab. For newsletters, go to the Overview tab. You can also compare metrics through your Analysis Dashboard. This data can help you determine subscription topic interest by monitoring unsubscribe rates.
Go to the docsReact Native SDK 3.0
Mobile sdkReact 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.
Go to the docsPre-built blocks for in-app messages
Messaging Ui improvements
You can now add pre-built blocks to your in-app messages to save time constructing message frames, buttons, and rounded images! Select from the component dropdown to get started.
Go to the docsOverride a subscription topic for a message
Messaging
You can now override a subscription topic at the message level. Within a campaign, select an email then select a different topic from the Subscription Preference dropdown. This way, you can target different audiences within a single campaign.
Go to the docsWe’ve made our in-app editor more intuitive
Messaging Ui improvements
We’ve made a series of improvements to our in-app message editor that make it easier to build and preview your message.
- Sticky preview: The preview stays in view, so you can see your message as you edit it.
- Expanded editing space: We increased the size of the in-app message editor and reduced the impact of other UI elements, making more room for you to work on your messages.
- Expand and collapse elements: The hierarchy of elements in your message are clearer, and elements aren’t hidden by default when you start a new message from a template. You can also collapse and expand parent elements without collapsing children, making it easier to focus on the elements you’re working on. Collapsed areas save with your message, so you can pick up where you leave off.
Create a custom subscription preferences page
API developers Data integrations MessagingYou can now create your own, custom subscription preferences page by fetching preferences from our App API and updating them through our Track APIs. This gives you full control over the branding, formatting, and location of your subscription preferences page.
Go to the docsIncreased support for SSO providers
Data integrations
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.
Go to the docsDismiss in-app messages at the right time
Mobile sdkWe’ve added functions to all of our SDKs to manually dismiss in-app messages. This is especially helpful in handling custom actions, so you can dismiss messages after your audience interacts with a custom button or link. You can listen for message interactions and then perform dismissals based on the actions users take in your messages.
Go to the docsCustomize the order of subscription center topics
Messaging
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.
Go to the docsRelate objects to people in the UI
Messaging Ui improvements
You can now add and delete relationships between objects and people in the UI, which allows you to explore objects without engineering. You can use relationships to segment users and to personalize messages with object data.
Go to the docsSecurely verify requests for webhook actions
API developers Data integrationsYou 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 Data & Integrations > Integrations > Reporting webhooks.
Go to the docsMulti-language support for the subscription center
Messaging
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.
Go to the docsSSO with Microsoft Azure Active Directory
Data integrations
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.
Go to the docsBrand your global unsubscribe page
Ui improvements
You can now update the branding of your global unsubscribe page! Go to Settings > Workspace Settings > Subscription Center to add a logo and/or update the background color of your Unsubscribe button. If you have not enabled our Subscription Center, your users will see this page after selecting Unsubscribe.
Go to the docsSend transactional push notifications
Messaging
Easily create, personalize, and measure your transactional push notifications with our Transactional Push API. Need to add an image or deep link or send in multiple languages? No problem — make updates to your transactional messages without changing a single line of code.
Go to the docsProtecting your account via 2FA
Admin billingTo protect accounts on our platform, we’ve enabled two-factor authentication (2FA) for all accounts that do not use SSO. If you’ve already enabled 2FA via authenticator app, there will be no change to your sign-in pattern. If you have not enabled 2FA via auth app and do not use SSO, you will now verify your log-in attempt through an email from us here at Customer.io. Just make sure you click the emailed link on the same browser and device on which you attempted to sign-in, and you’ll be good to go!
Go to the docsAdd dynamic expiration dates to in-app messages
Messaging
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}}
.
Data Pipelines now available in early access
Cdp
For the past decade, we’ve helped companies use their data to connect with their customers. We know that data management can be a headache and have long recommended using a customer data platform as standard practice. For years we’ve also been building features to help you manage data, including Reverse ETL, custom objects, and a sync to data warehouses. Today we’re announcing the next step in that work: Data Pipelines. Data Pipelines connects your customer data to every product in your tech stack, letting you focus on what matters most: building relationships with your customers.
Read more
Allow partial updates to subscription preferences
MessagingYou 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.
With this update, you can also import each subscription topic preference as its own attribute via CSV.
Go to the docsOfficial Flutter SDK release
Mobile sdkOur Flutter SDK has been in beta for the past couple of months. Now that we’ve smoothed out the rough edges, our 1.0 release is ready for use in your production apps.
Our Flutter SDK supports all the same features as our other SDKs, including in-app messaging, support for images and links (rich push), and the ability to send events from your audience’s devices. As an officially-supported SDK, we’ll continue updating our Flutter library to support both OS updates and new features that we expose in Customer.io.
Go to the docsSend pushes to iOS devices with the default sound
Mobile sdk
When you use our SDKs, you can now send push notifications to iOS devices that use the default system sound, alerting your audience when they get a new message. This affects all of our SDKs that support iOS, including React Native, Flutter, and our Expo plugin.
This only adds support for the default system sound. Our SDKs do not yet support custom sounds.
Go to the docsAMP for email
API developers Messaging Ui improvements
We’ve added support for AMP components to our email code editor! Validate AMP and send test emails from within your workspace.
AMP lets your customers complete surveys, RSVP to events, respond to comments, and more within your emails. Visit Amp.dev to find templates and components for your use case.
Toggle these experimental features on in Account Settings to get started: Advanced Code Editor and AMP for Email.
Go to the docsImport Objects and Relationships in Reverse ETL integrations
Data integrations
Now you can sync objects (like companies, accounts, or online classes) and relationships as a part of our Reverse ETL database integrations—MySQL, BigQuery, Snowflake, and so on. Now you can easily add objects and relate them to people on a regular interval based on business logic and data that you store outside of Customer.io.
Go to the docsOfficial In-App Messaging Release
Messaging Mobile sdkWe’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.
In-app settings: moved and improved
Ui improvements
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.
Rename your in-app messages
Ui improvements
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!
Go to the docsCustomize your subscription center
Ui improvements
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.
Go to the docsSupport for object-based segments in campaigns
Automation
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!
Go to the docsMessage limits with automatic retries
Automation Messaging
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!
Go to the docsObjects: a new way to group people together
API developers Automation Data integrations
We now support objects—non-people data that you can relate to people, like accounts that people belong to, flights they’ve booked, online courses they’ve enrolled in, and so on. This release is only the beginning. Support in this release is limited to a single object type and they’re limited to Newsletters, but we’re actively working on this feature to add support for more objects, campaigns, and object-to-object relationships.
Read more
Build a subscription center the easy way
Automation Messaging
We’ve added a subscription center feature that can help you manage your audience’s subscription preferences without having to manage a complicated set of preferences on your own. This feature makes it easy to set up your subscription topics, apply those topics to campaigns or broadcasts, and let your audience decide what topics they want to subscribe to.
Read more
Automatic device cleanup
AutomationPeople 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.
Go to the docsSend batch requests with our v2 API
API developersWith 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.
New Flutter SDK in Alpha
Messaging Mobile sdkIn 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.
Go to the docsSend in-app messages to mobile or web channels with in-app page rules
Messaging Mobile sdk
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.
Go to the docsTrue holdout tests
Automation Messaging
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!
Go to the docsSend transactional messages by Trigger Name
Data integrations Messaging
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
More predictable database-sync intervals
Data integrationsIn 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.
Multi-language transactional messages
Messaging
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.
Go to the docsStore and reuse images with the Asset Library
Ui improvements
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.
Go to the docsSet wildcards for in-app page rules
Messaging Mobile sdk
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
).
Expire in-app messages in hours or minutes
Automation Mobile sdk
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.
Go to the docsOfficial React Native SDK release
API developers Mobile sdk
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.
Go to the docsCompare conversion events to your trigger events
Automation
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!
Export delivery content to your data warehouse
API developersWe’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.
Upgrade to v4 to use subjects and outputs
We’ve made some minor changes to subjects and outputs a part of our v4 release. If you’re using a previous schema version, we disabled your subjects and outputs on October 31st, 2022. You need to upgrade to schema version 4, to continue syncing outputs and subjects data.
Copy broadcasts and newsletters across workspaces
Ui improvements
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!
Go to the docsWe’ve updated our campaign trigger page
Messaging
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.
Go to the docsExport duplicates and devices for troubleshooting purposes
Admin billing
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.
Go to the docsSend rich push messages without writing custom payloads
Messaging
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.
Go to the docsWait until an event matches properties
Automation
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!
Go to the docsUse nested attributes with our simplified UI
Automation
In a previous release, we exposed the ability to use JSON dot notation to access nested attributes and event properties in segments, filters, etc. But what if you’re not a developer or familiar with JSON? This update adds some simple options that can help folks traverse nested attributes without needing a deep understanding of JSON and related terms!
Read more
React Native SDK in Open Beta
Mobile sdkYou 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!
Go to the docsAdd people in bulk via the API
API developersThis 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.
Preview messages in your workflow
Messaging Ui improvements
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.
Email code editor using Parcel
API developers Messaging
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!
Go to the docsExperimental feature: Parcel email code editor
API developers Messaging
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.
Read more
Twilio MMS Support
Messaging
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.
Go to the docsEvent conversions for newsletters
Automation Ui improvements
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.
Go to the docsSegment and filter against complex arrays and JSON
Automation Ui improvements
In the past, you weren’t able to create segments or use complex JSON attributes (arrays, nested objects, and arrays of objects) in filters, branch conditions, etc. This forced you to flatten your attributes and events to fit the sorts of segments you wanted to create, which could take a lot of effort and planning. Now, you can use complex JSON in conditions, making it easier to use your data and segment your audience without reshaping your data.
Read more
Upload events via CSV
Ui improvements
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.
Go to the docsExport your workflow as an image
Ui improvements
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.
Set up Wait until delays based on attribute and event conditions
Automation Ui improvements
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!
Go to the docsLocalize campaigns and broadcasts without complicated workflows!
Automation Ui improvementsTo 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.
Go to the docsiOS SDK 1.1.0 release
Mobile sdkWe’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.
Go to the docsAndroid SDK 2.0 release
Mobile sdkThis 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.
Go to the docsSegment Source integration now supports all channels
Data integrations Ui improvements
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.
Go to the docsTry out new experimental features
Ui improvements
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!
Go to the docsExport your data on regular intervals to Microsoft Azure Blob Storage
Data integrations
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.
Go to the docsCapture custom metrics in periods longer than 120 days
Ui improvements
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.
Go to the docsSubmit forms without writing code
Data integrations
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.
Go to the docsBatch update: update a group of people related to an account, order, job, or another object
Data integrations Ui improvements
Our new batch update action makes it easy to handle one-to-many relationships, like an account with multiple users or a product update that a group of people are interested in. With a batch update, you can associate a single incoming piece of data with, and even send messages to, a group of people.
Read more
Schedule your database sync start time
Data integrations
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.
Segment and filter people based on device attributes
Automation Mobile sdk
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.
Read more
See where Snippets are used
API developers Ui improvements
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.
Go to the docsUse Javascript to personalize actions
API developers Ui improvements
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 %}
Segment and filter on device attributes
Ui improvements
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.
Updated integration catalog view
Ui improvements
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.
Beta API official release
API developersThe 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).
Create or update people in your workflows
Ui improvements
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
Go to the docsFilters in the Message Library
Ui improvements
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.
Go to the docsCreate event in any campaign
Automation Ui improvements
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.
Go to the docs