Skip to content

docs: Add Analytics & Product Event Tracking Specification#35

Merged
phertyameen merged 1 commit intobridgelet-org:mainfrom
BigBen-7:docs/analytics-event-tracking-spec
Mar 6, 2026
Merged

docs: Add Analytics & Product Event Tracking Specification#35
phertyameen merged 1 commit intobridgelet-org:mainfrom
BigBen-7:docs/analytics-event-tracking-spec

Conversation

@BigBen-7
Copy link
Contributor

@BigBen-7 BigBen-7 commented Mar 5, 2026

Summary

Closes #33

Adds /docs/analytics-spec.md — a structured product analytics specification for Bridgelet based on the FRD, ROADMAP, and frontend technical spec.

  • Event naming convention — Noun Past-Tense Verb in Title Case with snake_case properties; journey-scoped via a journey field on every payload
  • Standard base payload — common properties (anonymous_id, session_id, device_type, network, etc.) on every event with explicit privacy guidance (no PII, no raw wallet addresses)
  • Sender journey — 18 events from homepage view through payment creation, link sharing, and dashboard actions (cancel, reclaim)
  • Recipient journey — 13 events from claim link open through token verification, wallet entry, sweep execution, and viral CTA
  • Error taxonomy — unified Error Displayed event with a standard error_type enum covering all FRD error states
  • 3 conversion funnels — Sender Activation, Recipient Claim, and End-to-End, each with stage-by-stage drop-off metrics
  • Business KPIs — formulas defined for Claim Conversion Rate, Time to Claim, Expiry Rate, Reclaim Rate, Viral K-Factor, and operational health metrics
  • Implementation notes — non-normative guidance on platform choice, client vs. server-side event sourcing, identity strategy, deduplication, and DNT compliance

Test plan

  • Review event names and properties against the FRD user journeys
  • Confirm no PII or raw wallet addresses appear in any payload definition
  • Verify all FRD error states are covered by the error_type enum
  • Confirm funnel stages map correctly to defined events
  • Check KPI formulas for correctness

@BigBen-7 @claude
docs: add analytics & product event tracking specification
aec0ff3 
Closes bridgelet-org#33

Defines the full analytics spec for Bridgelet including:
- Event naming conventions (Noun Past-Tense Verb, Title Case)
- Standard base payload structure with privacy guidance
- 18 sender journey events (homepage → payment → dashboard)
- 13 recipient journey events (claim open → sweep success)
- Unified error event taxonomy with standard error_type enum
- 3 conversion funnel definitions with stage-by-stage drop-off metrics
- Business KPIs with formulas (CCR, TTC, Expiry Rate, Reclaim Rate, etc.)
- Implementation notes covering platform choice, client/server sourcing,
  identity management, deduplication, and DNT compliance

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
phertyameen
phertyameen approved these changes Mar 6, 2026
View reviewed changes
Copy link
Contributor

@phertyameen phertyameen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is over and beyond expectation. Thank you for your contribution.

@phertyameen phertyameen merged commit 6bab7cf into bridgelet-org:main Mar 6, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@phertyameen phertyameen phertyameen approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

docs: Define Analytics & Product Event Tracking Spec

2 participants

@BigBen-7 @phertyameen