Customer.io Introduces Snapshot Segments for Point-in-Time Audiences

On October 20, 2026, Customer.io introduced Snapshot Segments, a new segment type that preserves audience membership at a specific point in time and lets marketers decide when to update it.

Unlike dynamic segments, which automatically add or remove people as customer data changes, Snapshot Segments retain their membership until the next refresh.

The feature is intended primarily for one-time marketing sends, campaigns targeting a previously selected audience, and comparisons of segment membership over time.

Snapshot Segments: How Fixed Audiences Differ From Dynamic Segments

Before Snapshot Segments, one of Customer.io’s main tools for automatically building audiences was Data-driven Segments. These use conditions based on user attributes, events, and behavior.

For example, a marketer might create a segment of buyers who placed more than two orders in the past 90 days or subscribers who have not opened an app in a month.

In a data-driven segment, Customer.io automatically reevaluates membership when new data arrives. Customers leave when they no longer meet the conditions, while others join when they begin to qualify.

Snapshot Segments use similar eligibility rules, but their membership does not change automatically. When a snapshot is created, Customer.io identifies everyone who matches the conditions and saves that audience.

Subsequent changes in behavior or user attributes do not automatically add or remove members.

For example, on November 1 a company creates a segment of customers who purchased at least once during the preceding 30 days. The resulting audience contains 25,000 people.

A week later, some shoppers no longer meet the original criteria, while others have made their first purchase. Yet the Snapshot Segment keeps its original members until it is refreshed.

This gives marketers control over exactly when segment membership is recalculated.

Creating a Snapshot Segment: Conditions, AI, and Audience Capture

The new segment type is created directly in the Customer.io Segments area.

1. Open Segments → Create segment.
2. Choose the Snapshot type.
3. Enter a segment name and description.
4. Specify audience conditions manually or with the available AI tools.
5. Save the segment.

After saving, Customer.io starts building the list of people who meet the selected conditions.

Processing time depends on the number of profiles in the workspace and the complexity of the conditions. Large lists or segments with several condition groups may take longer to calculate.

The status of this operation appears in the workspace Tasks list.

You can use the same types of conditions as Data-driven Segments, including user attributes, events, communication history, and other supported segmentation data.

A Snapshot Segment does not require marketers to upload a recipient list through CSV. Customer.io identifies eligible members from the configured rules.

Updating the Audience: Manual Refresh Instead of Automatic Recalculation

After a Snapshot Segment is created, Customer.io shows when its membership was last generated.

When marketers need a current audience, they can click Refresh. Customer.io then reapplies the conditions to current customer data and creates a new membership list.

For example, a marketer creates a segment on November 1 for customers who purchased in the past 90 days. A month later, they can refresh it to capture new orders and changes in the customer base under the same rules.

Customer.io then records the latest refresh timestamp.

An important limitation: Snapshot Segments do not automatically refresh on a schedule. Customer.io documents a manual Refresh action. The marketer decides how often to update the audience and initiates each refresh.

This is particularly relevant when a campaign requires a stable audience during a specified period.

For instance, before a one-time send, the marketer can finalize the criteria and capture the intended audience rather than relying on a continuously changing dynamic segment.

Membership History: People Added and Removed Between Snapshots

Customer.io lets users track membership changes between refreshes.

The Overview area shows the segment membership trend. On the Change tab, marketers can review how many people joined or left after a refresh.

For example, an initial Snapshot Segment has 113,085 members. A week later, the marketer refreshes the audience. No new people qualify, while five no longer meet the criteria, leaving 113,080 members.

Customer.io also supports exporting these changes to CSV.

This helps teams document changes in target groups between campaigns, assess segment stability, and observe how users move between defined states.

However, Snapshot Segments do not retain a complete history of every customer attribute.

They report membership differences between successive refreshes but do not automatically establish the exact date when each person stopped meeting a condition.

For that reason, Snapshot Segments are not a complete historical customer-data analysis system.

Editing Segment Conditions and Rebuilding Membership

Customer.io allows marketers to edit a Snapshot Segment’s selection rules after creating it.

However, changing conditions is different from an ordinary refresh.

If the marketer edits the conditions and saves them, Customer.io automatically recalculates membership using the new rules.

For example, a segment originally includes customers with two orders over the past 90 days. If the threshold is changed to three orders, the platform rebuilds the list after the new conditions are saved.

The original audience therefore no longer remains unchanged.

Customer.io recommends creating a separate segment if the team needs to compare two audiences built using different selection rules.

By contrast, changing the name, description, or tags does not trigger membership recalculation.

Snapshot Segments remain stable when customer data changes, but they are not protected from edits to the rules that define membership.

Using Snapshot Segments in Sends and Automations

Snapshot Segments can be used in the same Customer.io workflows that support audience segments, including:

• The audience for one-time sends.
• A trigger condition for automated campaigns.
• Inclusion or exclusion criteria for users.
• A source for membership analysis and audience exports.

For one-time sends, the primary benefit is control over the intended recipients.

For example, an online retailer can prepare a special offer for buyers who met the eligibility criteria on the day the audience was captured. The group remains fixed ahead of the campaign rather than changing as customers make new purchases.

It is important to distinguish stable segment membership from the actual eligibility requirements for sending a message.

A Snapshot Segment does not override subscription status, consent requirements, or other delivery restrictions enforced by Customer.io.

Teams must also consider how the segment is used in automated journeys.

If the snapshot is used as a trigger or filter, a manual Refresh may change membership and affect related automations.

Before refreshing a snapshot, marketers should check where it is being used.

Snapshot, Data-driven, and Manual Segments: Three Ways to Manage Audiences

With the October update, Customer.io supports three main types of segments:

The key distinction between Snapshot and Manual Segments is that a snapshot is generated from segmentation conditions, while a manual segment is controlled by explicit additions and removals.

Snapshot Segments also differ from Data-driven Segments because they do not continually reevaluate eligibility.

The appropriate type depends on whether an audience should change automatically following every new event or retain its agreed membership until the marketer chooses to update it.

Applications for E-commerce, Customer Services, and B2B

E-commerce. Snapshot Segments work well for campaigns directed to a previously selected group of customers.

For example, a retailer can capture loyalty-program members, VIP shoppers, or customers who purchased during a specific season and use that audience for a dedicated campaign.

This helps when a team needs to estimate its potential audience and agree on communication terms in advance.

Customer Services. Service businesses can capture groups of customers who should receive a notification, an offer for repeat service, or an event invitation.

For example, the team can identify customers who used a specific service in the previous quarter and hold the audience until the communication is sent.

B2B. Snapshot Segments can support existing-customer campaigns, webinar invitations, and communications with selected product users.

A B2B SaaS company can capture users who met a given activity threshold when the campaign was planned and compare membership after subsequent refreshes.

However, Snapshot Segments do not replace CRM-based account and buying-committee segmentation. They work with the customer profiles and conditions available in Customer.io.

Customer.io Combines Customer Data, Segmentation, and Multichannel Direct Marketing

Customer.io is a customer communications automation platform that uses behavioral data to personalize email, SMS, push notifications, and other messages.

The platform is built around customer profiles, events, and attributes, which marketers use to create segments and trigger automated journeys.

Customer.io supports a visual campaign builder, audience management, message personalization, A/B testing, analytics reports, APIs, and integrations with outside data sources.

In E-commerce, it can automate messages following product views, account registration, purchases, or extended inactivity.

For Customer Services, it supports service notifications, reminders, and repeat-engagement sequences.

For B2B SaaS, Customer.io supports onboarding, activation, product adoption, and retention campaigns.

Snapshot Segments complement those existing tools by letting marketers preserve the membership of an audience at a selected moment.

This is especially useful when teams need to agree on the recipient group in advance and monitor changes between campaigns.

The main limitation is that saved membership does not automatically respond to new customer data. Its relevance depends on when the marketer last refreshed it and whether the conditions still meet current needs.

Sources

1. Customer.io — Snapshot Segments Release Notes, October 20, 2026
2. Customer.io — Snapshot Segments Documentation
3. Customer.io — How Segments Work
4. Customer.io — Data-driven Segments
5. Customer.io — Release Notes