Behavioral segmentation groups customers by what they did: purchases, visits, clicks, gaps between orders. Marketing guides list it as the fourth of four types beside demographic, geographic and psychographic. It is not like the other three. They describe who a person is; behavioral segmentation describes timestamped events, and a group built from events expires at the next event.
Relvino decides per shopper instead of per segment, so read this as informed but interested. The two vendor guides that rank second and third for the term are quoted directly; the argument about why the fourth type is different is ours.
Salesforce’s guide opens with the list every marketing course teaches. “The four primary marketing segmentation categories are:” demographic, geographic, psychographic, behavioral. It then picks a favorite: “While each segment can be a powerful way of understanding and communicating with your audience, the most useful is arguably behavioral segmentation.”
RudderStack’s guide puts the four in a table, and the table gives the game away. Behavioral is based on “Actions, usage patterns, purchase history,” and its example is “Customers who purchased within the last 30 days.” Demographic is based on “Age, income, education, household size.” Geographic on “Location, region, market.” Psychographic on “Behaviors, lifestyle, attitudes.” Read the examples side by side. Three of them describe a state. One of them has a clock in it.
RudderStack is explicit about why: “Behavioral segmentation divides an audience into groups based on observed actions rather than assumed characteristics. The inputs are behavioral data: time-stamped records of what a person did, when they did it, and how often.” A customer’s age changes once a year. Their location changes once in a few years. Their attitudes drift over a lifetime. Their behavior changes tonight, when they open a product page, or tomorrow, when the delivery arrives and the thing they were about to buy is no longer needed. The fourth type is the only one whose membership is a function of time.
Salesforce: “Behavioral segmentation looks at how and when a consumer decides to spend their money on a product or service. It focuses on consumers’ shopping behavior, how they make their decisions, why they choose one product over the other, and how they feel about a product, company, or service.” It then names “the six subcategories within behavioral segmentation”: purchasing behavior, occasion purchasing, customer usage, benefits, loyalty gauge, buying stage.
RudderStack counts differently. Its takeaways say “The four primary segmentation types are purchase behavior, occasion-based triggers, benefits sought, and loyalty and engagement level.” Six on one page, four on the next. The disagreement is not an error on either side. It is a sign that behavioral segmentation is not a method so much as a list of questions a marketer might ask about customers, grouped under one heading because the answers come from the same data.
One of the questions gets a dedicated line on both pages. RudderStack, under purchase behavior: “The relevant variables are recency (when they last bought), frequency (how often they buy), and value (how much they typically spend). These three dimensions, often combined in RFM analysis, allow teams to identify segments such as high-value repeat purchasers, occasional buyers, and lapsed customers who may need re-engagement.” That is RFM, and the RFM segmentation guide on this site covers what those scores do and do not tell a brand.
The People-also-ask box for this search asks for an example of a behavioral segment, and RudderStack’s ecommerce section supplies the standard set. “Cart abandonment is one of the most common behavioral segments in e-commerce. Customers who add items but do not complete a purchase have signaled intent without converting; they often need a specific prompt, such as a reminder or a shipping offer, to complete the transaction. Browse abandonment is a lower-intent signal, where customers view products but do not add them to a cart, and typically requires educational content or social proof rather than a direct purchase prompt.” Then repeat purchasers: “Tracking purchase frequency within rolling windows, such as 30, 60, or 90 days, lets teams identify their most engaged buyers and treat them accordingly with loyalty rewards, early product access, or personalized recommendations.”
Salesforce’s examples are built the same way. Under customer usage: “It’s useful to identify your heavy, medium, and light users so you can effectively market to them.” Under buying stage, a five-step ladder: “Nonusers have never heard of you,” prospects, first-time buyers, regulars, and “Former customers jumped ship and are now your competitors’ customers.”
Look at what every example has in common. “Within the last 30 days.” “Rolling windows, such as 30, 60, or 90 days.” Heavy, medium, light. Added to cart but did not buy. Each segment is a threshold on an event count or an event age, and a person chose the threshold. Thirty days is not a fact about customers. It is a round number a marketer picked because a list has to have an edge somewhere.
A demographic segment is wrong rarely and slowly. A customer who is 35 to 44 today will be 35 to 44 next month. A behavioral segment is wrong constantly and quickly, by construction. “Purchased within the last 30 days” loses members every day as orders age past the edge and gains them every hour as new orders land. “Added to cart but did not buy” empties the moment the customer buys, which is the one outcome the segment exists to produce. The membership that matters is the membership right now, and right now keeps moving.
RudderStack says so, in the plainest sentence on the page: “Real-time data collection and continuous segment refresh are necessary to keep campaigns relevant as customer behavior changes.” Salesforce’s guide, which ranks above it, does not say how often a behavioral segment should be recomputed; the word refresh does not appear. That absence is the industry’s habit in one page: behavioral segments are taught like the other three types, as if membership were a trait, and the clock inside them is left to whoever builds the flow.
The flow is where the clock bites. On most email platforms a segment is attached to a message, and the segment is evaluated when the flow runs, on a schedule or on a trigger. Between evaluations, the list is a photograph. A win-back message built for “no order in 90 days” reaches a customer who ordered yesterday if the segment was computed the day before. A cart reminder reaches someone who checked out an hour ago if the delay was set to two hours and nobody checked the exit condition. These are not bugs in any one platform. They are what a list built from events does between refreshes.
There is a second tell in Salesforce’s guide, and it points the other way. Under purchasing behavior: “Purchasing behavior varies from customer to customer and can be difficult to quantify. It may be best to use customer surveys to learn this information.” Under benefits: “Customer surveys and A/B testing can really help you uncover the true motivations of your customers.”
Two of the six behavioral subcategories, by the guide’s own account, cannot be read from behavior. They have to be asked. Why a customer chose one product over another, and what benefit they were after, are motivations, and motivations are psychographics wearing a behavioral label. Strip them out and what remains of behavioral segmentation is the part with timestamps: when they bought, how often, how much, where they are in the buying stage. That is the part that is actually observable, and it is exactly the part that expires.
The fix the vendors offer is faster refresh. Compute the segment continuously and the photograph becomes a video. That helps, and it keeps the segment as the unit: a group, defined by a threshold someone chose, attached to a message someone wrote.
The other fix is to stop building the group. Relvino does not evaluate “purchased within the last 30 days.” For each shopper, each event, a product viewed, a checkout started, an order placed, a week of silence, is a reason to reconsider that one shopper: whether to act at all, on which channel (email, SMS/MMS or a pop-up), with what offer, and when. The decision is made in under 80ms from the shopper’s own events, with no threshold, because there is no list to have an edge. Declining to send is a decision too, recorded per shopper, which is the behavior a segment cannot have: a segment either includes a person or it does not.
The cold start that every segmentation scheme handles with a “new customer” bucket is handled with a prior. A Large Retail Model trained on 7M+ data points across 10K+ retailers knows what a first order in that category tends to lead to, and the shopper’s own behavior takes over from there. The brand sets guardrails once: margin floors, quiet hours, channel limits, brand voice. The AI marketing automation guide gives a test for whether a platform has made that shift: count the segments and flows a team still maintains a year after adding the AI.
In the list below, the segmentation column is assembled from the two guides quoted above; quoted phrases are theirs and the rest is a plain reading of the practice. The decisioning column describes Relvino.
For a brand that segments today, the test is cheap: pick the busiest behavioral segment, note when it was last evaluated, and count how many of its members have had an event since. For a brand deciding whether to keep building lists, the Klaviyo vs Relvino comparison sets up a 14-day pilot beside the current setup, and pricing is public. The lifecycle marketing guide covers the stage model that behavioral segments usually serve, agentic marketing covers who owns the decision once the segment is gone, and the abandoned cart vs abandoned checkout guide is the clearest case of a behavioral segment with a clock inside it.
Demographic, geographic, psychographic and behavioral. Salesforce’s guide lists them in that order and calls behavioral arguably the most useful. The first three describe who a person is: age and income, where they live, how they see themselves. The fourth describes what a person did, and RudderStack’s guide defines its inputs as time-stamped records of what a person did, when they did it, and how often. That difference in inputs is why a behavioral segment goes out of date in a way the other three do not.
Customers who purchased within the last 30 days, the example RudderStack’s comparison table uses. A quick test of whether a segment is behavioral is to ask what removes a person from it. For that one, the passing of a day. For cart abandoners, the purchase the segment exists to produce. For heavy users, a quiet month. If the answer is an event or the clock, the segment is behavioral and will need recomputing; if the answer is a change in who the person is, it belongs to one of the other three types and can sit still for a year.
A reminder sent after a checkout is abandoned, a browse-abandonment message after a product is viewed twice and not bought, a replenishment reminder timed to a consumable’s reorder cycle, a win-back offer after a period without orders, and a welcome series that changes depending on what the first order was. Each one attaches a message to a behavioral segment. On most platforms the segment is a rule with a threshold, and the message goes to everyone who matches it at the moment the flow runs.
Psychographic segmentation groups people by attitudes, lifestyle and how they see themselves, which has to be inferred or asked. Behavioral segmentation groups people by observed actions, which are recorded. RudderStack puts the relationship this way: behavior tells you what a customer did while other signals suggest why. The practical difference is in the data: a psychographic trait is roughly stable for years, while a behavioral segment can gain or lose a member with every order, visit or click.
At the rate the segment’s inputs change, which for an online store means every order, visit and click, and every midnight for any window measured in days. A nightly recompute is the floor for a segment such as purchased in the last 30 days; the real fix is to have each flow re-evaluate the segment at send time rather than at the moment it was scheduled, and to give every flow an exit condition for the event the segment was built around. RudderStack recommends continuous refresh for the same reason. A per-shopper decision system removes the cadence question by not keeping a list to refresh.
About 30 minutes for the technical cutover: connect the Shopify store, point the sending domain, connect SMS, and order and browse history ingest automatically. No segments are rebuilt, because there are no segments; each shopper is handled by a decision made in under 80ms from their own events, inside guardrails the brand sets once, such as margin floors, quiet hours and channel limits. Revenue is then proven in a 14-day pilot run beside the current setup.