Comparisons
by fullstorydevb20614e2d08dNo license11 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 3 days ago
How to structure A vs B comparisons in Fullstory — when to use dimensionality (event/session properties) vs separate segments (user-level properties), and why the distinction matters for correctness.
- b20614e2d08dCurrentcommit b20614ePublished Oct 8, 2026
Source and attribution
Source:fullstorydev/fullstory-skillsinskills/comparisonsat commitb20614e
License: No license
Content belongs to its original authors. SourceWeft indexes it from a public repository.
More from fullstorydev/fullstory-skills
Session Review
fullstorydev
Reviews Fullstory session recordings via MCP tools to diagnose reported bugs, investigate errors, and validate UI behavior.
General Analysis
fullstorydev
Guides a Fullstory analytics workflow: build segments and metrics, compute results, then inspect sessions for context.
More in Data & Analytics
Spanner Basics
Guides Google Cloud Spanner administration, schema design, querying and performance diagnosis.
Gke Cost Analysis
Answers natural-language questions about GKE cluster and workload costs using BigQuery billing exports and live cluster metrics.
Datalineage Bigquery Asset Impact Analysis
Guides an agent through downstream impact (blast radius) analysis for a BigQuery table or view using Data Lineage.
Bigquery Troubleshooting
Diagnoses failing, slow, or unexpectedly expensive BigQuery jobs through structured root-cause workflows.
Bigquery Optimization
Guides BigQuery cost and performance optimization across capacity editions, storage layout, and SQL queries.
Bigquery Bigframes
Guides writing Python code with BigQuery DataFrames (BigFrames) for data processing, analysis, and machine learning.