You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to improve feature usage tracking in Pendo, it is necessary to be able to identify user interactions more granularly. A critical point of interaction is the confirmation action performed by users. However, the current implementation of the NewConfirmationDialog component lacks the capability to modify the ID of the confirmation button. Tracking in Pendo works best when we can assign a tracked feature to an Element in the VIP Dashboard by it's ID.
Proposed Solution:
The ability to set a custom ID for the confirmation button within the NewConfirmationDialog component upon its creation. This will allow for precise tracking of the confirmation events in Pendo.
The text was updated successfully, but these errors were encountered:
This issue has been marked stale because it has been open for 60 days with no activity. If there is no activity within 7 days, it will be closed.
This is an automation to keep issues manageable and actionable and is not a comment on the quality of this issue nor on the work done so far. Closed issues are still valuable to the project and are available to be searched.
In order to improve feature usage tracking in Pendo, it is necessary to be able to identify user interactions more granularly. A critical point of interaction is the confirmation action performed by users. However, the current implementation of the NewConfirmationDialog component lacks the capability to modify the ID of the confirmation button. Tracking in Pendo works best when we can assign a tracked feature to an Element in the VIP Dashboard by it's ID.
Proposed Solution:
The ability to set a custom ID for the confirmation button within the NewConfirmationDialog component upon its creation. This will allow for precise tracking of the confirmation events in Pendo.
The text was updated successfully, but these errors were encountered: