[BLOCKED] [Analytics] [Landing pages] Custom GA events removal & web component upgrades

[randimays]

Status

[2024-08-19] [Fran] Info from Randi: This ticket should be taken with similar caution as #18502. In #18502 (comment), @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:

• https://www.va.gov/service-member-benefits/ (All "Call us" links in the sidebar)

Engineering notes

Code where these links exist:

• https://github.com/department-of-veterans-affairs/content-build/blob/7c123600579e02589bbfc0b17408492e6adc363c/src/site/layouts/landing_page.drupal.liquid#L88
• https://github.com/department-of-veterans-affairs/content-build/blob/7c123600579e02589bbfc0b17408492e6adc363c/src/site/layouts/landing_page.drupal.liquid#L95
• https://github.com/department-of-veterans-affairs/content-build/blob/7c123600579e02589bbfc0b17408492e6adc363c/src/site/layouts/landing_page.drupal.liquid#L103

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

• Elements: all phone numbers in the "Call us" section (sidebar)
  • convert to va-telephone component
  • remove custom events
• a11y review

[randimays]

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.