Customer.io Release Notes

New features

Our AI Assistant and MCP server can now fetch detailed conditions for segments, campaigns, and templates, helping you better understand segment conditions and analyze campaign performance.

You can ask our assistant about:

• Segment conditions: “When do people enter my Onboarding segment?”
• Campaign performance: “What’s the click-to-open rate for my Onboarding campaign and how does that compare to my Welcome campaign?”
• Email template/content analysis: “Are there any issues with my email template that might affect performance with my audience?”

You can combine these things as well. For example, you might request information about a campaign and then ask the assistant to analyze the emails in the campaign for issues that might affect performance or deliverability.

Go to the docs

Automatic Geolocation Data Collection

Our new Automatic Geolocation Data Collection feature captures geolocation and time zone data for people you identify from our JavaScript client or mobile SDKs. This data makes it easy to segment your audience by location and send messages at the right times for each member of your audience using our recommended send time feature and time zone match features.

This setting is on by default for workspaces in our US data center and off by default for workspaces in our EU data center. If you’re in the EU data center, you’ll need to enable it under Workspace Settings > Time Zone & Geolocation Settings.

Go to the docs

Automatic Geolocation Data Collection

Our new Automatic Geolocation Data Collection feature captures geolocation and time zone data for people based on their IP addresses when you identify them. This data makes it easy to segment your audience by location and send messages at the right times for each member of your audience using our recommended send time feature and time zone match features.

Our JavaScript client and mobile SDKs automatically capture IP addresses for you, making geolocation easy.

If you use our backend libraries (like our Node.JS or Go SDKs) or our Pipelines API, you’ll need to:

• Go to your integration’s Settings tab and turn on the Enable Geolocation setting.
• Capture the IP address yourself and pass it in the context.ip field in your identify requests.

This setting is on by default for workspaces in our US data center and off by default for workspaces in our EU data center. If you’re in the EU data center, you’ll need to enable it under Workspace Settings > Time Zone & Geolocation Settings.

Salesforce data filtering in Customer.io

You can now filter incoming Salesforce data to only bring in the data you need to use in Customer.io. In the past, if you didn’t want to use all of your Salesforce contacts, accounts, and other data types in Customer.io, you had to bring all of that data into Customer.io and clean it up later. This helps you avoid sending unnecessary data into Customer.io so you can focus on the data you really want to use.

While Salesforce filters typically require a SQL syntax, we’ve included a handy AI box, where you can describe the data you want to bring into Customer.io and we’ll generate a filter for you.

Collections moved to Data & Integrations

If you use collections, you’re probably used to finding them in Content menu. We’ve moved them to Data & Integrations > Collections because they’re much more like like data you use programmatically than your typical message content, layouts, image assets, and so on. Don’t worry: we haven’t changed anything besides moving Collections to a friendlier location in our menu.

If you haven’t used collections before, now’s a great time to start! Collections let you store data that you want to use in campaigns but isn’t necessarily associated with people or objects. These could be things like available promotions/coupons or upcoming events your audience might be interested in.