DashLX is a Lived Experience Data platform that connects wearable and activity data from fitness platforms including Garmin, Strava, Apple, Fitbit, Coros, Polar, and Suunto, into brand CRM, CDP and Experience Management systems. Athletic and outdoor brands use DashLX to power activity-based rewards and lifecycle marketing, and to capture real-world performance data for wear testing and product innovation.
DashLX has launched Segments, a new capability in the DashLX Admin App, alongside the static Lists customers already know. For brands running loyalty and lifecycle programs, or wear test and research panels, this changes how audiences get built and maintained.
Quick answer: DashLX Segments are criteria-based, self-updating audiences inside the DashLX Admin App. A brand defines the criteria once (for example, "completed a marathon in the last 30 days"), and membership updates automatically, refreshing as often as every hour, so audiences stay current without a manual rebuild. Static Lists remain available for groups that should stay fixed.
- Key Terms: Cohort, List, and Segment.
- The DashLX Admin App.
- What is Segment Builder.
- Why Self-Updating Audiences Matter for Athletic and Outdoor Brands.
- What Brands Can Do With Segments and Lists.
- Frequently Asked Questions.
- This Is What Lived Experience Data Is For.
Key Terms: Cohort, List, and Segment
Cohort: The entire group of opted-in consumers, members, or wear testers connected under one brand's program. This is the population a brand sees by default in the DashLX Dashboard. Brands may manage a single cohort or, if running the same program across multiple regions, manage a separate cohort per region.
List: A static, fixed subset of a brand's cohort. A brand admin builds it once, at a point in time, and it stays exactly as built even as the underlying data changes. A fixed event roster is a good example, where the whole point is that membership doesn't shift.
NEW! Segment: A dynamic, self-updating subset of a brand's cohort. A brand admin defines it by criteria, such as "completed a marathon in the last 30 days," and contacts are automatically added and removed as their underlying lived experience (LX) data changes. No manual rebuild required.
What Is Segment Builder
Previously, brand admins could see their cohort in the Dashboard and build static Lists, but couldn't build Segments. If a brand wanted to act on a shift in user behavior, someone had to notice the shift and rebuild a list by hand, which meant it was already out of date by the time it was ready to use.
Two capabilities ship alongside the Segment builder itself:
- Segment history: shows how a Segment's membership has ebbed and flowed over time, rather than only ever showing a single snapshot.
- Segment comparison tool: puts two Segments side by side to compare demographic composition, so brands can see how groups differ without a separate export or analysis step.
The DashLX Admin App
DashLX isn't just a data pipe connecting wearables to a brand's tech stack. DashLX customers also receive access to the Admin App, where brands can view what customers have opted into LX programs, and Segments and Lists are the tools for doing it.
Every DashLX customer has access to it, and the Dashboard is what they see by default when they log in: an overview of their cohort, with the ability to toggle between cohorts if a brand manages more than one.
Why Self-Updating Audiences Matter for Outdoor Brands
Two Kinds of Programs, One Shared Problem
DashLX serves two distinct types of enterprise programs, and Segments are relevant to both. For marketing and loyalty teams, DashLX connects opted-in athlete activity data into CRM and CDP systems to power rewards, personalization, and lifecycle triggers. For product and research teams, DashLX captures real-world performance data from wear testers and research participants to validate product development decisions.
In both cases, the underlying data never sits still. Athletes train, taper, get injured, pick up a new sport, or go quiet for a season, and a static List of cohort members built in January is a poor description of who that group is in August.
A Runner in Transition
Take a collegiate runner training for a fall marathon. A List built in January to capture "committed runners" for a shoe launch still shows that same person in August, even after a March stress fracture pushed them into eight weeks of cycling and swimming instead. The List was built once and doesn't know any of that happened, so the brand keeps sending marathon-training content to someone who hasn't run a step in weeks.
A Segment behaves differently. One defined by "consistent running activity in the last 30 days" would have quietly dropped that runner the moment their connected wearable data showed the shift, and a second Segment built around "rising cycling or swimming activity following a drop in running frequency" would have picked them up as a cross-training candidate within the hour.
Same athlete, same underlying data, but a brand running Segments is recommending cross-training gear the week the athlete actually needs it, instead of six weeks into a recovery it never noticed. Explore first, activate later: check what's true today before building a downstream experience on top of it. Lists remain the right tool wherever a group genuinely should stay fixed.
What Brands Can Do With Segments and Lists
Loyalty and Membership Programs
A List built once to capture "Gold tier members as of Q1" freezes that roster: someone who fell off in Q2 keeps getting Gold perks, and someone who qualified in Q3 gets none until the next rebuild.
A Segment of highly engaged members (for example, everyone currently meeting a minimum activity frequency threshold) shows brands who's earning that status right now, not who did it six months ago. That keeps tier-based or milestone-based rewards tied to current behavior instead of stale data.
Race Training Journeys
The same problem shows up in training programs. A List of everyone who registered for a marathon training block doesn't know who dropped out in week three or finished early and moved on but it still shows them months later.
A Segment of users currently in a marathon training block updates on its own as athletes enter and exit that window, triggering the right content, product recommendation, or support message at the right moment in that athlete's training.
Research and Product Panels
Wear-test panels have the same issue. A List of testers recruited for a two-year-old footwear study won't reflect testers who've long since stopped logging the mileage the study depends on.
A Segment of, say, millennial-aged trail runners meeting a minimum activity frequency threshold can be compared against that List, or against another Segment, to confirm who still actually qualifies. That gives product and research teams a faster way to check whether a panel actually represents the population they're trying to study, using DashLX's product research and wear testing tooling.
Across all of these, Segment and List membership can drive conditional logic for more personalized, relevant downstream experiences: in marketing and loyalty programs, in retail and ecommerce, and in product research.
Frequently Asked Questions About DashLX Segments:
What are Segments in DashLX?
Segments are dynamic, rule-based audiences inside the DashLX Admin App. A brand sets the criteria once, and membership updates automatically as customers' real activity changes, without anyone manually rebuilding the list.
What is a List in DashLX?
A List is a static, manually curated group of users. It's the right tool for a fixed group that shouldn't change on its own, like a set of race participants or beta testers, and it only updates when someone edits it by hand.
What's the difference between a Segment and a List in DashLX?
A List is something a brand builds once. A Segment is something that keeps building itself, adding and removing members automatically as their activity data changes, so it stays current without manual upkeep.
How often do Segments update?
Segments refresh automatically on a schedule configured for each use case. The right cadence depends on how quickly the criteria are likely to change and what happens when someone enters or leaves the Segment. A group used for a weekly research review might refresh weekly, while one supporting a timely customer journey might refresh daily or hourly. Updates also depend on when data from connected sources becomes available.
Do brands need engineering support to build Segments or Lists?
No. Segments and Lists are both built directly in the DashLX Admin App by whoever manages the brand's LX programs, without needing an engineering team to write custom queries or exports.
Who has access to Segments today?
Availability varies by program, and every customer has access to the Admin App and its default Dashboard view regardless. Brands should check with their DashLX customer success representative to confirm what's available on their account.
This Is What Lived Experience Data Is For
Segments aren't just a filtering tool layered on top of existing data. They're the connective layer between raw LX data collection and everything downstream that depends on knowing who, within a brand's cohort, belongs to a meaningful group: personalization, activation, trend analysis.
Lists already solved static grouping. Segments answer the harder question: what happens when the underlying data keeps changing but the grouping doesn't. That's the actual promise of Lived Experience Data — it's supposed to reflect what's happening now, not a snapshot from setup day.
Already running DashLX? Ask your customer success representative about turning on Segments for your account. New to DashLX? Ask about Segments and Lists when you book a demo.
Book a Demo
-Photoroom%201.png)
.svg)