Summary: The 7Mind mobile app uses six vendors across the analytics, attribution, engagement, error-tracking, feature-flag and A/B-test layers. Some of them (Rudderstack, Braze) also appear on the backend side. Since the 2026-09-14 migration, Rudderstack is also the ingestion path for practice history into the Gymondo platform, and all identities use the numeric Gymondo user id. Since app 4.0.6 Braze feature flags run rollouts and A/B tests; Amplitude Experiment is gone. Sources: direct code inspection (pubspec.yaml, lib/app.dart, lib/features/core/data/services/configuration/, lib/features/core/data/services/analytics/ in 7mind-mobile-apps-monorepo); re-checked against origin/main at 4.0.9 on 2026-11-09 (braze_configurations_provider.dart, braze_feature_flags.dart, configurations.dart, feature_flags.dart, documentation/docs/basic/ab_testing.md, PR 1579 for MIND-880, AppDelegate.swift, AndroidManifest.xml) Last updated: 2026-11-09


What each vendor does

VendorPackageRole
Rudderstackrudder_sdk_flutter 3.3.0Primary CDP. Mirrors analytics events to downstream destinations. Since 2026-09-14 the content piece events (started, completed, cancelled) are also how practice history reaches Gymondo: Rudderstack webhook to service-event-broker to function-statistic. The app never POSTs completions itself.
Adjustadjust_sdk 5.6.2Install attribution; also resolves shortlink URLs on iOS for deep linking. See mobile-deep-linking.
Brazebraze_plugin 16.0.0Engagement (in-app messages, push, content cards, lifecycle campaigns), and since MIND-880 (app 4.0.6) feature flags for rollouts and A/B tests. Called directly at sdk.fra-01.braze.eu. Backend-sourced attributes and events now come from Gymondo (function-braze-event-handler, one key per vendor) on the Gymondo event schema.
Sentrysentry_flutter 9.8.0Crash and error reporting.
ConfigCatconfigcat_client 4.1.1App-wide feature flags per environment, e.g. isSosToolkitEnabled, isAppleHealthEnabled, isCourseProgressionEnabled.
Firebasefirebase_core 3.15.0 + firebase_messaging 15.2.9Push transport only. No firebase_auth, no firebase_analytics.

Why ConfigCat and Braze flags both exist

ConfigCat holds plain on/off switches that are the same for every user of an environment (lib/features/core/data/services/configuration/feature_flags.dart). Braze feature flags (MIND-880) hold everything that targets users: rollouts to a segment and A/B tests. They follow the Braze user, so a user keeps the same flag and variant on every device. Treat ConfigCat as “is this feature on” and Braze as “is it on for this user, and which variant did the user land in”.

How the Braze flags work in the app (braze_configurations_provider.dart, repo doc documentation/docs/basic/ab_testing.md):

  • A rollout is a plain Braze flag that is on or off for the user.
  • An experiment is a flag that stays enabled in every arm and sets the string property variant to control, treatment or challenger. A missing or disabled flag means “not allocated” and reads as off.
  • Startup uses the flags Braze cached in the last session. The native SDK refreshes them with every new session, at most every five minutes, and again after login. Gates read once at startup, like the module routes and ff_aury, pick up a change on the next cold start.
  • Reading an experiment variant logs a Braze feature flag impression, once per flag and app session. Braze needs it to count users, control included.
  • Flag ids live in BrazeFeatureFlags: ff_aury, ff_content_collections, ff_app_intro_offer_experiment, ff_3p_recommendations (parked; the flag does not exist in Braze, so the section is off).

Amplitude Experiment was removed with MIND-880 (PR 1579, merged 2026-10-14, app 4.0.6). The repo doc gives the reason: the Amplitude contract ends on 2026-11-30. The exposure event the app still sends to its analytics providers keeps the Amplitude name $exposure.

Cross-repo overlap

Two vendors have configurations on both the mobile app and the backend. Since 2026-09-14 the backend side is the Gymondo platform (see platform-unification); before that it was elixir-backend.

  • Rudderstack: the app sends events with the 7Mind write key. The Gymondo service-event-broker receives the content piece events through a Rudderstack webhook (/api/v1/{vendor}/events/sevenmind) and turns them into meditation statistics and streaks. The old Elixir Pub/Sub consumer still records the same events in parallel. Since TP-602 (2026-10-05) the website’s anonymous funnel events also go straight to Rudderstack. Rudderstack stays “for now”; deprecating it is on the platform’s list of future topics.
  • Braze: same Braze account as before, but backend-sourced attributes and events switched to the Gymondo schema at cutover, and CRM rebuilt the automations between 14 and 16 Sep 2026. There are three 7Mind Braze workspaces (new, legacy, B2B). The mobile app uses Braze for push, in-app messages and feature flags.

Identity after the migration

The app now identifies users by the numeric Gymondo id in Rudderstack, Braze, Adjust and Sentry. All four also receive the retired 7Mind UUID as an extra attribute (legacy_uuid). Braze feature flags follow the Braze user, so they are keyed by the numeric id too. Events from users still logged in from before the migration carried the old UUID and were dropped by function-statistic until a content_user_id fallback shipped (MIND-863, 2026-10-06). See gymondo-sso-auth.

Reporting

Looker dashboards on the 7Mind BigQuery tables are obsolete. Reporting moved to Tableau (7NXT); the BigQuery tables are to be deprecated after validation.

Raised 2026-10-05 (MIND-843), independent of the migration: Adjust, Braze and Sentry start before valid consent in both the 7Mind and Gymondo apps.

When debugging “why did this event arrive twice in Rudderstack?”, check whether both client and server are emitting it. This is intentional in some cases (client-side click vs server-side confirmation) and accidental in others.

Aury analytics

The Aury AI companion has dedicated tracking helpers in lib/features/core/data/services/analytics/ai_companion_analytics.dart: trackAuryChatOpened(), trackAuryChatClosed(), trackAuryConsentGiven(), etc. These go through the app’s analytics providers (Rudderstack, Adjust, Braze). See aury-companion.

What agents should know

  • Never add a fourth analytics vendor without confirming the event taxonomy. Adding a new SDK that duplicates Rudderstack’s role is a known anti-pattern in this codebase.
  • For an app-wide switch, use ConfigCat (feature_flags.dart). For a per-user rollout or an A/B test, use a Braze flag: add the id to BrazeFeatureFlags and read it with Configurations.isFeatureEnabled or Configurations.getVariant.
  • Firebase Analytics is intentionally not installed. Do not introduce firebase_analytics to “track an extra event”: use Rudderstack instead.
  • Sentry is the only error sink. Don’t add a competing crash reporter.
  • Push is handled natively by Braze: BrazeFirebaseMessagingService on Android (FCM), the Braze notification handling in AppDelegate.swift on iOS (APNs). No Dart code uses firebase_messaging directly.