Release Notes

You can now export object and relationship data from the people or object summary pages as well as from individual people and object pages. This gives you flexibility to share this data with your colleagues that do not have access to Customer.io.

By default, our in-app messages have a maximum width of 414px—a common breakpoint for mobile design. But that might be too narrow for non-mobile mediums, like your desktop website. Now you can set a custom max width for in-app messages, expanding your message on larger screens while still being responsive when your message appears on screens smaller than the max-width value.

By default, we display modal in-app messages on top of a background overlay colored black with 20% opacity. Now you can customize the modal overlay color and opacity to better fit your brand and ensure that your messages are accessible to all of your users.

You can now hide profile and event attributes from team members with the Author role to limit who has access to personal information in your workspace. Admins can manage this setting in Account Settings > Team Members. When creating or editing a team member with the Author role, toggle on Prevent this person from viewing profile and event attributes. Authors with reduced access cannot manage segments, objects and relationships, or webhooks. They also cannot edit people or attribute conditions for broadcasts.

If your account is in our European Union region, you can now take advantage of Data Pipelines to send data from your various sources to destinations where you can activate that data. Now our full suite of features—both Journeys and Data Pipelines—are available to you, wherever you are.

Now you can set up multiple page rules for an in-app message, making it easy to show your message on any page relevant to your message and audience.

The Zendesk destination helps you identify your users, so you can keep a record of your users and can easily identify the people and organizations who ask you for help.

You can now keep banners and messages on your web or mobile app until a set expiration date. This option is perfect for announcing upcoming conferences, webinars, promotions, and more.

If you use our Web SDK, you can start sending persistent in-app messages today. If you use our Mobile SDKs, you’ll need to update to the latest version to take advantage of this feature. Persistent messages are available starting in:

• Android 3.7.0
• iOS 2.8.4
• React Native 3.2.0
• Flutter 1.3.0

If you use outgoing webhooks to trigger messages from a third-party provider that is not natively integrated with Customer.io, you can send incoming calls to our Track metrics API to capture metrics in Customer.io. This allows you to see delivery metrics for all of your messages in one place.

You can now retrieve a list of all workspaces and high-level data, like people and object counts, through our App API. This is useful if you need to track usage outside of Customer.io.

You can now hide profile and event attributes from team members with the Viewer role. Admins can manage this setting in Account Settings > Team Members. When creating or editing a team member with the Viewer role, toggle Prevent this person from viewing profile and event attributes to on.

The Google Tag Manager (GTM) destination helps you take advantage of GTM through your Data Pipelines implementation. You won’t have to drop in the GTM snippet or call gtag directly.

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.

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

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.

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.

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

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.

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.

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.

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

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.

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

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.

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.

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

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.

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.

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.

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.

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

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

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

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

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.

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.

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.

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!