Rheo
Segment definition used in both an analytics report and an Engage automation audience
Product

Segments that power Analytics reports and Engage sends

Define behavioral segments once in Rheo and use them for Analytics cohort analysis, Convert targeting, and Engage broadcasts and automations: without CSV exports.

Segments are the handoff point between understanding users and acting on that understanding. When segments live only in a analytics vendor, growth exports CSVs. When they live only in email tools, product cannot reproduce the audience in a funnel chart. Rheo defines segments on the unified customer profile so Analytics, Convert, and Engage read the same rules.

This post explains segment types, authoring patterns, consent gates, and operational hygiene: so your next win-back send targets exactly the users who stalled on the paywall last week.

Why one segment definition matters

Problem with duplicate definitionsConsequence
“Power users” means 5 sessions in analytics, 10 in CRMWrong send size
Funnel segment not available in EngageDelayed campaigns
Manual refreshStale audiences

Rheo segments are declarative: traits, events, and time windows evaluated against the profile.

Building blocks

Building blockExample
Traitplan = free, marketing_email_consent = true
Event countpaywall_viewed ≥ 2 in last 7 days
Event sequencetrial_started without purchase_completed in 14 days
Revenuelifetime_revenue > 0 from billing integration
Flow stateStarted onboarding v12, did not complete
Platformplatform = ios

Combine with AND/OR; nest for advanced cases per your workspace features.

Lifecycle of a segment definition

Segments are not static labels: they move through a simple lifecycle:

StageAction
DraftProduct proposes rule on paper; validate event exists in staging
ValidateCompare segment size to manual SQL or legacy tool export
ActiveUsed in dashboards and at least one Engage or Convert surface
MonitorSize and conversion impact tracked weekly
ArchiveRule deprecated; automations detached

Skipping validate is how teams send email to zero users or to the entire database.

Segment patterns for subscription apps

Acquisition quality

Segment nameRule sketchAnalyticsEngage
Paid social trialistssource = facebook + trial_started 7dCohort retentionEducate on day 3
Organic high intentOrganic + paywall_viewedFunnel compareOptional nudge

Onboarding and Convert

Segment nameRule sketchAnalyticsEngage
Stuck step 4Flow step reached, not complete 48hDrop-off confirmEmail with deep link
Experiment control holdoutVariant = controlLift analysisExclude from promo

Tie to onboarding funnel drop-off.

Revenue and churn

Segment nameRule sketchAnalyticsEngage
Trial endingtrial_ends_at within 48hConversion ratePush + email
Lapsed paidWas subscriber, not activeLTV post-mortemWin-back journey

Billing traits sync from RevenueCat/Stripe; verify latency in docs.

Always intersect promotional audiences:

marketing_email_consent = true
AND NOT unsubscribed
AND <your behavioral rule>

See marketing consent.

Analytics: segments as lenses

In Analytics reports:

  • Filter funnels and retention by segment.
  • Compare completion rates: stuck users vs completers.
  • Attribute revenue: which segment drove MRR this month?

Export segment definitions in team wiki: not one-off screenshots: so Engage authors trust the numbers.

Engage: segments as audiences

Send typeSegment use
BroadcastSnapshot audience at send time
Automation entryUser enters when segment becomes true (or on event + segment)

Dynamic membership: user who fixes onboarding exits “stuck” segment automatically: avoid sending “finish setup” after completion.

Automation triggered when segment conditions match

Convert: targeting experiments

Use segments to restrict who sees a channel or experiment arm:

  • iOS-only fix for layout bug.
  • Locale-specific flow for DE users.
  • Exclude employees via is_internal trait.

Experiment analysis still segments by variantId inside targeted population.

Operational hygiene

PracticeFrequency
Name segments with owner prefix growth_trial_endingAlways
Document definition in description fieldOn create
Review size before broadcastEach send
Archive unused segmentsQuarterly
Test with internal profilesEach new rule
Red flagAction
Segment size 0Rule typo or missing events
Segment = entire MAUMissing consent filter
Sudden 10x jumpBilling sync or event duplicate

Segments vs tags vs lists

ConceptRheo approach
Static email listPrefer dynamic segment
One-off CSV uploadLast resort; breaks loop
Real-time event triggerAutomation entry event
Slow-changing traitSegment on trait

Advanced: warehouse-enriched traits

If you compute scores in Snowflake, push traits via API on schedule:

churn_risk_score updated nightly → segment churn_risk > 0.8 for Engage.

Keep operational segments in Rheo; keep model features in warehouse with thin sync.

Connect to the growth loop

  1. Analyze funnel → identify population.
  2. Segment define rule.
  3. Convert fix in-app for subset OR Engage message subset.
  4. Analyze again: did segment shrink?

Hub post: Analyze → segment → convert → engage.

Worked example: paywall stall end-to-end

Monday: Analyze: Funnel on live onboarding pin shows 58% loss between personalization and paywall on Android only.

Tuesday: Segment: Create growth_android_paywall_stall = reached paywall_viewed without trial_started within 72h, Android, live pin 19.

Wednesday: Convert: Publish variant B with one fewer screen before paywall; 50/50 experiment on Android channel.

Thursday: Engage: Automation entry on same segment (exclude experiment holdout if policy requires): wait 6h, email with deep link to channel.

Friday: Analyze: Compare trial start rate: segment size shrinking, experiment variant B + message arm vs control.

Document the segment ID in the experiment ticket so nobody re-exports a CSV “just for marketing.”

Collaboration norms

RoleOwns
ProductSegment naming, hypothesis
GrowthEngage copy and send calendar
EngineeringTrait correctness, billing sync
DataWarehouse traits pushed to profile

Weekly 15-minute segment review in shared doc: new segments, archived segments, size anomalies.

Bottom line

Segments are not a marketing feature: they are the contract between analytics and action. Rheo teams that treat them as shared infrastructure ship campaigns that match what the dashboard already proved.

Start for free