GA: recordEvent when `va-alert` loads on MHV landing page

wesrowe commented 11 months ago

Description

User story

As a Cartographers team member, I want to be able to segment GA data for users who see either the non-LOA3 or unregistered alerts, so that I can understand the frequency of this user type and see if their behavior differs significantly from other Veterans.

Notes

"Key" user types include, at a minimum:
- Those who are not registered at a facility (and would see corresponding alert)
- Those whose credentials are not LOA3, and which credential they used (and would see corresponding alert)
Component loaded event was added ~to~ for use by the va-alert component ~via~ by Analytics Team. Implementation ticket. Jamie Stutt "the custom event dataLayer" (her words) in a comment on that ticket
- It's possible that instead of this va-alert event, we could segment users based on demographic data on the GA user (Carlos did some discovery around this topic in the past), but that is probably not necessary

Example segmented GA report

Screenshot

Possible tasks

Acceptance criteria

Built a GA report that shows unique link clicks segmented by non-LOA3 and unregistered user types
~GA events for link clicks include destination domain (VAgov vs eauth/myhealth.va.gov)~
~(stretch) Discovered how GA work might need to be adapted in GA4~
~Demonstrated that "key" landing page user types are can be used to segment/filter user sessions in Datadog~

wesrowe commented 5 months ago

planning: if a piece of work for GA segmenetation is identified as big-effort and wasted/duplicated between GA360 and GA4, we can consider ticketing as future work to be done when the need is clearly imminent.

wesrowe commented 5 months ago

I overhauled the ticket, reducing ACs to just implementing the component-load event on va-alert – expect the points should come down.

wesrowe commented 5 months ago

@radavis, we have partial success in Staging. Here's what I see for User 3, who is not registered:

The bottom one is the "good" one that will correspond to Prod GA. The event action (ea) is just Navigation - Unknown.

I'm not exactly sure how it was supposed to appear. But per Jamie Stutt's comment I thought it would include the alert headline and status:

'event': 'nav-alert-box-load' 'action': 'load' 'alert-box-headline': //populate with the heading_1 'alert-box-status': //populate with the alert status, seems more like alert type - normally info, warning, continue

radavis commented 5 months ago

@wesrowe ~Nice.~ I'm currently looking for a loa1 account, but none are listed in the Test User Dashboard.

wesrowe commented 5 months ago

People often use their personal ID.me acct, if you have one that's not ID-proofed.

radavis commented 5 months ago

Waiting on OCTO-identity review.

radavis commented 4 months ago

@wesrowe According to the frontend support dashboard, changes in department-of-veterans-affairs/vets-website#29421 are now in dev, staging, and prod. Let me know when you have the chance to verify in GA.

wesrowe commented 4 months ago

@radavis, have you tried it in Staging? I'm still seeing the same Navigation - Unknown in adswerve. user 3

radavis commented 4 months ago

@wesrowe Ok, we will need to sync w/ the Analytics Team to get this sorted.

radavis commented 4 months ago

@wesrowe Could you provide a link to the analytics.google.com page you are viewing?

radavis commented 4 months ago

On May 3rd, 2024, the Analytics Team was able to change the GTM settings so that AdSwerve outputs Navigation - {heading content} for <va-alert /> components loading on our landing page.

There's still the problem of enabling this functionality for all <va-alert /> components. [discussion]

wesrowe commented 4 months ago

this looks perfecto on our "unregistered alert"!

and the non-LOA3 alert too!

wesrowe commented 4 months ago

@radavis, I believe I covered both use cases above. If you're satisfied, this can close.

department-of-veterans-affairs / va.gov-team