Category: Blog

Building a Space for Feedback, One Gif at a Time

Customer.io has teams spread across the globe. That’s awesome, but it can also present unique challenges. With people managers and their teams spanning 5 continents and more timezones than we can count on both hands and feet, we wanted to create a simple way to give and solicit feedback regularly. We use a weekly company-wide newsletter – with plenty of gifs and conversation-starting questions – to gently nudge team members to talk with their managers, building a space for feedback.

Several services will take care of these kinds of internal messages for you – 15five is a great one. But at the end of the day, this is an email campaign. And that is what Customer.io does! Having newly joined the People Operation Team, I inherited these Weekly Campaigns and just knew there was a way to automate and achieve this goal by using our own platform.

Even if we were to automate these emails, we knew each email should be personalized to the recipient. The email should address them by name, be sent at a time that makes sense in their timezone, and connect them directly with their correct manager. All of that is easy to do out of the box in Customer.io. I also wanted its content to be different each week, ideally seasonally relevant, so people don’t grow blind to the emails. And it should make people smile when they open the email – bring on the gifs and cheesy opening lines!

The easiest way of building this in Customer.io would be an email broadcast. Each week, someone on the People Ops team would build out the newsletter, customize it for the week, and then schedule it to send in the team member’s timezone. But that would be a lot of recurring manual work, setting reminders that often get pushed back, and general human error (read: forgetting).

But I realized that the emails themselves are structured mostly the same week after week, only the content changes. If we could set up a year’s worth of content in a spreadsheet, then all the campaign would have to do is pull in the current week’s information. And if we want to add content to any particular week- no problem! Just open the Collection’s spreadsheet and toss in that new gif you came across or share a recently found article with the team. With a combination of Google Sheets, Collections, and Event-Triggered Campaigns, we got it working!

Here are the steps to follow if you want to build this out for your team:

Step 1: Build Your Spreadsheet

Each weekly email has the same structure. It starts with an opening line, goes into some questions, and then has a closing line. There’s also a fun gif at the bottom and top. Each element gets its own column, and each row is identified with the send date. Here’s what that looks like:

We use HeyTaco! for team member recognition 🌮🌮🌮

Step 2: Create Your Collection

Collections are one way in Customer.io to store data not directly tied to a user. You can upload a CSV or link a Google Sheet to Customer.io, and then query that data in your campaigns. With the Google Sheet already set up and filled out, you can import the email content in just a couple clicks.

Step 3: Design Your Campaign

We have a workspace in our Customer.io instance that’s just for People Ops. Each team member has their own profile. Each profile includes their full name, timezone, manager’s name, and anything else we’d need to personalize the messages they receive.

This campaign starts with a Time Window to wait until Thursday afternoon in the team member’s timezone. Next, we set up the Collection query. Since each row in the spreadsheet (and therefore the Collection) is identified with a date, we need to add an attribute to everyone’s profile that matches the current date. We do that with an attribute update and some liquid logic formatting to match the format we have in the Collection:

Once that attribute is set, we can query the Collection. We want the row in the Collection with the date that matches the current date. Once that’s found, each column in that row is added as a new attribute against the team member’s profile.

Now we’re ready to create the email! Using liquid logic, we can pull in the email content we queried for from the Collection, including the gifs.

To end the campaign, we wait 6 days and then fire an event. That event triggers next week’s email, starting the campaign over again.

Pairing Pair-fection

This post started as an internal document written by our Senior Site Reliability Engineer, Joe Purdy. In it he describes his personal approach to pairing (including, but not limited to, pair programming). We hope this helps you in your own work, whether or not you’re an engineer.

What is pair programming?

Traditionally, pair programming is simply the act of two (or more) people working off a single editor to write code. Normally one person “drives” by being the person to actually type code and run commands while the other person helps navigate.

That’s the basics, but I like to extend this much farther by removing all that “programming” baggage from the act.

My version of pairing

I like to pair with people I work with on all sorts of projects. Sure, there’s some programming, but more often than not the activity we’re pairing on is something totally non-code related. I’ve paired with people to write documentation, author internal processes, share general knowledge of organization lore, and yes, write some occasional code.

Why pair with someone?

Being a remote worker often means working alone. Pairing is a fantastic way to get some time to socialize with a co-worker like RealOfficePeople™ do. I also don’t learn much from reading Pull Requests, release notes, or raw code compared to the times I’ve collaborated with other people.

