Clean up GA events on New Homepage

[wesrowe]

Description

User story

AS A(N) product manager I WANT each event on the new homepage to only have one relevant GA event fire SO THAT both the AdSwerve console and GA Dashboard are less cluttered

Engineering notes / background

The redundant events were added as a short-term solution in #12065 at a time when we were planning to launch the new homepage but were still waiting on Platform Analytics to wire our custom events in GTM.

This Mural contains the various events involved. The ones in black text with "AC" are the ones that need to be removed.

Analytics considerations

Nothing additional

Quality / testing notes

Validate in AdSwerve (either staging or production).

Acceptance criteria

Consider

• Design / Accessibility reviews
• Collab cycle requirements
• Device sizes (mobile first)
• Documentation updates / Change management
• Testing notes

• [ ] The following events detailed in "AC" text of Mural above are no longer firing or visible in AdSwerve console in Chrome
  • [ ] "Create Account" button – a Primary Button Click event, e.g. the "Feedback" button on the existing HP: ec: Interactions ea: Default Button CTA - [button text] - [optional: button color]
  • [ ] Other search tools links – same GA as "zone one" links on existing HP (i.e., the 4 boxes): ec: Interactions ea: Navigation - Zone One - ->[optional: path of destination] - [required: link text] - [optional/not defined]
  • [ ] "Top pages" links – same GA as "zone one" links on existing HP (i.e., the 4 boxes): ec: Interactions ea: Navigation - Zone One - ->[optional: path of destination] - [required: link text] - [optional/not defined]
  • [ ] News promo ("Pathfinder...") links – tracked as "zone one"
  • [ ] Block title
  • [ ] "read full article"
  • [ ] "More VA news"
  • [ ] "Sign up" button for newsletter – "primary button click" similar to Feedback button: ec: Interactions ea: Default Button CTA - [button text] - [optional: button color]

Team

Please check the team(s) that will do this work.

• [ ] CMS Team
• [X] Public Websites
• [ ] Facilities
• [ ] User support

[wesrowe]

Possible reasons to delay this ticket:

• GA4 implementation might require us to handle this anyway (so do it then)
• it's just clutter, not breaking anything

[jilladams]

@FranECross was digging through backlog and came across this older ticket. I don't totally understand the issue, but figured I'd flag in case it's relevant for the GA4 related work and needs to be looked at re: custom events vs. components, etc etc.

[wesrowe]

Hello! I see I didn't link the Mural in the ticket body. Here it is, although it's Greek to me now. The gist: because we couldn't get custom events implemented by the Platform Analytics Team in the timeframe of launch, we initially added GA events that were not as well named. Then we added the preferred ones when available without removing the "temporary" ones.

I have no idea how the GA4 migration would have affected things.

[FranECross]

@wesrowe @jilladams I'll take a look to see if the events detailed have been removed, and if not, will queue the ticket up for action. Thanks!