Customer.io Release Notes

Messaging

Customer.io now keeps a history of every time a person opts in to or out of your messages: when it happened, what it applied to, and where the change came from. Now you don't just know your audience's current message preferences, you can keep a history of their choices for compliance purposes.

Now you can answer questions like “when did this person agree to hear from us, and how?” with consent records. Customer.io writes a record each time a person opts in to or out of your messages, whether they use your subscription center, click an unsubscribe link, or reply STOP to a text message.

Consent records are already on for accounts created on or after October 1, 2026. If your account is older, an administrator can turn them on in

Workspace Settings > Consent

to:

• See a person’s current consent for each topic and channel in the
  Consent state
  panel on their profile.
• Build segments from consent history, like everyone who opted out by SMS reply in the last 30 days.
• Export consent history for audits and compliance reviews.
• Start each person’s history with a record of the choices they made before Customer.io started recording, based on their current subscription preferences and opt-outs.

Messaging

Mobile SDK

Now you can draw geofences as polygons that follow the shape of the locations you care about rather than just circles that roughly map to your campuses, venues, or other places your audience spends time.

A circle doesn’t always fit the places where you want to reach your audience. With polygon geofences, you can draw a boundary on the map in your workspace, or import polygons in a GeoJSON or GeoJSONL file. You can mix circles and polygons in the same geofence set, and your existing circular geofences don’t change.

Polygons must be convex: one boundary with no holes or inward corners. You can read the full list in our polygon requirements.

Your app needs one of these SDK versions to detect polygons. Older SDK versions keep monitoring circles, but they don’t receive polygons.

• Android 4.22.0
• iOS 4.9.0
• React Native 6.13.0
• Flutter 4.7.0
• Expo plugin 3.11.0

Go to the docs

Data & integrations

Now you can import data from Databricks into Customer.io. Connect your Databricks instance, write queries against your data, and sync the results into Customer.io as people, events, and objects (like accounts, companies, etc).

If your company runs on Databricks, the data you need to message and activate your audience probably already lives there: audience information, subscription tiers, product usage, churn scores, and so on. Until now, getting that data into Customer.io meant exporting it to S3, building your own pipeline against our APIs, or paying for a separate reverse ETL tool.

Now you can connect Databricks directly to Customer.io. You write a query against your Databricks warehouse (or get help with this from AI!), map the columns to people, objects, or events, and pick how often the sync runs. Customer.io runs the query on that schedule and imports the data, so you can segment your audience and send them personalized messages from Customer.io.

To get started, pick Databricks in the integrations directory in your workspace, or start with our Databricks documentation.

Go to the docs →

Messaging

Mobile SDK

If you have multiple mobile apps with overlapping audiences, you can support both apps in the same workspace. When you send an in-app message, you can choose the apps and platforms you want to show your in-app message on—no more page-rule workarounds or separate workspaces to keep messages out of the wrong app.

If you have multiple apps in your workspace, in-app messages will show a Where this message appears setting. From here, you’ll choose the app your message belongs to and the platforms where you want to show it.

You’ll need to update your mobile SDK to support this feature. If you have multiple apps that you manage across workspaces today, and you want to consolidate them to a single workspace, you need to wait until a significant number of devices have updated to the new SDK version before you consolidate workspaces.

AI

The Customer.io AI agent now works in Slack. You can @Customer.io in a thread to ask it questions about your data and workspace. Or you can message it directly and give it work—without opening Customer.io.

With the Customer.io Slack app, Customer.io becomes another collaborator in your work. You can have a conversation about the messages you want to send and hand the work off to @Customer.io all in one place.

We’re rolling the Customer.io Slack app out to accounts through August 22. If you don’t see Slack Agent options in your settings yet, it’s on the way.