Behavioral Segment

Origin & evolution

Market segmentation was named by Wendell R. Smith in his 1956 Journal of Marketing paper Product Differentiation and Market Segmentation as Alternative Marketing Strategies, which argued that a heterogeneous market is better served as several smaller homogeneous ones, each with a tailored offer. Early practice leaned on demographics and geography because those variables were cheap to obtain and easy to count.

The behavioural turn came from direct marketers who had transaction data and a reason to use it. RFM analysis, which scores customers on Recency, Frequency, and Monetary value, had been used by catalogue marketers for decades and was codified for a wider audience by Arthur Hughes in Strategic Database Marketing (1994). RFM was the first widely taught segmentation built entirely on observed behaviour, three numbers about what a customer had actually done, and it consistently out-predicted demographic cuts of the same base. Database marketing practitioners treated recency in particular as the single most predictive variable for repeat purchase.

Software product analytics completed the shift. The arrival of event-tracking tools let teams segment on in-product actions directly: users who reached an activation milestone⛳MilestoneProgram ManagementA key date or achievementView reference →, users who use a feature⭐FeatureProduct SpecificationA product capability or featureView reference → weekly, users who have gone dormant. The Jobs🔨JobUserJob To Be Done: what the user is trying to accomplishView reference →-to-be-Done tradition supplied the theory for why this works. Clayton Christensen's milkshake argument was that two people in the same demographic box can hire a product for completely different jobs, so attributes mislead and behaviour reveals. The working consensus settled there. The better the data a team has, the further it moves from who-users-are toward what-users-do.

How it works in practice

A note-taking product finds its demographic segments useless. "Knowledge workers aged 25 to 40" sign up, retain, and churn in no consistent pattern, so the cut explains nothing and predicts nothing. The team re-cuts the base on behaviour and two real segments appear.

One group writes daily in long desktop sessions and lives in the editor. The other captures short fragments on mobile and rarely opens the desktop app. These behavioural segments predict cleanly: the daily writers retain at 90 percent and want richer formatting, while the fragment capturers churn at triple the rate and want faster mobile capture. The roadmap🛣️RoadmapProduct SpecificationA strategic plan of features and milestonesView reference → argument demographics could never settle now resolves, because the two segments want opposite things and the team can see which one its growth depends on. Each segment is also a live measurement, so the team watches the split move as the product changes.

Behavioural segment vs. its neighbours

• Persona🎭PersonaUserAn archetype representing a user segmentView reference → is a single named, evidence🔎EvidenceValidationData supporting or refuting a hypothesisView reference →-based individual standing in for a group, built to carry design empathy. A behavioural segment is the group itself, usually a count or a percentage of the base. The persona is who; the segment is how many and doing what.
• Cohort👥CohortGrowthA group of users sharing a common characteristicView reference → is a group defined by a shared moment, such as everyone who signed up in March, and is built to track how one intake changes over time. A behavioural segment slices the base by ongoing behaviour at any moment, regardless of when people joined. Cohorts watch a vintage age; segments group by what people currently do.
• Ideal customer profile👤Ideal Customer ProfileGo-To-MarketThe ideal customer profile (ICP)View reference → is the account a go-to-market team most wants to acquire, a forward-looking target. A behavioural segment describes how the existing base actually divides today. They overlap when your best behavioural segment matches your target profile, and that match is itself a useful signal that acquisition and product are aligned.

In the graph

In the Unified Product Graph, behavioral_segment🐾Behavioral SegmentGrowthA user segment based on behaviour is the canonical successor to the deprecated generic segment🐾Behavioral SegmentGrowthA user segment based on behaviour type, which left "behavioural" as one option among several and let teams quietly default to demographics. The narrower name makes the anchoring explicit. It sits in the Business, GTM and Growth region as a container, and its edges encode why a behaviourally defined group is worth having. product_segments_into_behavioral_segmentProductsegments intoBehavioral Segmenthierarchy ties it to the product whose users it divides, and behavioral_segment_maps_to_personaBehavioral Segmentmaps toPersonacross-domain reaches across into the Users and Needs🫀NeedUserA user need, pain, desire, or constraintView reference → region so a number connects to a recognisable human. The activation edges show what a behavioural segment is for: growth_campaign_targets_behavioral_segmentGrowth CampaigntargetsBehavioral Segmentcross-domain, acquisition_channel_targets_behavioral_segmentAcquisition ChanneltargetsBehavioral Segmentcross-domain, pricing_tier_targets_behavioral_segmentPricing TiertargetsBehavioral Segmentcross-domain, and experiment_plan_targets_behavioral_segmentExperiment PlantargetsBehavioral Segmentcross-domain each point a lever at the group. A segment worth keeping maps to a person and aims at least one of those levers; a segment that does neither is a slice nobody acts on.