Closed Tom-Davis closed 1 week ago
Thanks @Tom-Davis -- our team will review this, and let you know what the best options will be here. We'll communicate further updates in this ticket.
FYI @jestutt, @ChristineYoungZA, @Blivaditis
Hi @Tom-Davis There are two parts to what you've asked for:
Before we start, this is a direction analysis and we won't always be dealing with real numbers.
When looking at external and internal traffic sources for a single or group of pages, you have to come at the information from a few angles in GA and manually combine them. I've created Debt Resolution Sources [A&I] Explore report to get you start.
Total number of page views generated across all pages with URLs that start with www.va.gov/manage-va-debt
Page view count for all www.va.gov sources
- based on
Page referrer
, where the user's browser says they were immediate before viewing pages with URLs that start with www.va.gov/manage-va-debt- excludes any referral traffic from the same section (sometimes called self referrals)
- excludes any referral traffic from auth login pages -- to finish the login process on a page, the users has to have started the process on the same page which means it's a self referral
Page view count for all non-www.va.gov sources
- also based on
Page referrer
, where the user's browser says they were immediate before viewing pages with URLs that start with www.va.gov/manage-va-debtSession default channel group
is a high-level grouping system for external sources based on a number of values, mostly includingPage referrer
and UTM tracking URLsSession source / medium
provide the more specific source information like which search was used or which site they came from
Event count for all tracked link clicks on www.va.gov to a /manage-va-debt destination link
- you can add other metrics to find placement information if needed
- excludes any events that happen on pages with URLs that start with www.va.gov/manage-va-debt
On Tab 3, you'll see that the Direct, or (direct) / (none), makes up more than 40% of the traffic sources. In these cases, direct = unknown and generally come from a non-HTML source like a bookmark, link typed into the browser, link click from an email or document, etc. To help reduce these unknowns in GA and provide better information on any external link placement we can control, we can add UTMs to our URLs to make them trackable.
Google provides a tool to assist in generating these trackable -- https://ga-dev-tools.google/campaign-url-builder/
You must complete the fields with an asterisk (*) when creating these URLs or risk incomplete information in GA.
There is one optional field I recommend using if you need to differentiate placements like the type of letter a qr code is in or the pictures used in a social post.
Tip: I strongly recommend keeping a record of any tracking links you create somewhere. It will come in handy when you're ready to start reporting on any traffic these links have generated.
cc @johnny-jesensky-adhoc
Google Analytics Implementation Request
Please provide the following details for this request
Team Name
Poduct Name
When is the launch date?
Provide the link(s) for Product/Page urls
What Events need to be tracked? NOTE: Design System Components are automatically tracked and should be used whenever possible to avoid custom configuration
[If this is a funnel, insert each step's URL - pages visible depending on the applicant's answers should be marked accordingly]
We are looking to track all incoming traffic to the portal be it internal or external sources including items such as a QR code that is printed on paper statements (QR code is here). I am not sure of the best format of the output report, we are looking for your help on how to have this data presented. I believe all the URL's are listed but didn't know if you just needed the root or every full destination.
If applicable, what test users are needed? NOTE: Do not put staging credentials in this ticket; store or reference them in a .md file in the
va.gov-team-sensitive
repositoryAny additional comments
Acceptance criteria
Product
andBenefit Hub
Content GroupsAdditional information
Please refer to Platform Collaboration Cycle or the Analytics Request Touchpoint on Platform website for more information about the Collaboration Cycle.