SKasimow commented 3 years ago

Google Analytics Implementation or QA Request

What this form is for

More Information

Use this template to request Google Tag Manager and Google Analytics implementation or QA for your product. Please fill out all brackets.

> _Please see the following information for implementation timeline:_ > New Teams: Implementation will usually be completed in 4 sprints: > > - Sprint 1: Discovery/Orientation > - Sprint 2: FE Implementation > - Sprint 3: Tagging Implementation > - Sprint 4: QA > > All other teams: Implementation will usually be completed in 2 sprints > > - Sprint 1: Discovery and FE Implementation > - Sprint 2: Tagging Implementation and QA For more information, please check out the [Google Tag Manager resources](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/analytics/google-analytics/readme.md). An example of a completed request template can be found [here](https://github.com/department-of-veterans-affairs/va.gov-team/issues/7199). A fully completed issue can help speed up the implementation process.

Description

Is this request for Google Analytics implementation or QA?

The initial request is for GA implementation but will need QA as well.

Who is this request for?

@SKasimow @DanielleThierryUSDSVA

Provide any relevant contact information and link this issue to the insights team on the DSVA Slack Channel: #VFS-Platform-Support.

What team/project is this work for?

Content & Localization team

This is for 3 new Language Assistance and Resource pages (Spanish, Tagalog, Other Languages) AND
Addition of link in the footer to the new pages

Provide the Domain where Google Analytics needs to be implemented

staging.va.gov

https://staging.va.gov/asistencia-y-recursos-en-espanol/ https://staging.va.gov/tagalog-wika-mapagkukunan-at-tulong/https://va.gov/asistencia-y-recursos-en-espanol/

va.gov

https://www.va.gov/resources/how-to-get-free-language-assistance-from-va/

Identify if PII is passed in URL or title tag

N/A

Please provide any upcoming deadlines or important milestones

Launch is targeted for June 7 2021

Typical Website Interactions to Track

Conversions Understanding the User Flow

Provide URLs that are part of the application from introduction page to successful form completion; conditional pages that are visible depending on an applicant's answer should be marker accordingly.

Final URLs are TBD but will likely be one of the options below (Spanish example below)

www.va.gov/spanish-language-assistance-support-and-resources/
- www.va.gov/espanol-language-assistance-support-and-resources/
- www.va.gov/apoyo-y-recursos-en-espanol/ (would need translation validation)

Other User Interactions: Provide details on other interactions and metrics, like click to help text links, that are helpful in understanding user behavior.

Link tracking
Pageviews
Scroll depth
Click to call
Entry and exit pages
UVs
Satisfaction scores

Sample Users when authentication is required _do not put staging credentials in your va.gov-team ticket; store or reference them in a .md file in the va.gov-team-sensitive repository**_

- No authentication required

Test Users to replicate the event _do not put staging credentials in your va.gov-team ticket; store or reference them in a .md file in the va.gov-team-sensitive repository**_

N/A

Certain conditions/responses that need to be reviewed

-Can Analytics team provide the event names we should use for the footer, such as:

FOOTER_COLUMNS.PROGRAMS: 'nav-footer-programs FOOTER_COLUMNS.RESOURCES: 'nav-footer-resources

Additional Comments

Please leave the following blank

Acceptance Criteria

[ ] QA has been completed
[ ] Events have been added to Product and Benefit Hub Content Groups
[ ] VFS team completes brief VSP Collaboration Cycle Feedback survey

Definition of Done

[ ] All appropriate issue tagging is completed
[ ] All AC completed
[ ] VSP: Platform Collaboration Point Tracker is updated

SKasimow commented 3 years ago

FYI - @youngfreezyVA . How soon do you need the event name for footer links? We should havef the URLs finalized by early next week.

jonwehausen commented 3 years ago

@laurensimpson14 & @bsmartin-ep Please triage, assign & review.

For footer events please see our ^nav-footer.*` should do the trick.

May also need to add scroll depth tracking within GTM.

SKasimow commented 3 years ago

@laurensimpson14 @bsmartin-ep Hello - just checking in to see if you have guidance for this? Thanks!

SKasimow commented 3 years ago

@joanneesteban Hi - can we get some one to look at these? Launching June 1st :)

joanneesteban commented 3 years ago

Hi @SKasimow - thanks for the ping! We'll get someone to look at these for your launch :)

joanneesteban commented 3 years ago

@laurensimpson14 will be working on this implementation.

laurensimpson14 commented 3 years ago

Hi @SKasimow do you have the URLs finalized for the three new language pages? When I click on any of the URLs listed in the ticket I get a missing page notice.

SKasimow commented 3 years ago

@laurensimpson14 Hi - we are going to use translated URLs and are waiting on translation service. Hope to have today/tomo. Once I have them I will add to the ticket.

@youngfreezyVA: Jon commented above that for footer events:

"... please see our ^nav-footer.*` should do the trick.

May also need to add scroll depth tracking within GTM."

Does that suffice for now?

youngfreezyVA commented 3 years ago

yes that works, i'll use the following event: nav-footer-language-support and I can pass the selected lang, similar to the analytics for the language switcher component

SKasimow commented 3 years ago

@laurensimpson14 Here are the 3 URLs for the new pages. Hoping to have 1+ 2 in staging by tomorrow:

va.gov/asistencia-y-recursos-en-espanol
va.gov/tagalog-wika-mapagkukunan-at-tulong
https://www.va.gov/resources/how-to-get-free-language-assistance-from-va/

SKasimow commented 3 years ago

Hi @laurensimpson14 do you need to just review the staging instances prior to our staging review (which is June 7) to see if there are any non-standard elements we need to tag? And then test to make sure everything fires off ok?

Just want to clarify what we need by next Thursday for Staging!

Thanks,

Sharon

cc @joanneesteban

laurensimpson14 commented 3 years ago

Hi @SKasimow, Please see my notes for each tracking item below:

- Link Tracking:

I want to confirm with you what you'd like tracked to be sure we're on the same page and capturing everything that you need. What is currently tracking:

All PDF downloads are automatically tracked:
All outbound link clicks (such as the one pictured below that goes to http://www.publichealth.va.gov) are automatically tracked:
The footer links are now tracking:
There are four links that go to other internal pages:
1. https://staging.va.gov/coronavirus-veteran-frequently-asked-questions-tag/
2. https://staging.va.gov/health-care/covid-19-vaccine-tag/
3. https://staging.va.gov/health/rights/patientrights.asp
4. https://staging.va.gov/health/rights/familyrights.asp
  
  Because these URLs are not repeated anywhere on the page, we recommend viewing the analytics for these by sorting by previous page path, rather than creating a new event.
The "Find helpful VA phone numbers" CTA on the "How to get free language assistance from VA" page is tracking:

These navigation list links are being tracked:

What is not currently tracking:

Accordion clicks are coming in as not set. @youngfreezyVA can you please pass nav-accordion-embedded-link-click? (GA report w/those events for reference here)
Would you like the three jump links here tracked on the Tagalog and Spanish pages?:
I noticed that the link to the facility locator is in two places on the page:

Will you need to be able to distinguish between the two locations on the page - or is just knowing how many users go from the Tagalog/Spanish page to the facility locator (regardless of which button) sufficient?

- Pageviews:

These are automatically tracked.

- Scroll depth:

This is currently tracking on the "How to get free language assistance from VA" page. However, scroll depth is not currently tracking on va.gov/asistencia-y-recursos-en-espanol or va.gov/tagalog-wika-mapagkukunan-at-tulong/. I've added tracking for it into GTM. After this gets QA'd by another member of the analytics team I can publish it.

- Click to call:

This is automatically being tracked:

- Entry and exit pages:

These are automatically tracked.

- UVs:

Do you mean unique visitors? If so, these are automatically tracked.

- Satisfaction Score:

Are you referring to the "good" and "bad" radio buttons under "How do you rate your experience on this page?"? If so, this is being tracked:

- Other

The search bar at the top of the "How to get free language assistance from VA" page is not returning any results, so the only tracking I'm able to verify for this is the No Search Results Returned event:

SKasimow commented 3 years ago

Hi Lauren,

Thanks for your detailed view and screenshots! I just had a few comments/questions on the info you provided above:

Item 1

There are four links that go to other internal pages:

https://staging.va.gov/coronavirus-veteran-frequently-asked-questions-tag/

https://staging.va.gov/health-care/covid-19-vaccine-tag/

https://staging.va.gov/health/rights/patientrights.asp

https://staging.va.gov/health/rights/familyrights.asp

Because these URLs are not repeated anywhere on the page, we recommend viewing the analytics for these by sorting by previous page path, rather than creating a new event.

SK: do you know why the other links you reviewed are all tracking and these 4 aren't? Is it bc the others go to teammate (external) pages whereas these go to internal? What is not currently tracking:

Item 2

Accordion clicks are coming in as not set. @youngfreezyVA can you please pass nav-accordion-embedded-link-click? (GA report w/those events for reference here) image

SK: need @youngfreezyVA to fix this

Item 3

Would you like the three jump links here tracked on the Tagalog and Spanish pages?: image

SK: yes we should track these; is that something @youngfreezyVA needs to add?

Item 4

I noticed that the link to the facility locator is in two places on the page: image

SK: I think this is just placeholder text but will ask @DanielleThierryUSDSVA to review

To be continued in next comment....

SKasimow commented 3 years ago

Item 5

Other

The search bar at the top of the "How to get free language assistance from VA" page is not returning any results, so the only tracking I'm able to verify for this is the No Search Results Returned event:

SK: think this is just an artifact of staging set-up. @youngfreezyVA can you confirm??

Thanks All!

laurensimpson14 commented 3 years ago

SK: do you know why the other links you reviewed are all tracking and these 4 aren't? Is it bc the others go to teammate (external) pages whereas these go to internal?

LS: Yes, we automatically track links to external pages since it is difficult to see GA data across multiple domains and multiple GA properties. For example, with external pages, we can't go the pageviews report, filter by that page, and then add a secondary dimension of previous page path since it can't look back across domains to see the previous page. Instead, it will register the external page as the landing page/first page visited in a different GA property.

With internal pages (like the 4 in the list) we don't typically add event tracking for those since you can find the information you're looking for in the pageviews report. This is also an effort to reduce the number of hits we send to GA since there is a limit for hits collected.

LS: Would you like the three jump links here tracked on the Tagalog and Spanish pages?: image SK: yes we should track these; is that something @youngfreezyVA needs to add?

LS: Yes - data layer specification for jump links: 'event': 'nav-jumplink-click', add link name attribute (or similar)

SKasimow commented 3 years ago

@youngfreezyVA Hi Fareez - think this is the only addition we need to make for GA tracking:

For "On this page" add tracking for the three jump links on the Tagalog and Spanish pages.

The data layer specification for jump links: 'event': 'nav-jumplink-click', add link name attribute (or similar)

youngfreezyVA commented 3 years ago

awesome! thanks so much @SKasimow for grooming this analytics ticket 🎉 🎖️ I will include these changes in the PR that updates Language Support -> Language Assistance

youngfreezyVA commented 3 years ago

after doing some digging, it looks like the above use case is already covered: https://github.com/department-of-veterans-affairs/content-build/blob/master/src/site/stages/build/plugins/modify-dom/add-id-to-subheadings.js#L93

laurensimpson14 commented 3 years ago

@youngfreezyVA I don't see any events firing for the table of contents. I'm also not seeing it in GitHub: https://github.com/department-of-veterans-affairs/va.gov-team/search?q=nav-table-of-contents

Can I ask where that came from?

youngfreezyVA commented 3 years ago

hello @laurensimpson14 ... the link above is where the table of contents is referenced, please take a look at this file or review internally with the analytics team and they can help clarify: https://github.com/department-of-veterans-affairs/content-build/blob/master/src/site/stages/build/plugins/modify-dom/add-id-to-subheadings.js#L84

will appreciate if you can review that code / link above internally before i proceed in making any changes as they may already exist.

laurensimpson14 commented 3 years ago

@youngfreezyVA Based on the code you linked, we should be seeing nav-jumplink-click events on table of contents link click? However, I'm not seeing them on the staging link.

youngfreezyVA commented 3 years ago

i am seeing errors related to GA when I click on those links, in the console in staging.

it looks like there is an issue with the inline recordEvent from the above code fixing this would require a separate ticket as I did not make the original changes I am guessing this may be an issue specific to the staging environment, but at this moment I'm not 100%

youngfreezyVA commented 3 years ago

@bsmartin-ep has previously reported errors from this inline event, he may be able to provide more insight.

laurensimpson14 commented 3 years ago

I spoke with @bsmartin-ep and he's going to create a ticket for that error.

In the meantime we can QA this one item when it goes to production @SKasimow.

SKasimow commented 3 years ago

@laurensimpson14 sounds good, thanks Lauren!

joanneesteban commented 3 years ago

@SKasimow let us know when this is pushed to Production, and we can double check that this is good to go! (CC: @bsmartin-ep )

SKasimow commented 3 years ago

@joanneesteban Hi - this is now first full day live (June 11th)!

bsmartin-ep commented 3 years ago

As expected, table of content links at the top of the page are working correctly in production.

joanneesteban commented 3 years ago

@SKasimow congrats on the launch! Can we close this ticket?

SKasimow commented 3 years ago

@joanneesteban Hi - thanks! I did check and am seeing data for page views (the only thing I checked so far) but do you guys check the other key metrics once it is moved to production? I know Brian confirmed the "On this page" component for us as noted above.

If everything is verified on you end then yes, feel free to close the ticket. Thanks, Sharon

laurensimpson14 commented 3 years ago

Hi @SKasimow, I've gone through and completed QA for each component in production below! Please see my notes and let me know if there is anything missing (note: entry & exit pages as well as unique visitors vs returning visitors are automatically tracked with pageviews) 🙂

Interaction	Screenshot	Status
PDF Downloads -		🟢 Tracking Correctly
Outbound Link Clicks		🟢 Tracking Correctly
Footer Language Assistance Links		🟢 Tracking Correctly
`Find helpful VA phone numbers` CTA		🟢 Tracking Correctly
Navigation List Links		🟢 Tracking Correctly
Accordion clicks		🟡 Accordion clicks are coming in as not set. @youngfreezyVA can you please pass nav-accordion-embedded-link-click? (GA report w/those events for reference here)
Jump Links		🟢 Tracking Correctly
Pageviews		🟢 Tracking Correctly
Scroll Depth		🟢 Tracking Correctly
Click to Call		🟢 Tracking Correctly
Satisfaction Score (Good/Bad Buttons)		🟡 the `not set` portion of the interaction label should be `good` or `bad` depending on the selection, not `not-set` @youngfreezyVA do you know why this is happening? (link to page here)
Search Bar		🟢 Tracking Correctly