Skip to content

Conversation

@danyelf
Copy link
Contributor

@danyelf danyelf commented Dec 7, 2025

Summary

This PR adds instrumentation to track all "explore action" interactions throughout the UI, capturing what action was chosen and where it was triggered from.

PLA-518

Tracking Categories

  1. Explore Actions: Track WHAT action (row_count, profile_diff, value_diff, etc.) and WHERE it was triggered (lineage menu, node sidebar, schema view, etc.)
  2. Form Interactions: Track when users click Execute vs Cancel on action forms
  3. Lineage Selections: Track selection actions (parent/child nodes, upstream/downstream) - We did this because it's the same menu as the lineage menu actions

Implementation Details

  • Constants defined in track.ts: EXPLORE_ACTION, EXPLORE_SOURCE, EXPLORE_FORM_EVENT, LINEAGE_SELECTION_ACTION
  • Type guards prevent tracking non-explore actions

Examples of Instrumentation

  1. Explore Action Tracking - [Web] explore_action

Event Name: "[Web] explore_action"

Examples of properties sent:

When clicking row count button from schema

  {
    action: "row_count",
    source: "schema_row_count_button",
    node_count: 1
  }

When running profile from node sidebar (single env)

  {
    action: "profile",
    source: "node_sidebar_single_env",
    node_count: 1
  }
  {
    action: "profile_diff",
    source: "node_sidebar_multi_env",
    node_count: 1
  }
  1. Lineage Selection Tracking - [Web] lineage_selection
  {
    action: "select_child_nodes",
  }
  1. Explore Action Form Tracking - [Web] explore_action_form

// When user clicks Execute button on value diff form

  {
    action: "value_diff",
    event: "execute" // or "cancel"
  }

Files Modified

  • track.ts: Added tracking constants and functions
  • RunModal.tsx: Track execute/cancel on explore action forms
  • useValueDiffAlertDialog.tsx: Track value diff confirmation dialog
  • LineageViewContextMenu.tsx: Track explore actions and lineage selections
  • NodeView.tsx: Track actions from node sidebar
  • ColumnNameCell.tsx: Track actions from schema view
  • useMultiNodesAction.ts: Track multi-node actions from top bar

🤖 Generated with Claude Code

Co-Authored-By: Claude [email protected]

…tions

This adds instrumentation to track all explore action interactions throughout the UI,
capturing what action was chosen and where it was triggered from.

Tracking categories:
- Explore actions: Track WHAT action (row_count, profile_diff, value_diff, etc.)
  and WHERE it was triggered (lineage menu, node sidebar, schema view, etc.)
- Form interactions: Track when users click Execute vs Cancel on action forms
- Lineage selections: Track selection actions (parent/child nodes, upstream/downstream)

Implementation:
- All action names and sources use constants (no magic strings)
- Constants defined in track.ts: EXPLORE_ACTION, EXPLORE_SOURCE, EXPLORE_FORM_EVENT, LINEAGE_SELECTION_ACTION
- Type guards prevent tracking non-explore actions
- Console fallback for development when Amplitude not initialized

Files modified:
- track.ts: Added tracking constants and functions
- RunModal.tsx: Track execute/cancel on explore action forms
- useValueDiffAlertDialog.tsx: Track value diff confirmation dialog
- LineageViewContextMenu.tsx: Track explore actions and lineage selections
- NodeView.tsx: Track actions from node sidebar
- ColumnNameCell.tsx: Track actions from schema view
- useMultiNodesAction.ts: Track multi-node actions from top bar

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>
Signed-off-by: danyel fisher <[email protected]>
@danyelf danyelf force-pushed the danyel.explore-action-tracking branch from 4591fcf to 421cd4c Compare December 7, 2025 23:18
@danyelf danyelf requested review from gcko and popcornylu December 7, 2025 23:26
@danyelf danyelf changed the title feat: Add comprehensive tracking for explore actions and user interactions feat: Add tracking for explore actions and user interactions Dec 7, 2025
Copy link
Contributor

@gcko gcko left a comment

Choose a reason for hiding this comment

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

LGTM

@gcko gcko merged commit 91cb576 into DataRecce:main Dec 9, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants