search

lansingcodes / www

Events and resources for Lansing coders
https://www.lansing.codes
Other
7 stars 16 forks source link

Use Google Analytics autotrack #55

Open egillespie opened 5 years ago

egillespie commented 5 years ago

Google developers have created a group of trackers for Google Analytics bundled as autotrack. These trackers make it a lot easier to track clicks on a page, scrolling behavior, form submission, and more.

Right now our Google Analytics usage simple reports information available on page load such as session duration, device information, and repeat visitor quantity. Using autotrack would be really helpful for future enhancements because it would give us a lot more insight into how visitors use the page.

At a glance, I think the following trackers would be most helpful:

pfhawkins commented 5 years ago

This issue depends on #73 being done first.

WalterEschenbach commented 2 years ago

Hi @egillespie ,

egillespie commented 2 years ago

Hi @egillespie ,

  • Are there credentials for the google analytics account associated with the tracking ID that can be found in nuxt.config.js? 🤔

Yep! It's at the very bottom of nuxt.config.js. The ID is UA-73509402-2.

WalterEschenbach commented 2 years ago

@egillespie - Nice Nice- so we have the Tracking ID in our code, which will tell analytics which account and property to send the data to - would we also need the account/admin info to test/verify that autotrack has been implemented correctly?

Or... does it make sense to make a new burner account, create a new Tracking ID for the purposes of testing that our autotrack plugins are firing correctly and then just switch in the relevant Tracking ID once everything is up and running?

Or... third alternative, I'm over thinking this (haha) and there is another way that allows us to see that when we implement an impressionTracker/urlChangeTracker... that it is being recorded in our analytics dashboard?

egillespie commented 2 years ago

@WalterEschenbach, thoughtful questions! Let's stick with the existing Tracker ID and associated Google account. I'll see if I can add additional members to the analytics account so you can verify the code changes are working as expected.

If you have a Google account, can you DM me your email in Slack?

WalterEschenbach commented 2 years ago

Confirmed, I do have a google account - just sent the email associated via slack.

egillespie commented 2 years ago

Confirmed, I do have a google account - just sent the email associated via slack.

I added you to the analytics account. Let me know if you have trouble looking at the info!

WalterEschenbach commented 2 years ago

See it in my inbox - Thank you!

WalterEschenbach commented 2 years ago

Hi @egillespie, I was able to accomplish some of the initial setup/config and can now see autotrack events firing in our Google Analytics dashboard 🎉.

What's left of this initial draft for implementing autotrack is aligning the reporting in the Analytics platform with the trackers we set up in our code. To view the results for several of these trackers (i.e., maxScrollTracker, pageVisibilityTracker), it is required for us to create custom metrics in our reporting.

Custom dimensions and custom metrics are like default dimensions and metrics in your Analytics account, except you create them yourself. You can use them to collect and analyze data that Analytics doesn't automatically track.

Custom dimensions and metrics are set at the property level in an Analytics account. You must have the Editor role on the property to create or edit custom dimensions & metrics.

Creating either a custom dimension or metric is a two step process. First, set up the custom dimension or metric in your property. Then, modify your tracking code. You must complete these steps in order.

Can you please update my role from "Analyst" to "Editor" on the property for lansing.codes in the Google Analytics platform?

egillespie commented 2 years ago

You're an editor now, Walter! 🤘

On Wed, Oct 20, 2021 at 4:27 PM Walter @.***> wrote:

Hi @egillespie https://github.com/egillespie, I was able to accomplish some of the initial setup/config and can now see autotrack events firing in our Google Analytics dashboard 🎉.

What's left of this initial draft for implementing autotrack is aligning the reporting in the Analytics platform with the trackers we set up in our code. To view the results for several of these trackers (i.e., maxScrollTracker, pageVisibilityTracker), it is required for us to create custom metrics https://support.google.com/analytics/answer/2709829#zippy=%2Cin-this-article in our reporting.

Custom dimensions and custom metrics are like default dimensions and metrics in your Analytics account, except you create them yourself. You can use them to collect and analyze data that Analytics doesn't automatically track.

Custom dimensions and metrics are set at the property level in an Analytics account. You must have the Editor role on the property to create or edit custom dimensions & metrics.

Creating either a custom dimension or metric is a two step process. First, set up the custom dimension or metric in your property. Then, modify your tracking code. You must complete these steps in order.

Can you please update my role from "Analyst" to "Editor" on the property for lansing.codes in the Google Analytics platform?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/lansingcodes/www/issues/55#issuecomment-948010988, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABKQNH2VJLYI752MKYRGDJTUH4Q2PANCNFSM4F6GPUSA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.