Another advantage for pairing outside of your role is to learn more about the processes and experiences of parts of the organization you don’t work in day to day. If you’re an engineer and you pair with someone from tech support to help improve some of their internal process you’ll learn about perspectives and problems that otherwise might not be apparent. I’ve found that the more teams I work with the better I understand the bigger picture of what we’re all working towards.

Enough theory, let’s talk practice

I look at pairing through the lens of “How many hours can I do this a week?”. In other words, I have roughly 40 hours a week spent working on things for the organization, so how many of those hours could I stand to devote to pairing with someone else? This is a personal question and one you should answer for yourself.

Once I’ve found how many hours I can spend I tend to divide that number into one hour blocks. I find pairing for a minimum of one hour helps to make sure there’s enough time to really get into whatever topic the person I’m pairing with wants to cover. Often I’m likely to run over an hour rather than under, so an hour feels like the right minimum.

I always leave headroom for the time I have for pairing. As an example if I decide I’m going to spend at most six hours of my week pairing with folks I make sure never to schedule more than five people. This means when sessions run over I don’t go far beyond the overall budget of my time. I also try to schedule pairing sessions without anything coming directly after so that they can run over the minimum 1 hour without consequence of having a hard stop.

How to have a successful 🍐 sesh

Plan Ahead

Have an “Ideas” document!

I’ll share a very basic template you can copy for yourself here:

Person 1 <> Person 2 🍐 Ideas

The general idea is you create a shared page titled after your name and the person you’re pairing with and share it between the two of you. From there you just collect a list of topics of interest.

Commit to it

For the people I pair with I default to a weekly time that works for us where we set a re-occurring calendar event. This event repeats forever and we both can make modifications to the event. I think regular pairing like this works best when both people commit to it.

…but remain flexible

Life happens. Sometimes either you or the person you pair with won’t be available and that’s ok! When that happens just communicate as such and if possible re-schedule the session for another time that week. If you have to skip the week that’s fine too. It’s also possible you’ll find that a lot of the time there isn’t anything pressing that feels worth pairing on. Skip the week in that case! Or another idea is to have a shorter pair session reviewing your ideas doc together to see if there are things you both want to work on together that just aren’t written down and are easily forgotten.

Tools

Right now I’m not doing anything overly fancy when it comes to tools that help pair. My 🍐 stack looks like this:

  • Video conferencing – This is a major 🔑 for pairing. All my pairing is remote and happens over video calls with screen-sharing. I’ve used Screenhero (RIP), Slack, Zoom, Screen.so, and MS Teams. If I had to pick the one that worked best I’d go with Screen.so, but honestly they all do a good enough job.
  • My Calendar – I make heavy use of my Calendar (this can be anything, Google, Outlook, etc.) to schedule re-occurring pairing meetings and find open availability.
  • A wiki – The aforementioned ideas doc lives in whatever wiki exists where I work. I’ve used Notion.so and Confluence primarily.

That’s really it. I don’t get too fancy with this stuff. If you have a Killer App or tool that really helps with pairing feel free to use it instead! My list used to be very specific in listing the exact product for each point, but I’ve found that products change and the basic set of tools remains the same. You need a tool to communicate in real time, a tool to schedule meetings, and a tool to asynchronously collaborate on pairing topics/backlog.

Keep Calm and 🍐 On

Thanks for reading this and I hope it sparked some ideas for you. More importantly I hope it inspired you to offer to pair with someone or to ask someone to pair with you (feel free to link your peer/manager to this page if you need a conversation starter 😉).

There are few things I evangelize at work as much as I do Password Management/MFA. Pairing is a close second to that. Pairing is an investment you can make in yourself and the people you work with that pays immediate dividends in the form of increasing your knowledge and making your team stronger overall. So go out there and get your 🍐 on!

A Virtual Walk in the Park

Customer.io doesn’t have the luxury of spontaneous conversations at the coffee machine or spur-of-the-moment catch-ups over lunch as a remote-first company. For many companies, those little moments are what build relationships and company culture.

As our VP of Operations, I’ve planned over ten company retreats with the mindset that they are our highest impact team-building opportunities throughout the year. About every six months, we gather as much of the team in locations like Budapest, Iceland, and Romania. Being together helps build up our interpersonal relationships and psychological safety, allowing us to collaborate more openly throughout the year.

The team at our 2019 Fall Retreat in Budapest
Our Fall 2019 Retreat in Budapest

In 2020, when all travel stopped due to the pandemic, we lost the option to meet in-person. Without our standard retreats, I worried that morale would suffer and people would feel withdrawn from each other and the team.

We knew we needed to add something more interactive to our Zoom calls and Pizzatime shared meals. Something to make this virtual retreat memorable. And that’s when it clicked: virtual retreat, VR … virtual reality!

We had our doubts. VR technology has come a long way, but would it feel like a gimmick? After researching a variety of VR headsets, we landed on the Oculus Quest. We found it the most user-friendly all-in-one VR set. Plus, we could get it shipped directly to almost all of our teammates all around the world!

Five teammates trying out the VR headsets in preparation for the retreat.
Five teammates figuring out their VR headsets together in prep for the retreat.

When the VR Virtual Retreat came around, I was surprised and excited to see that many of the activities we used to do in-person translated incredibly well to VR. Instead of sitting together in a dark Hungarian bar playing cards, we hosted a VR poker tournament with Pokerstars. Instead of preset team-bonding activities in the evening, teammates started impromptu Elven Assassin sessions throughout the day.

Response to our Virtual Reality Retreat was overwhelmingly positive. Seeing teammates half a world away from each other having meaningful interactions, to borrow some quotes from the team:

From Cam: I have to be honest that I wax worried that VR wouldn't be as effective of a "Real LIfe" replacement for cross team trust building and just filling up people's social batteries. But then I saw HiuHui and Cody playing Eleven Assassin together and it made my heart full. Cook-Out also gets huge praise from me promoting teamwork, trust and communication.

From Alyssa:
It has gone so well Cam, brilliant idea to you all!!! Lacey, Alex, Nay and I are dominating at Elvin Assassin and the team work is amazing. Cook out too! I think everyone will keep playing after work hours and stay connected even more post retreat!
From Brendan: Signing off for the day. I thought VR made this retreat roughly 1m000% better than our last virtual retreat. THanks Cam, Alyssa, Sonja and everyone else for making that happen!

What surprised me most was how, as a remote company, we could use VR to build relationships between coworkers throughout the year. Why wait for the next in-person retreat? You can always catch up with a teammate on a virtual walk in the Walkabout Mini Golf park today.

Dun, Dun, Dun … Dunning with Empathy

Dunning emails are the messages a business sends to its customers to collect past-due payments. At best, they are a nuisance; at worst, they inspire dread. Email marketers often overlook these messages as a distasteful, if necessary, part of doing business. When I redesigned our dunning campaign, I wanted to create as painless an experience as possible for our customers. Here are five ways I designed our campaign with empathy that you can use in your dunning emails, too.

#1 Wait to send your first email until you’ve confirmed there is a billing problem

Dunning emails are triggered most often by card failures at the time of billing, and our campaign is no different. Many dunning campaigns would then email the customer instantly to inform them that their card failed. However, most charge failures are due to temporary issues, which retrying the card solves. That is why Stripe (our payment processor) will retry the card up to five times over five days.


With this knowledge, I start the campaign with a five-day Time Delay. In that time, our payment processor automatically retries the card, and frequently the charge goes through successfully. When it does, the campaign automatically exits the customer. With this Time Delay alone, 50% of card failures are resolved – without ever messaging the customer.

#2 Send additional messages only after enough time has elapsed

Solving payment issues has many moving parts – bureaucratic finance departments, bank approval times, regional holidays, and time zone differences – which all increase the time to resolution. It might feel right to follow up quickly about a critical billing issue, but I found that allowing adequate time between reminder messages are kinder and more productive. I use a Time Delay between each dunning email of at least three days. I also include Time Windows before each email to ensure the campaign only sends emails during weekday working hours (in the customer’s timezone).

#3 Be sure you’re only sending messages if the problem hasn’t been fixed

Dunning emails are stressful by nature, but mistakenly emailing your customers after they fix the issue is even more stressful. In conjunction with the Time Delays, we use Exit Conditions to ensure that the campaign only messages customers with active billing issues. When a billing failure is corrected, our payment processor sends an event into our workspace. This event defines the campaign’s exit condition segment.

We solve some billing issues outside of the payment processor. In these cases, I manually remove the customer from the campaign.

#4 Message your billing contact first, then add additional contacts

Contacting the right person with billing issues is another way you can exhibit empathy. Emailing everyone in an account for a billing issue only one person in their company can fix is a quick way to lose your customer’s trust. In our product, we encourage accounts to list a dedicated contact for billing purposes. The first two emails in our dunning campaign go only to this contact. The campaign sends to the account owner in the following emails if the issue remains.

#5 Above all, be human

All billing issue conversations are awkward. Throughout our campaign, I try to be as human as possible to alleviate that awkwardness: we start the emails with Hi instead of the more formal Dear; I signs the emails with my name instead of the them coming from a more generic billing team. 

Beyond these human touches, if a billing issue remains after sending these automated emails, the campaign notifies me to reach out to the customer individually to see how I can help. If the business is going through a challenging period, I work with them to figure out a payment solution.

With these five tips, I transformed our dunning campaign from an afterthought to a successful email campaign. Not only does it bring in revenue that the company would otherwise lose, each message in the campaign proudly exhibits our brand value of empathy. We encourage any subscription-based-revenue company to do the same. 

January Release Notes

This month, we made it possible to add people to your workspace using only their email addresses and provided tools to save time when you create or edit complex campaign workflows. Read on to learn more about the features we shipped in the past month.

What’s New?

Email Addresses as Unique Keys

You’re probably used to identifying people by ID—a value that represents your audience as customers. Now you can identify people by their email addresses, helping you start conversations with people before they make a purchase, create an account, or subscribe to your service.

Select “Email address” as the identifier for your workspace

When you use email as your workspace’s unique key, each email address represents a unique person, helping you manage your audience directly by email address. To use email addresses as your unique key, create a new workspace and choose to identify people by “Email address”.

If you want to explore the possibility of converting an existing workspace to identify people by email address, contact win@customer.io.

Multi-select, Copy, and Move in the Workflow Builder

Formerly, our campaign builder required you to create and modify workflow items individually. It took a lot of time and clicks to change the structure of your workflow. We added the ability to select, move, copy, and delete multiple workflow items so that, in just a few clicks, you can copy and move blocks while preserving their structure.

The workflow builder supports both hotkeys and click-and-drag functionality, so you can select and modify items using the input method that works best for you.

Copy Entire Workflows Across Campaigns

We also made it easier to copy entire workflows across campaigns and workspaces, helping you reuse your most successful messages and workflows. You can copy entire or partial workflows to or from another workflow using the Copy to and Copy from options.

Copy entire workflows across campaigns

That’s a wrap for now. We’ll see you next month! In the meantime, follow Customer.io on Twitter to get updates about the latest releases and improvements. Questions? Comments? Send them to win@customer.io.

December Release Notes

At Customer.io, we want to help you maintain a healthy relationship with your audience. Part of that is making sure you don’t wear out your welcome. This month, we added a feature to help you limit the messages you send and respect your audience’s inbox. Read on to learn what other new features we shipped in the last month.

What’s New?

Message Limits

You no longer have to worry about filling your audience’s inbox when you schedule a new message. You can now set a limit on the number of messages a person can receive within a specific time frame. This feature helps prevent you from overloading people with messages, so you can maintain a positive relationship with your audience. To set a message limit, go to Settings > Workspace Settings and click Message Limit. Learn more here.

How to Enable Message Limit

CSV Import Improvements

We reduced the steps required to add and update people using CSV files in Customer.io, helping you avoid mistakes and put your CSV files to work faster. When you successfully upload a new CSV file, you’ll also find new options to create and update existing manual segments using your CSV import.

Complete import and create a new manual segment

Tracking Metrics for Custom Unsubscribe Pages

Before now, if you wanted to use a custom unsubscribe page, we didn’t have a way for you to track unsubscribe metrics. That’s no longer the case. We added a new API you can use to report when people visit your custom unsubscribe pages. Now you can see unsubscribe metrics and identify the emails that result in unsubscribes. Get going and take advantage of re-engagement campaigns after people unsubscribe!

Attribute Exports for Data Warehouse Sync

We updated our data warehouse sync feature to include a new Attributes export file, capturing profile attribute updates. Now you can sync attribute changes to your data warehouse. Learn more about data warehouse sync.

New data warehouse integrations will automatically export Attributes. If you have an existing integration with us, contact product@customer.io and ask us to enable the Attributes export!

Set Sending Behavior for Workflow Actions

Previously, you couldn’t modify the sending behavior for workflow actions programmatically—you had to do it through our UI. You can now change the sending behavior (sending_state) for workflow actions using our APIs.

3 New Liquid Filters

Take advantage of our new subtract_day, subtract_month, or subtract_year liquid filters to personalize messages using complex logic or to modify dates in your message.

