Closed LindaLi123 closed 2 years ago
@joanneesteban Hello Joan, would you please confirm if i provided all the necessary information to start analytics implementation? We want to track all clicks and user journey
@LindaLi123
Would you be able to look at this documentation and let us know if there are additional interactions that you'd like to track that we won't be tracking already with our standardized tags? Please ping us for any and all questions!
CC: @laurensimpson14
@joanneesteban Hello Joanne, standardized template is fine. Thank you so much!
@LindaLi123 I was unable to find the following two links on staging, so I was unable to provide QA for them:
https://www.staging.va.gov/health-care/pay-copay-bill/your-current-balances/
https://www.staging.va.gov/health-care/pay-copay-bill/your-current-balances/balance-details/
QA for https://www.va.gov/health-care/pay-copay-bill/ : |
Interaction | Interaction Screenshot | QA Screenshot | Status |
---|---|---|---|---|
Pageview | π’ Tracking | |||
Hyperlinks to other internal web pages | N/A | π’ Tracking - As long as this hyperlinked text is the only way to navigate to https://staging.va.gov/coronavirus-veteran-frequently-asked-questions/#benefit-and-copayment-debts from this page, then it is automatically tracked using the Google Analytics previous page metric. If there is more than one way to get to an internally linked page from this page (i.e. the multiple links on this page to https://va.gov/find-locations/ ) then it will still be tracked, however you will be unable to distinguish which hyperlinked text they clicked to navigate to that page. |
||
Outbound link click | π’ Tracking - All outbound link clicks are automatically tracked. | |||
Phone outbound link clicks | π’ Tracking - All phone link clicks are automatically tracked. | |||
Download PDF | π’ Tracking - All PDF clicks are automatically tracked. | |||
Accordion clicks | π’ Tracking - All accordion clicks are automatically tracked. | |||
Navigation link list clicks | π’ Tracking - All navigation link list clicks are automatically tracked. |
Please let me know if you have any questions about the above interactions or if there are additional interactions that you'd like to request tracking for. Also, please let me know about the two additional links that I was unable to reach!
@laurensimpson14 Hello Lauren, these two links will be working soon we are working on them. Will keep you posted once they are. Thank you so much. https://www.staging.va.gov/health-care/pay-copay-bill/your-current-balances/ https://www.staging.va.gov/health-care/pay-copay-bill/your-current-balances/balance-details/
@laurensimpson14 Hello Lauren, these two links are working now please go ahead and provide QA and analytics for them. Thank you so much
@LindaLi123 I was unable to find the following link on staging:
https://www.staging.va.gov/health-care/pay-copay-bill/your-current-balances/balance-details/
QA for https://www.staging.va.gov/health-care/pay-copay-bill/your-current-balances/ : |
Interaction | Interaction Screenshot | QA Screenshot | Status |
---|---|---|---|---|
Alert drop down | π‘ Not Tracking - are clicks to expand this alert something that you need tracked? | |||
Phone outbound link clicks | π’ Tracking Correctly |
In the What you owe to each facility
section this is what I see:
None of the BALANCE CARD
grey boxes are clickable. Is that correct?
@laurensimpson14 Hello Lauren, sorry for the confusion, looks like staging isnt 100% ready yet. Would you be able to create analytics tags via links to the mocks instead of staging? Here is the link https://preview.uxpin.com/16e8675a9898914d5615d6ea2d23e310b7d8dfaa#/pages/140669280/simulate/sitemap?mode=i
@LindaLi123 Unfortunately, I'm unable to create tracking tags or QA based on a mock. Do you know when that mock will go to staging?
@laurensimpson14 @joanneesteban Hi Lauren, Did this change with the introduction of the standardized template? I believe you just provide the tags and the FE devs add them for tracking still? or do you now go into the code and add them yourself? Thanks! Leah cc: @craigwheeler
@leahkeeler 90% of our tracking is automatic, so no additional tags are needed for pageviews, unique users, time on page, menu clicks, phone call clicks, download clicks, accordion expands, etc. If any custom tagging is needed, then our team will write the dev specs and the devs add them in. We don't go into the code and add them ourselves.
Looking at your mockup, I don't believe custom tagging will be required, however I'd still like to double check once this goes into staging. Once it's in staging I'll be able to see what web component this subtitle is using (which could determine if it needs additional tracking or not).
@leahkeeler - let us know when this is in Staging, and we can start supporting the tagging process!
@joanneesteban Hello Joanne, staging is not ready yet as of today, will let you know soon!
@joanneesteban @laurensimpson14 I am picking up this work from Linda and wanted to follow up on this. I believe these pages (below) are now in staging and you should be able to do the double check that you mentioned. I am getting clarity on exactly what we wanted to ensure was being tracked but as part of your check if you can review what is and isn't currently tracked that would be incredibly helpful.
https://www.va.gov/health-care/pay-copay-bill/ https://www.va.gov/health-care/pay-copay-bill/your-current-balances/ https://www.va.gov/health-care/pay-copay-bill/your-current-balances/balance-details/
cc: @leahkeeler
@denisecoveyduc Is there a specific test user that I should use to view these two pages? https://www.va.gov/health-care/pay-copay-bill/your-current-balances/ https://www.va.gov/health-care/pay-copay-bill/your-current-balances/balance-details/
When I log in with Judy or Cecil on staging I see this error:
Hi @laurensimpson14 Thanks for taking another look. At the moment the team is working on a work around to fix an issue with the test cases. I will let you know once it has been resolved.
We also discussed the tables you provided above to understand what is being tagged and what isn't. I have a list of 5 custom tags that we would like to add.
@craigwheeler Please feel free to add to this if I missed anything you can think of.
@denisecoveyduc I'll move this ticket to stand by until the test users are resolved π
Page Views - distinction between landing page and logged in page
This is automatically tracked - you will be able to see this information β
Bounce Rate - How many users bounce
This is automatically tracked - you will be able to see this information β
Type of Alert Shown: Which will be one of these (Error, Veteran is deceased, No history of medical copays, Not enrolled in VA health care)
Will want to confirm that this is tracking once we have the test users working π¨
Number of PDF downloads
This is automatically tracked - you will be able to see this information β
Referral Page - where users are coming from (organic va.gov search, google search, {+eventually we will also have an email that is sent out but that isn't ready yet))
This is automatically tracked as source
- you will be able to see this information β
Hi @laurensimpson14 Following up on this. Currently we have TestUser#84 up and running which should work for the pages above. We are still sorting out two use cases but I think you should have what you need now to get started. Could you confirm? Thank you
@denisecoveyduc When I log in with test user 84 (Gregory) I see an error that We can't access your current copay balances right now
.
Is Gregory the correct test user for the staging site?
@denisecoveyduc When I login with test users 80 & 81 I'm able to see what they owe, however I don't see an alert on either test user (Error, Veteran is deceased, No history of medical copays, or Not enrolled in VA health care). Below is a screenshot of what I see on the page. Is there a test user with an alert showing? Or is there a away for me to trigger an alert?
@laurensimpson14 Doh! @LinnJS @craigwheeler I thought 81 had an alert?
@denisecoveyduc 81 had an alert until LETT fixed that user. Any user below 81 should work. Try 84.
@LinnJS I'm able to see an alert that says "We can't access your current copay balances right now"!
It looks like we deprecated auto-tracking on alert boxes. Here is what needs to be passed in the dataLayer to get tracking on that:
recordEvent({
event: 'visible-alert-box',
'alert-box-type': 'warning',
'alert-box-heading':
'We don't have any issues on file for you that are eligible for a Higher-Level Review' //dynamically populate according to the top level heading of the alert box,
'error-key': contestableIssues?.status || '',
});`
Hey @laurensimpson14 Try staging user #84 (Gregory George Lane) that should fail successfully on staging to produce the alert.
custom analytics added to alerts on this pr https://github.com/department-of-veterans-affairs/vets-website/pull/19673
Hi @denisecoveyduc and team π
Thank you Craig for adding the custom analytics to the alerts! Below is my QA - I logged in with test user #142.
Interaction | Interaction Screenshot | Event Screenshot | Status |
---|---|---|---|
Type of Alert Shown: Which will be one of these (Error, Veteran is deceased, No history of medical copays, Not enrolled in VA health care) | π’ Tracking |
Is You havenβt received a copay bill in the past 6 months
one of the alerts that you want tracked? If so, it's tracking correctly! Are there any other test users with different alerts that you'd like me to QA?
Hi everyone π I believe all tracking and QA has been completed here. Please feel free to re-open this ticket if you need anything additional or if you have a question.
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? Analytics Implementation
Who is this request for?
#VFS-Platform-Support
and tag@platform-analytics
.What team/project is this work for? this adds context for the data
Provide the Domain where Google Analytics needs to be implemented i.e. www.staging.va.gov
https://www.va.gov/health-care/pay-copay-bill/ https://www.va.gov/health-care/pay-copay-bill/your-current-balances/ https://www.va.gov/health-care/pay-copay-bill/your-current-balances/balance-details/
Please provide any upcoming deadlines or important milestones ex: launch
Please provide website interactions to Track
Design System components are automatically tracked. Read more here to see which Design System components are opt in or opt out. You do not need to specify on this ticket which components you are tracking unless you are opting in.
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.
[URLs here]
Other User Interactions: Provide details on other interactions and metrics, like click to help text links, that are helpful in understanding user behavior.
[Other user interactions here]
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 theva.gov-team-sensitive
repositoryTest 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 theva.gov-team-sensitive
repositoryCertain conditions/responses that need to be reviewed
Additional Comments
Acceptance Criteria
Product
andBenefit Hub
Content GroupsDefinition of Done