Skip to content

Conversation

@BiswaViraj
Copy link
Contributor

What changed? Why was the change needed?

Screenshots

Expand for optional sections

Related enterprise PR

Special notes for your reviewer

@linear
Copy link

linear bot commented Apr 21, 2025

NV-5699 Analytics

@netlify
Copy link

netlify bot commented Apr 21, 2025

Deploy Preview for dashboard-v2-novu-staging ready!

Name Link
🔨 Latest commit e48577a
🔍 Latest deploy log https://app.netlify.com/sites/dashboard-v2-novu-staging/deploys/68076034dfbeb500087155b0
😎 Deploy Preview https://deploy-preview-8169.dashboard-v2.novu-staging.co
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR adds telemetry tracking for digest variable selections in the dashboard's autocomplete features. Key changes include:

  • Adding a new telemetry event (DIGEST_VARIABLE_SELECTED) in telemetry utilities.
  • Modifying autocomplete source functions in liquid-autocomplete.ts and control-input.tsx to include telemetry tracking via a track callback.
  • Integrating telemetry tracking into the MailyVariablesListView component in the email workflow editor.

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

File Description
apps/dashboard/src/utils/telemetry.ts Added new telemetry event for digest variable selection
apps/dashboard/src/utils/liquid-autocomplete.ts Updated autocomplete source to track digest variable selections and include a new telemetry callback
apps/dashboard/src/components/workflow-editor/steps/email/views/maily-variables-list-view.tsx Integrated telemetry tracking for digest variable selection upon item selection
apps/dashboard/src/components/primitives/control-input/control-input.tsx Passed telemetry track callback to autocomplete source function
Comments suppressed due to low confidence (1)

apps/dashboard/src/components/workflow-editor/steps/email/views/maily-variables-list-view.tsx:78

  • [nitpick] Consider using a consistent payload key (e.g., 'variable' instead of 'type') for the DIGEST_VARIABLE_SELECTED event to maintain consistency across telemetry calls.
track(TelemetryEvent.DIGEST_VARIABLE_SELECTED, { type: item.name, });

Comment on lines +78 to +80
track(TelemetryEvent.DIGEST_VARIABLE_SELECTED, {
type: item.name,
});
Copy link
Contributor

Choose a reason for hiding this comment

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

Is it possible to have a generic "Variable Selected" event and pass the name as a pram?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, do we want to track all the variables including payload, subscriber etc
or just the digest ones for now?

@BiswaViraj BiswaViraj merged commit 86eb10d into next Apr 22, 2025
27 checks passed
@BiswaViraj BiswaViraj deleted the nv-5699-analytics branch April 22, 2025 14:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants