Customer.io Lets Teams Freeze an Audience Before a One-Time Send

Customer.io added snapshot segments on Oct. 20: audiences that keep the membership they had when they were built and change only when someone clicks Refresh. The company described them in its Oct. 20 release notes as a way to “create a more robust audience for one-time sends.”

A snapshot stays put until someone refreshes it

Customer.io’s documentation for snapshot segments compares one to a photograph: it reflects a point in time and doesn’t update automatically. Until now, segments in Customer.io were data-driven. Membership shifted whenever a person’s data changed. The release notes say teams no longer have to rely only on data-driven segments to group people by shared conditions.

Building one works like building a data-driven segment: name it, add conditions, save. The snapshot can then trigger an automation or set the audience for a one-time send. Customer.io said the first build runs longer in a large workspace or with complex conditions. Progress shows in the workspace’s Tasks list.

Refreshes leave a record of who came and went

Each snapshot shows the date and time it was taken. Clicking Refresh rebuilds the membership and updates that timestamp. A Change tab on the segment’s Overview chart counts the people who entered or left across refreshes, and the counts export to CSV.

Customer.io’s example: a snapshot first taken on Oct. 13 matches 113,085 people. A refresh on Oct. 19 finds no new matches and five people who no longer fit. The audience drops to 113,080.

Editing conditions blurs the timeline

Saving new conditions on a snapshot refreshes it at once, Customer.io said. The Change tab then shows the movement in membership, but the company said it does not track when members changed in response to the edit as opposed to the data. Its advice for teams that need that history is to create a new segment instead of editing the old one. Renaming a snapshot or changing its description or tags does not trigger a refresh.

Customer.io also blocks deleting a snapshot that an automation, an unsent one-time send, an API-triggered broadcast, a form, a SQL import or another active segment still uses. A Usage list shows where the segment is referenced.

Key takeaways

• A snapshot segment keeps its membership until someone refreshes it.
• It can trigger an automation or set the audience for a one-time send.
• The Change tab and CSV export count who entered or left at each refresh.
• Editing a snapshot’s conditions refreshes it and blurs the cause of any membership change.

The take

We think the value here is a send list that doesn’t move while a team is reviewing it. With a live segment, the group a marketer approved on Tuesday can differ from the group that receives the email on Thursday. The underlying data kept changing. A snapshot fixes that gap by making the refresh a deliberate act.

The cost is staleness. Opt-outs after the snapshot was taken stay in the audience until the next refresh. Customer.io’s consent records, introduced Oct. 1, track those choices. Refresh the snapshot just before sending. Then check the Change tab for departures. Investigate any drop the data doesn’t explain before the send goes out.