packages/analytics implementation is never wired into packages/ui — it's dead code

[BigBen-7]

What's wrong

`packages/analytics` has a real, tested implementation: `EventEmitter`, `ConsoleSink`/`HttpSink`/`FileSink`, sampling, deduplication, retry, PII scrubbing, a dead-letter queue — 87 passing tests across 14 files.

`packages/ui` has a completely separate, ad-hoc analytics implementation instead of using it:

• `packages/ui/src/lib/analytics.ts` (28 lines) — its own `track()` + listener registry
• `packages/ui/src/lib/analyticsEvents.ts`, `analyticsPrivacy.ts`, `apiErrorTracking.ts`, `searchTracking.ts` — more parallel, hand-rolled tracking helpers

Nothing in `packages/ui` imports `@stellar-explain/analytics` (checked — zero matches). Whatever `packages/analytics` does (sampling, retry, PII scrubbing, sinks) never actually runs in the app; the UI's own mini-implementation has none of that behavior.

Why it matters

This is likely why analytics "isn't working" in practice — the tested, feature-complete package sits unused while a much thinner duplicate handles real traffic with none of its guarantees (no retry on failed sends, no PII scrubbing, no sampling).

Suggested fix

Either:

1. Have `packages/ui`'s tracking calls actually construct and use an `EventEmitter` from `@stellar-explain/analytics` with a real sink (`HttpSink` pointed at the analytics endpoint), removing the duplicate `lib/analytics*.ts` files, or
2. If the UI-side implementation was intentionally kept separate for a reason, document why and what `packages/analytics` is actually for.

Depends on #853 — the package has no entry point yet, so it can't be imported until that lands.

[midenotch]

Hi Maintainer,
Interested in working on this issue. I'll implement the requested changes and ensure everything is properly tested before submission.

Payout wallet (Stellar): GBLT6QSRPF7YGSCOWEOGBXKS2DRKOPBLF6QHJAD6QCNCWWQ54E2NJ4AB
GrantFox OSS campaign — smart escrow payout on merge.

[phertyameen]

I’d like to take this on by connecting the UI to the existing @stellar-explain/analytics implementation rather than maintaining a second tracking system.

I’ll integrate EventEmitter with the appropriate sink, migrate the existing UI tracking calls, and remove the redundant analytics helpers once their functionality is covered. I’ll also verify that features like retry, sampling, deduplication, and PII scrubbing are actually applied to UI events.

I’ll treat #853 as a dependency and keep the integration focused on eliminating the current disconnect without introducing unnecessary changes.

[grantfox-oss]

🦊 GrantFox — @phertyameen has been assigned to this issue as part of the Third Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #851)
2. Your PR will be reviewed by the StellarCommons maintainers

Good luck! Track your progress on GrantFox.

[Tinna23]

@phertyameen proceed please issue #853 has been merged to main.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Third Campaign campaign!

@phertyameen's PR #857 was approved and merged by @Tinna23.

🏆 @phertyameen: You earned 40 FoxPoints for this contribution! Your current tier: Builder (1,255 total points). Track your full progress on GrantFox.

👏 Great work, @phertyameen! Keep contributing to StellarCommons.