Skip to content

feat(conversations): Add Amplitude analytics to conversation pages#115622

Merged
obostjancic merged 2 commits into
masterfrom
ognjenbostjancic/tet-2351-conversations-analytics
May 18, 2026
Merged

feat(conversations): Add Amplitude analytics to conversation pages#115622
obostjancic merged 2 commits into
masterfrom
ognjenbostjancic/tet-2351-conversations-analytics

Conversation

@obostjancic
Copy link
Copy Markdown
Member

@obostjancic obostjancic commented May 15, 2026

Add comprehensive Amplitude analytics tracking to the conversations feature to understand how users interact with the conversations table and detail pages.

Remove unused drawer.open and drawer.span-select event definitions that were never wired up, and rename drawer.tab-switch to detail.tab-switch since the drawer no longer exists.

Closes TET-2351

@linear-code
Copy link
Copy Markdown

linear-code Bot commented May 15, 2026

TET-2351

@github-actions github-actions Bot added the Scope: Frontend Automatically applied to PRs that change frontend components label May 15, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 15, 2026

📊 Type Coverage Diff

✅ No new type safety issues introduced. Coverage: 93.53%

@obostjancic obostjancic force-pushed the ognjenbostjancic/tet-2351-conversations-analytics branch from 9042232 to 09cada2 Compare May 15, 2026 10:35
@obostjancic obostjancic force-pushed the ognjenbostjancic/tet-2351-conversations-analytics branch from 09cada2 to 24a0f34 Compare May 18, 2026 08:53
@obostjancic obostjancic force-pushed the ognjenbostjancic/tet-2351-conversations-analytics branch from 24a0f34 to 45d33f1 Compare May 18, 2026 08:58
Add comprehensive analytics tracking to the conversations feature:

- Table: track clicks on conversation ID, input/output rows, pagination,
  and search submissions
- Detail page: track page view, span selection, copy conversation ID,
  trace link clicks, and errors link clicks
- Messages: track message clicks (with role) and tool call clicks
- Rename stale drawer.tab-switch event to detail.tab-switch
- Remove unused drawer.open and drawer.span-select event definitions

Closes LINEAR-TET-2351
@obostjancic obostjancic force-pushed the ognjenbostjancic/tet-2351-conversations-analytics branch from 45d33f1 to 717a0f3 Compare May 18, 2026 09:34
@obostjancic obostjancic marked this pull request as ready for review May 18, 2026 10:23
@obostjancic obostjancic requested review from a team as code owners May 18, 2026 10:23
Copy link
Copy Markdown
Contributor

@cursor cursor Bot left a comment

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 2 potential issues.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 717a0f3. Configure here.

Comment thread static/app/views/explore/conversations/components/conversationSummary.tsx Outdated
Comment thread static/app/views/explore/conversations/conversationDetail.tsx Outdated
Comment thread static/app/utils/analytics/conversationsAnalyticsEvents.tsx Outdated
- Fix shared ConversationAggregatesBar firing detail-specific analytics
  from trace AI tab by accepting an optional onErrorsLinkClick callback
- Add conversationId to page-view useEffect dependency array so
  navigating between conversations fires a new page-view event
- Remove duplicate conversations.table.search analytics event since
  search bars already have built-in analytics with source and query metadata
@obostjancic obostjancic merged commit 794ab37 into master May 18, 2026
74 checks passed
@obostjancic obostjancic deleted the ognjenbostjancic/tet-2351-conversations-analytics branch May 18, 2026 11:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants