randimays
commented
1 month ago This ticket should be taken with similar caution as #18502. In a comment there, @laflannery explained that we have some outstanding issues in order to be able to reliably convert telephone numbers to the web component.
Before we can pick up and work this ticket, we need to carefully consider exactly how each of the links are constructed and our technical approach to converting them to web components, if possible.
Status
[2024-08-19] [Fran] Info from Randi: This ticket should be taken with similar caution as https://github.com/department-of-veterans-affairs/va.gov-cms/issues/18502. In https://github.com/department-of-veterans-affairs/va.gov-cms/issues/18502#issuecomment-2226262877, @laflannery explained that we have some outstanding issues in order to be able to reliably convert telephone numbers to the web component.
Before we can pick up and work this ticket, we need to carefully consider exactly how each of the links are constructed and our technical approach to converting them to web components, if possible. [2024-08-14] [Fran] Not urgent; no dupe events. [2024-07-15] [Fran] Noting that this needs to be refined by the team in our next prefinement.
Description
The va-link web component's analytics now include link destination, and va-link-action has been released to the component library. We can now use baked-in analytics on the Resources & Support detail pages where the default contact is used.
Example pages:
Engineering notes
Code where these links exist:
User story
AS A PO/PM managing Public Websites products & features I WANT to (where appropriate) adopt the va-link or va-link-action component, its baked-in analytics, and remove the custom GA events SO THAT extraneous code is removed and only the events needed will be triggered.
Acceptance criteria