Release Notes

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.

Campaigns, broadcasts, newsletters, and segments now show their creation date and when they were last edited. We hope this change makes it easier to understand when you started using an asset, and helps you track down issues related to segment, campaign, and newsletter changes.

You can now capture form submissions directly from Typeform without using Zapier as an intermediary to transform data. To set up a Typeform integration, go to Data & Integrations > Forms and select the new Typeform option. Copy the personalized webhook URL, add it to your Typeform, and you’re all set!

We added a Skip duplicate email addresses setting to email newsletters in ID only workspaces. If people in your newsletter audience have the same email attribute, prevents you from sending your email newsletter multiple times to the same address.

You can now connect your MySQL or Postgres database to Customer.io over SSL, helping you securely import data to your Customer.io workspace from external sources.

You no longer need to explicitly share Customer.io sheets with cio_share@customer.io. Now, before you import your first Google sheet, you’ll authorize Customer.io to access specific files in your Google Drive. After you grant access, you can easily pick the sheets you want to share from your Google account—to add people, create segments, and update collections—without having to get individual links for each sheet that you want to share with us.

When you query a collection, you can now match against a value in an attribute containing an array of values. For example, if you store your audience’s interests as an array in an attribute called interests, you can now query your collection to return data where people’s interests include a specific interest—like “cooking” or “football”!

As campaign workflows become larger and more complicated, it can become challenging to read campaign logic or remember what each branch, split, and message action does. Now you can leave notes for yourself and others, to help explain your workflow at a glance.

Previously, our Segment Source integration wouldn’t send events for people who did not have an ID. Now, if a person has an email but does not have an id, we send events to Segment using the email address as an anonymousId. This lets you map events for leads in Customer.io to another destination.

You can now segment people based on messages in individual campaigns. This helps you see which individual people opened a message, or received a specific message in a campaign split.

When you create a segment, select the message type under Message Data. Then you can click Any , and search for the campaigns or individual messages that you want to segment on by name.

After you start a campaign, you can click the campaign’s Journeys tab to see the most recent journeys that started for that campaign. These journeys can help you understand if your campaign works the way you expect it to.

We’ve added an API endpoint that you can use to merge duplicate people. The payload lets you identify a primary person and a secondary person. The primary person remains after the merge. The secondary person’s information is merged into the primary, and then it is deleted.

We added a new message library, making it easy to search for messages in your workspace without having to click through your campaigns and broadcasts to find them. Go to Content > Message Library to search through your messages.

Set up a newsletter webhook, sending a request for every member of a newsletter audience. This provides a handy way to trigger in-app messages and other external services based on a segment of people in Customer.io!

Now you can edit, recategorize, and delete rows saved rows in our drag-and-drop editor. This helps you prune saved rows and prevent other members of your team from accidentally reusing stale content! Note that deleting a row does not remove it from existing messages; it only prevents you (and others) from using that row in the future.

You can save rows of content in emails that you create in our drag-and-drop editor. This helps you save reusable content, like headers and footers, so that your messages all have the same look and feel without having to re-create message blocks every time you write an email!

In Email or ID workspaces, you can now add people from a CSV file by email address. Previously, you could only add people from CSV files by ID.

Customer.io now automatically identify people when they click tracked links that send them to pages containing the JavaScript snippet. We append your links with a _cio_id URL parameter to identify people who click tracked links. This feature is on by default when you create new workspaces. If you want to turn this feature on in an existing workspace, go to Settings > Workspace Settings > URL Parameters and turn on the Add _cio_id URL parameter setting.

You can now segment your audience based on URL parameters passed in a page view event. Page view events captured by our JavaScript snippet automatically convert query parameters to event properties you can segment on.

Our JavaScript snippet now automatically captures URL parameters in page view events, helping you retain information about the pages a person views, like filters, search queries, etc.

Unsubscribe links generated by Customer.io are now untracked by default. You no longer have to worry about unsubscribe links counting as tracked clicks.

When you select a person, you can now go to the attributes tab and search that person’s attributes by name. This can help you find specific attributes when you associate people in your workspace with large amounts of data.

You can now count conversions from webhooks, providing a mechanism to track conversions for messages that you trigger with webhooks in services outside of Customer.io. When you set up a webhook in your campaigns, toggle Allow conversion from this webhook to count conversions from your webhook.

Twilio supports response keywords, letting people opt-out of Twilio SMS messages by replying with keywords like STOP or QUIT. We wrote a script you can use and a quick recipe to help you set up a Twilio workflow to send opt-outs back into Customer.io.

We added the option to disable link tracking in the drag-and-drop editor, so you can exclude unsuccessful click outcomes, like custom unsubscribe clicks, and maintain an accurate click rate. To disable link tracking, just add the untracked class to the button, image, or text link that you don’t want to track.

You can search for team members in your workspace settings, making it easier to determine who has access to your workspace, especially when you have a large team.

You can now send WhatsApp messages via Twilio just like SMS messages. When WhatsApp support is enabled, you can compose WhatsApp messages with customer data, and preview the output directly in our Twilio composer.

To support Twilio WhatsApp messages, you must set up access to the WhatsApp Business API. When you do, contact win@customer.io, and we’ll enable WhatsApp support for your account.