That’s a wrap for now. We’ll see you next month! In the meantime, follow Customer.io on Twitter to get updates about the latest releases and improvements. Questions? Comments? Send them to win@customer.io.

Year in Review: Top 20 Features From 2020

To wrap up the year, here are the highlights of what we delivered for you:

Brand new capabilities

  • Transactional Emails – Now, you can send emails by calling our API. Our transactional service provides a dedicated lane to create and send transactional messages independent of your marketing messages, ensuring the highest possible deliverability. If you haven’t sent a transactional email yet, learn how to create your first message.
  • Collections – A Collection is a new way to store data to help you represent static things in your business. You can query collections in campaigns and customize your messages based on people’s preferences and engagement.

Advanced tools for sending bulk messages

  • Multi-Channel Newsletters – Do you want to send a broadcast message to everyone who has a device ID? You can now send Push and SMS Newsletters, just like you’ve always done for email.
  • Sending Newsletters in User’s Time Zones – Your customers are located around the world; we can relate. Sending messages in your audience’s respective time zones helps you send messages at the right time.
  • Cancel In-Progress Newsletters – We hope you never have to use this feature, but if you do, you can cancel any Newsletter that’s still in progress.

Tons of new insight into message performance

  • New Dashboards – It’s essential to have access to metrics to help draw conclusions about performance. This year, we added several new views into your data, including the Workspace Dashboardworkflow metrics, and segment membership metrics.
  • Analysis Page – The new Analysis page allows you to compare metrics across multiple campaigns and broadcasts.
  • Custom Date Ranges – You’re no longer limited to 30 days, 12 weeks, and 12 month time ranges when viewing metrics. Custom date range pickers are now available for all the charts and tables throughout Customer.io.

Made it easier to manage your account

  • Workspace Permissions – Now, you can grant or revoke access to specific workspaces from the Team Members page, helping you manage the people and campaigns your teams have access to.
  • Single Sign-On (SSO) – Enable Google and Okta SSO to grant and manage Customer.io access within your organization. Visit your Account Security page to enable SSO.

More control over your campaigns

  • Stop, Restart, and Archive Campaigns – It’s easier to manage campaign lifecycles: temporarily stop campaigns while you make changes; sunset campaigns so people can finish the campaign and prevent new people from entering it; or stop and restart seasonal campaigns.
  • Additional Branch Conditions – We added other ways for you to customize your messages. You can add event conditions to True/False Branches and Compare Attributes in workflow branches.

New options for getting data in and out of your account

  • Data Warehouse Sync – If you want to sync all historical and future data from Customer.io to your Data Warehouse, you can! You can automatically keep Amazon Redshift, Amazon S3, Google Cloud Storage, Big Query, or Snowflake up to date with your latest sending data.
  • Multi-Channel Reporting Webhooks – We commonly use webhooks to pass data to analytics tools where it can be combined with other campaign performance info. We added support for push, SMS, Slack, and webhook message activity, and the option to include message content in all events.

Tools for composing better messages

  • Snippets – No one wants to type the same information over and over. That’s why we introduced snippets! You can create reusable content—like headers, footers, and signatures—and insert them into your messages. 
  • New Design Options For The Drag-and-Drop Email Editor – It’s easier to customize your messages in our drag-and-drop editor. We now support the ability to change your entire message’s alignment, add icons, write comments, and set a custom number of columns for layouts.

Helped you save precious time

  • Waaaay Faster Campaign Workflow Builder – It now loads three times faster and cleanly renders large workflows without a bunch of unnecessary scrolling.
  • Create a Manual Segment From CSV Imports – On the “Review” step of CSV Imports, you can tell us to create a Manual Segment containing all the people added or modified by the import.
  • Manually Send Events – Want more ways to test and troubleshoot your campaigns before you hit send? You can now send events directly through the UI to test your campaigns and liquid logic in messages. 
  • Tagging for Newsletters and Segments – We added tagging to Newsletters and Segments to help you save time and stay organized.

If you’re not already doing so, follow us on Twitter to get updates about the latest releases and improvements! Questions? Comments? Send them to win@customer.io.

Update on European Availability Zone – Targeting Q1 2021

After the European Court of Justice (CJEU) announced the invalidation of the Privacy Shield Framework earlier this year, Customer.io implemented a Standard Contractual Clauses (SCC) to allow for the lawful transfer of data for our EU customers.

If you’re an EU customer and require an executed Standard Contractual Clauses (SCC), download, countersign our pre-signed form, and return the final copy to your CSM or submit it here.

For customers who prefer to host their data in the EU, we’re now targeting mid to late Q1 2021 instead of January 1st for a general release of a European availability zone. To date we’ve completed setting up the infrastructure for the EU data center. We are now working through the modifications necessary for our services and app to work with this new region.

New customers will see an option to choose the US or EU data centers when creating their account.

Existing customers migrations will be coordinated through your Customer Success Manager.

If you have any questions, please email win@customer.io.

Thank you for being our customer,

Colin Nederkoorn
CEO

November Release Notes

Our goal at Customer.io is to help you consolidate all your bulk and automated messages so you have a single picture of all your customer communications. Continuing on this mission, we launched a new way to send transactional messages: now you can send messages directly from code using our Transactional API. Read on to find the details about everything we shipped!

What’s New?

Transactional Emails

Our new Transactional service lets you send emails by calling our API. We built this service on its own sending lanes and provided a dedicated transactional IP pool, ensuring the highest possible deliverability. Before this release, your only option for sending transactional messages was to send events that trigger campaigns. 

Message content can optionally be stored in Customer.io to enable editing the transactional messages without making changes to your codebase. The service also includes an option to protect sensitive content, like password reset tokens, in transactional messages to reduce risk of misuse. 

You’ll find Transactional in the main navigation of your account and you can learn more in our Transactional API docs.

Select "Transactional" in the navigation menu to send your first message.

Manually Send Events

Now you can send events to a profile directly through the UI to test and troubleshoot campaign workflows as well as Liquid logic messages. Use the “Send Event” feature on a Campaign Trigger, a Person’s page, the Activity Log, or the Data Index to send a real event without going to the command line!

Manually sending an event is simple. Enter event name and event data (optional), then click the "Send event" button.

13 New Liquid Filters For Your Personalization Toolbox

Liquid helps you personalize messages by injecting data and logic into your messages. We’ve added support for thirteen new filters: where, compact, at_least, at_most, concat, url_decode, sort_natural, url_encode, pluralize, remove, strip, lstrip, rstrip.

Compose Left-Aligned Drag and Drop Messages

You can now change the alignment of your entire message in the drag and drop editor. In many cases, left-aligned messages feel more conversational—they’re more like messages your audience composes in their own email clients.

In the drag-and-drop editor, you can select "LEFT" or "CENTER" to align the content area.

We’ll see you next month! In the meantime, follow Customer.io on Twitter to get updates about the latest releases and improvements. Questions? Comments? Send them to win@customer.io.

October Release Notes

Did you have a cup of java to celebrate International Coffee Day in October? Our team celebrated with a global coffee exchange. With elevated energy levels, we were focused on speeding up the workflow builder and adding the final touches to some upcoming (and BIG!) features that we’re not quite ready to reveal yet. In the meantime, read on to learn what we improved last month.

What’s New?

Fast and Space-Efficient Visual Workflows

We love seeing the complex workflows you’re building in Customer.io, but sometimes they took a few seconds too long to load and required a bunch of scrolling. This past month, we rebuilt the algorithm that renders our workflows. The new builder loads complex workflows 3 times faster than before and organizes them efficiently so you can navigate without tons of zooming in and out.

Side-by-side image comparison of old vs new visual workflow builder.
Old vs New

Commenting for Drag and Drop Emails

Ever want to leave feedback for the designer of an email? You can now write comments for yourself or collaborators directly within the Drag and Drop email editor. Click on any Row in the editor, then tap on the chat bubble to add comments.

The chat icon is displayed to the left of the delete icon.

Custom Column Layouts for Drag and Drop Emails

It’s now possible to set a custom number of columns for layouts in the Drag and Drop email editor, rather than be restricted to a few presets. From the editor, select the entire row to alter the number of columns, background color, and padding.

Add new customize columns by taping the purple [+ Add new] button.

Smaller Improvements

  • We added automatic language detection on the unsubscribe page. Visitors will now be presented with a translated unsubscribe page based on their browser’s language settings.
  • When creating a new email, we now show you the list of Layouts so you can use them as starting points with one click. Find this in the “Rich text” and “Code” tabs when adding message content.
  • Your list of manual segments can now be sorted by the date they were imported.

We’ll see you next month! In the meantime, stay updated with the latest releases and improvements by following Customer.io on Twitter. Questions? Comments? Send them over to win@customer.io.