General Principles of Intellectual Property: Concepts of Intellectual Proper...
How to Defeat the Beast
1. How To
Defeat
The Beast
Safely migrate from Classic,
Universal, to Google Tag Manager.
#AIM 5 #heweb17
Sylvia E. Nicosia
Farmingdale State College
@synicosia
Follow Slides at: https://www.slideshare.net/SylviaNavarroNicosia/how-to-defeat-the-beast
Day Of The Dead "Horse and Rider" Instant Digital Download Printable Art jpeg Print Mexican Folk Artist J Ellison
https://www.etsy.com/transaction/1334132909
3. ALL ANALYTICS TOOLS
SERVE THEIR PURPOSEG
a.jsAnalytics.js
G
tm
.js
W
ebtrends
yoast
G
oogle
AnalyticsH
ubspot
hs-analytics.netG
oogle
classic
piw
ik
SiteIm
proveH
otjarG
oogle
U
niversal
G
oogle
AdW
ordsQ
uantcast
M
onsterInsightsTw
itter
G
oogle
Tag
m
anager
quintly
K
lout
O
pen
w
eb
analytics
Sim
ply
m
easured
fbq.push
W
P
Plugin
Acquia
Lift
bitly
clicky
sim
ila
4. ____
COMMON DENOMINATOR IN HIGHER ED
analytics.js gtm.js
Google
Analytics
+
Google
Analytics
Google
Analytics
+ga.js _______ ____
Classic
Analytics
Google Tag
Manager
Universal
Analytics
5. WHAT’S EVERYBODY IN HIGHEDWEB USING?
*As of August, 24, 2017
97%Google Analytics
6. GOOGLE ANALYTICS
STATISTICS
g of institutions and
companies
attending
HighEdWeb 2017
use Google Tag
Manager (gtms.js)
use Google
Universal Analytics
(analytics.js).
use Google
Classic Analytics
(ga.js).
40% 31% 11%
10. CLASSIC ANALYTICS
Uses old tracking code ga.js Javascript library
Google Analytics properties were transferred to Universal
Analytics, however it’s unclear what will happen to those
properties which are still utilizing the old tracking code
Misses features from Universal Analytics such as User ID
Google can make old tracking script stop working at any
time
Needs custom JavaScript tags to track events
<a href="http://farmingdale.edu/catalog.pdf"
onClick="_gaq.push(['_trackEvent', ' PDF Downloads', ‘Click',
’Catalog');">Catalog</a>
11. UNIVERSAL ANALYTICS
Uses tracking code analytics.js Javascript library
All new Properties use it
Enjoys cool features from Universal
Connect multiple devices, sessions, and
engagement data with the User ID.
Still needs custom JavaScript tags to track events
<a href="http://farmingdale.edu/catalog.pdf" onClick="ga(‘send’,
‘event’, ‘ PDF Downloads’, ‘Click’, ‘Catalog’);”>Catalog</a>
12. GOOGLE TAG MANAGER GTM
Uses tracking code gtm.js Javascript library
GTM does not replace your analytics, but helps you easily
add/manage JS tracking code (tags) to your website
Minimal amount of coding for more complex tags
Built-in debug feature, preview mode
Built-in variables and tags, plus you can make your own
Event tracking: No more custom JavaScript tags on your site
<a href="http://farmingdale.edu/catalog.pdf" class=“gtm-
catalog”>Catalog</a>
13. IS IT ONE BETTER THAN THE OTHER ONE?
Classic
Universal
GTM
Day Of The Dead "See No Evil, Hear No Evil, Speak No Evil" 8x10" Art Print Poster Mexican Folk Artist J Ellison. https://www.etsy.com/transaction/1334132911
14. THE ISSUE IS IN THE MIGRATION
Migration Classic Universal GTM
m c u g
=
15. YOU MAY BE TEMPTED TO…
Classic GA Property ID Number
Universal GA Universal ID Number
GTM Google Tag Manager
UA-XXXX123-1
UA-XXXX123-1
Your Website
16. WHAT COULD GO WRONG?
Bad or inflated data by
conflicting or
overlapping code (i.e.,
using the same
property ID all along)
No data on any view in
your property.
No data at all! (i.e., not
testing properly)
Data from Goals and
Events can stop while
the code is switched
(i.e., gap between
deleting old code and
new).
bad Really bad Very Extremely Mega Bad
17. THERE’S A SAFE, ALTERNATE SOLUTION
The “Parallel” testing with a migration plan
gtm.js
ga.js
or
analytics.js
Property A
Property B
19. YOU SHOULD
CONSIDER MIGRATING IF…
Classic Analytics Universal Analytics
+20 Custom Tags Manage
•Facebook tags
•Twitter tags
•AdWords
•Any other custom
HTML/JavaScript code
•Make your life easier
You Should Consider Google Tag Manager IF…
20. OLÉ
An this is how it’s DONE.
Day Of The Dead "The Bullfighter" 8x10" Art Print Poster Mexican Bull Matador Multiple Sizes Available Folk Artist J Ellison. https://www.etsy.com/transaction/1324512636
21. STEP 1: NEW PROPERTY
1
Create a NEW Property in Google Analytics and
recreate all views/filters from your current GA
Property.
Current Property
UA-XXXX123-1
Testing Property
UA-XXXX123-2
22. HOW GOOGLE TAG MANAGER WORKS…
1. Tag: A snippet of code (usually JavaScript)
added to a page.
2. Trigger: Defines when and where tags are
executed.
3. Variable: Used to receive or store
information to be used by tags and triggers.
GTM has pre-defined variables like:
Page URL: returns the full URL of the current
page (http://www.farmingdale.edu/about)
And you can build your own tags & variables.
23. STEP 2: CREATE CONTAINER IN GTM
2
Current UA-XXXX123-1
* Useful Tip: Use same name as your GA Property
Testing UA-XXXX123-2
UA-XXXX123-2
24. STEP 3: SETUP YOUR PAGE VIEW TAG WITH
NEW VARIABLE
3
29. STEP 5: WHILE YOU START COLLECTING
DATA, REVIEW EVENTS
5
Review your Events. This is the best time to do
an extensive inventory to find a common
ground:
•How many and where are they located?
•Which Events will you keep?
•Which ones to modify?
•Which ones to remove?
30. EVENT INVENTORY
WE ARE AMONG THE TOP 50
DESIGN AGENCIES IN THE UK.
Sed ut perspiciatis unde omnis iste natus error
sit voluptatem accusantium doloremque
laudantium, totam rem aperiam, eaque ipsa quae
ab illo inventore veritatis et quasi architecto beatae
vitae dicta sunt explicabo.
40. STEP 6: REVIEW YOUR GOALS
6
Just like with Events, do another inventory for
all your Goals:
•All Goals per View
•Which Goals need adjustment since some
Events’ actions and labels changed
•Different from Events, Goals will need to
individually be modified in ALL views.
44. STEP 7: REVIEW DATA, MAKE ADJUSTMENTS
7
Testing UA-XXXX123-2
Current UA-XXXX123-1
Current UA-XXXX123-1 Testing UA-XXXX123-2
45. STEP 8: PLAN FOR MIGRATION
8
• After testing your data and you’re confident
you have the results you want, it’s time to plan
for the migration.
• The migration/upgrade consists of:
• Remove all existing Universal code
(tracking code and event tracking code).
• Switching GTM variable from Testing
UA-XXXX123-2 to Current UA-XXXX123
• Set an official (realistic) date and timeline for
the migration.
46. REMOVE ALL CUSTOM EVENT TAGS
An audit may be helpful to find
them all.
All matches will have to be
deleted.
47. MAKE SURE OLD EVENT TRACKING CODE IS
REMOVED!
<li>
<a href=https://www.farmingdale.edu/about/contact-us.shtml onclick="ga('send', 'event',
'Footer Call to Action Buttons', 'click-contact-us', 'Footer Contact Us /about/contact-
us.shtml', 10, {'nonInteraction': 1});” class="btn btn-default .btn-sm btn-block
call-to-action-gtm”> <i class="fa fa-comment-o fa-fw"></i> Contact Us</a>
</li>
<li>
<a href=https://www.farmingdale.edu/about/contact-us.shtml class="btn btn-default .btn-
sm btn-block call-to-action-gtm”> <i class="fa fa-comment-o fa-fw"></i> Contact Us</a>
</li>
48. DAY OF SWITCH: REMOVE ALL CUSTOM TAGS
Remove the GA code for
Classic/Universal Analytics
and schedule pages to publish
on merge date.
Leave your GTM code intact
Remove all instances of
Classic/Universal custom tags
code and set pages to publish
on merge date.
49. STEP 9: ON MERGE DATE, SWITCH PROPERTY
ID IN GTM VARIABLE
9
From Testing
UA-XXXX123-2
To Current
UA-XXXX123-1
50. MAKE SURE NOW YOU’RE TRACKING
UAXXXX123-1
Current
Property
UA-XXXX123-1
51. STEP 10: PUBLISH YOUR CONTAINER
10
Publishing both pages and GTM container
must be done at the same time. Any gap or
overlapping when switching can affect your
data!
52. CHECK WITH GTM PREVIEW MODE
Check that all your tags are firing and passing the right variables
53. CHECK WITH GA REAL TIME
Check that you events and Goals are working properly
Keep closed monitoring in the next 48 hours
54. YOUR MAIN PROPERTY DATA CONTINUES…
Current Property A: UA-XXXX123-1
Testing Property B: UA-XXXX123-2
That’s it!
56. CONSIDER UPDATING/MIGRATING IF…
You are using Classic Analytics
You are using Universal Analytics and you have at least
20 custom JavaScript tags on your website
You want to manage your Facebook tags, Twitter tags,
AdWords, event tags, and any other custom
HTML/JavaScript code
Make your life easier
57. STEPS FOR A SAFE MIGRATION
1. Create a new Property in GA, recreate your views.
2. Create a container in GTM.
3. Setup your tracking code with a Page View tag and a variable to
store your new Property ID.
4. Install GTM code on your website along your current GA code.
5. Review your Events.
6. Review your Goals.
7. Review your collected data, make necessary adjustments.
8. Plan for upgrade: Set a date and timeline, remove GA tracking
code and custom tags, set pages to auto-publish.
9. On upgrade day, switch to current Property ID in GTM variable.
10. Publish your container and monitor for the next few days.
58. ADVICE
Same steps apply when migrating from Classic to
Universal, Classic to GTM.
Do your testing for at least two months so you’ll have
data for comparison.
Schedule the switch at the end of the spring semester.
Do it on a Monday! You’ll have all week to fix any mess.
You’re welcome.
60. THANK
YOU!
Questions?
Day Of The Dead "Street Party" Frida Kahlo and Diego Rivera, 8x10, Art Print Poster Mexican Folk Artist J Ellison. https://www.etsy.com/transaction/1334132907
Slides available at:
https://www.slideshare.net/SylviaNavarroNicosia/how-to-defeat-the-beast
Notas do Editor
My name is Sylvia Nicosia, I’m the Director of Web Programming and Development at Farmingdale State College, State University of New York, and I’m going to talk to you about defeating the beast when upgrading from Classic Analytics, Universal Analytics, to Google Tag Manager.
Day Of The Dead &quot;Horse and Rider&quot; Instant Digital Download Printable Art jpeg Print Mexican Folk Artist J Ellison
https://www.etsy.com/transaction/1334132909
Nowadays institutions of higher education depend greatly on data to make any kind of informed decisions ranging from recruitment, student engagement, giving, web design/redesign, and web content, among others.
There are plenty of options out there, open-source and paid that offer great analytic solutions tailored specific for higher education. Either solution you choose or whether you use Google Classic, Universal, and Google Analytics, you know you’re getting very valuable information to assist you in the most common goals in higher education: recruitment of prospect students, engagement from current students, and increasing donations from your alumni, among others.
And the common denominator in higher education is Google Analytics, which has become a very important factor
Before jumping into detail, some useful information.
A quick research to 190 institutions and companies attending HighEdWeb 2017 to determine what are they using for their analytics… These results as of August 24, 2017.
This research provided very good numbers in the sense that 99% has some sort of analytics in place. While almost half is already using Google Tag Manager, only 11% is using Google Classic Analytics, and a 31% is using Google Universal Analytics.
A big percent already using Google Tag Manager, and a very low number using Classic Analytics. Thirty-one percent using Universal.
These institutions are all in the process of updating to the next level of analytics.
This section focuses on those using Classic and Universal.
Should you migrate? You have a large site, already set Goals and event tracking, constant data… Should you bother upgrading to Universal or to Google Tag Manager?
A quick review from each version…
Classic Analytics:
Uses old tracking code ga.js Javascript library
Google Analytics properties were transferred to Universal Analytics, however it’s unclear what will happen to those properties which are still utilizing the old tracking code
Misses features from Universal Analytics such as User ID (User ID: Helps tracking the same user across different devices.)
Google can make old tracking script stop working at any time
Needs custom tags to track events
&lt;a href=&quot;http://farmingdale.edu/catalog.pdf&quot; onClick=&quot;_gaq.push([&apos;_trackEvent&apos;, &apos; PDF Downloads&apos;, ‘Click&apos;, ’Catalog&apos;);&quot;&gt;Catalog&lt;/a&gt;
Sources:
https://www.analyticsmania.com/post/difference-between-google-analytics-and-universal-analytics/
Universal Analytics:
Uses tracking code analytics.js Javascript library
All new Properties use it
Enjoys cool features from Universal
Connect multiple devices, sessions, and engagement data with the User ID.
Still needs custom tags to track events
&lt;a href=&quot;http://farmingdale.edu/catalog.pdf&quot; onClick=&quot;ga(‘send’, ‘event’, ‘ PDF Downloads’, ‘Click’, ‘Catalog’);”&gt;Catalog&lt;/a&gt;
Sources:
https://support.google.com/analytics/answer/2790010?hl=en
Google Tag Manager
Uses tracking code gtm.js Javascript library
Minimal amount of coding for more complex tags
GTM does not replace your analytics, but helps you easily add GA tracking code (tags) to your website
Built-in debug feature, preview mode
Built-in tags
Event tracking: No more custom JavaScript tags on your site
&lt;a href=&quot;http://farmingdale.edu/catalog.pdf&quot; class=“gtm-catalog”&gt;Catalog&lt;/a&gt;
“GTM makes your life easier by simplifying the process of adding these JavaScript snippets to your website. Instead of updating code on your website, you use the interface to decide what needs to fire and on what page or what action. GTM then adds the appropriate tracking to your site to make sure it all works.”
Harmon, K. (2016, February 15). What Is Google Tag Manager? (And How Does It Work With Google Analytics?). Retrieved from https://www.lunametrics.com/blog/2016/02/15/what-is-google-tag-manager/
Sources:
http://www.lunametrics.com/blog/2017/03/23/10-reasons-start-google-tag-manager/
http://www.ironpaper.com/webintel/articles/8-benefits-google-tag-manager/
https://www.lunametrics.com/blog/2016/02/15/what-is-google-tag-manager/
There’s Classic, Universal, and Google Tag Manager, but which one? Is it one better than the other one?
Day Of The Dead &quot;See No Evil, Hear No Evil, Speak No Evil&quot; 8x10&quot; Art Print Poster Mexican Folk Artist J Ellison
https://www.etsy.com/transaction/1334132911
The issue comes when at certain point you need to upgrade your Google Analytics. Migrating from Classic Analytics to Universal or from Universal to Google Tag Manager can be a cumbersome task and if done improperly, it can give you LOTS of headaches and can result in a disaster with your data.
You may be tempted to just switch your tracking code on your website of use your same Property ID in Google Tag Manager. Don’t, it can affect your data in ways that it cannot be reverted or recovered.
Sources:
http://blog.productcart.com/2014/05/using-googles-universal-analytics-tracking-code/
http://www.lunametrics.com/blog/2016/11/22/google-tag-manager-snippet-placement/
You may ask yourself, what could possibly go wrong?
From Lunametrics, a well-known digital marketing and web analytics consulting firm, “Migrating a very large site to GTM can pose some serious challenges: if done incorrectly, data collection can stop while the code is switched (bad), become dirtied by conflicting code (very bad), or cease altogether (extremely bad). The end goal of this process is that you data in Google Analytics remains constant, without any disruption when you make the transition.”
Source:
Safely Migrating to Google Tag Manager, http://www.lunametrics.com/blog/2015/07/16/safely-migrating-to-google-tag-manager/
From our own experience, reading, taking analytics classes and workshops, we learned the SAFE way to do the migration, where your original data remains constant, untouched, and not altered while making the transition.
The goal is to keep your current data steady while you do your testing. Any mistake can result of loss of valuable, irreplaceable data.
You should consider migrating if you’re using Classic or Universal; if you have at least 20 custom tags throughout your website (you only keep adding them from this point on); if you need a centralized platform to manage Facebook and Twitter tags, AdWords, or track anything you want.
Sources:
http://www.socialmediaexaminer.com/google-tag-manager-what-marketers-need-to-know-christopher-penn/
https://www.analyticsmania.com/post/google-tag-manager-vs-google-analytics/
There’s proper planning to do a safe transition between your current settings and GTM.
Day Of The Dead &quot;The Bullfighter&quot; 8x10&quot; Art Print Poster Mexican Bull Matador Multiple Sizes Available Folk Artist J Ellison
https://www.etsy.com/transaction/1324512636
This is a combination of a proper installation and some planning.
Create a new Property in Google Analytics to start collecting data as soon as possible. This will be a temporary property for testing.
Google Tag Manager has pre-defined variables for you to use. You can also create your own.
https://www.lunametrics.com/blog/2016/02/15/what-is-google-tag-manager/
Create your Container in GTM. A container is the equivalent of a Property, and this is where you will send all your information into Google Analytics. Use a variable to store your Property ID. This will come handy when we do the switch later on.
A tag is a snippet of code that sends that information to your Google Analytics. The Page View tag tells GTM to send a Page views to Google Analytics and the trigger tells GTM to send that Page view every time a page is loaded. This is how you install your Universal Tracking code from GTM.
Sources:
http://www.digitalmarketer.com/guide-to-google-tag-manager/#creation
Paste the GTM code into your website. Do not change or remove any of the existing GA code, both go together.
The idea is to have your current property and a test property where you will do all your testing without disrupting your current data.
Google Tag Manager has a Preview mode and a debug panel that allows you to see your tags in action on real time. This is very useful when testing your tags. You can check that your recent created tag is indeed working.
Once you’re done, leave Preview mode and click Submit. GTM will save every time a version of your container, which allows you to revert it in case anything goes wrong.
Now you’re collecting data, but it takes Google Analytics 24 hours before we can see any data. This is the best opportunity to do an inventory of your Events. Which ones to move to GTM, which ones to remove? How many do you have, hundreds? Make note where the code is installed. Few pages, hundred pages?
A spreadsheet is a must when dealing with events.
This how events are tracked in your current Property, either with Classic or Universal.
A tag is a piece of code that sends information to a third party, such as Google Analytics. Tags are used to track events in GTM.
Source:
https://support.google.com/tagmanager/answer/3281060?hl=en
This is how Google Tag Manager works behind the scenes tracking events to send them to your test Property.
Track events on both properties to compare your data. If tracking the same on both properties, data should be similar in numbers. If you have a huge gap in data, thousands, this is the time to review what you’re tracking. Are you using the right variables? This is why you do it on a test Property. If something goes wrong, all this happens on the test property; your current data remains the same.
One of the great advantages of switching to Google Tag Manager, is the ability to track complex tags with little or none complex code. Tracking downloads is the best example.
With four lines of JavaScript code to track any type of download you specify in your trigger.
Check your tag is working as intended.
And check in Google Analytics in Real Time that you are tracking the right variables and sending the right information to Google Analytics.
The details in the tracking will make you wonder why you didn’t switch to Google Tag Manager any sooner.
Now we are able to track several documents at the same time, but also provides the URL for that particular document.
Just like with Events, do another inventory for all your Goals:
All Goals per View
Which Goals need adjustment since some Events’ actions and labels changed
Different from Events, Goals will need to individually be modified in ALL views.
It helps to do a spreadsheet to better be able to visualize your Goals and how they will be organized in your testing Property.
If you will use the same Goal, find a common ground on both properties so you will get the same data on your current and testing properties.
You need to check that each Goal is working on each view and compare your results to see that you are getting the data you want, especially if you had to modify some of your events.
Both properties should start looking something like this. Review your data, make any necessary adjustments.
After testing your data and be confident you have the results you want to track, it’s time to upgrade. The upgrade consists of switching GTM from Property UA-XXXX123-2 to UA-XXXX123-1. Set an official and realistic date to do the upgrade that you know you’ll have everything ready by that day.
Use your Content Management System to do an audit of all your custom tags. They all will have to be deleted on upgrade day.
On the day of the upgrade, you’ll need to delete your current tracking code and live only the Google Tag Manager.
You also need to delete all custom tags for tracking events. Ideally you deleted the code and set the pages to publish on your upgrade day, all at the same hour, let say, noon.
On merge day, about half hour before you publish your pages, you will switch the Property ID from UA-XXXX123-2 back to UA-XXXX123-1. Any place you used this variable, automatically will apply the new Property ID.
Depending of your settings or Content Management System, the idea is to delete the old code and switch the Property ID in GTM at the same time. Please remember that any gap between deleting the old code and switching to the new Property, it will result in a gap with your data. Also, any overlapping, will result in double counting your data, therefore you’ll have inflated data.
Use Preview and Debug mode to make sure the new Property ID is the one showing.
Weber, J. (2015). Practical Google analytics and Google tag manager for developers. Berkeley, CA: Apress.
Make sure you’re now tracking your current property.
Publish your container and hope for the best!
Keep monitoring with Preview and Debug to check that your tags are working, that your current Property ID is the one getting all the hits…
Use Google Analytics “Real Time” to check that your Goals and events are working properly. Keep close monitoring in the next 48 hours to be able to detect any anomaly and be able to fix it right away.
If everything went well, your Property should look like this, where your main data remains constant. It means that you had a successful upgrade.
These same steps are the same if updating from Classic to Universal Analytics.
Before we go, a quick review.
Create a new Property in GA
Create a container in GTM
Setup your Page View tag with a variable
Install GTM code on your website along your current GA code
Review your events
Review your Goals
Review your collected data, make necessary adjustments
Plan for upgrade: Remove GA tracking code and custom tags
Switch Property ID in GTM variable
Publish your container
Source:
Weber, J. (2015). Practical Google analytics and Google tag manager for developers. Berkeley, CA: Apress.
Some good advice:
Do your testing for at least two months so you’ll have data for comparison.
Schedule the switch at the end of semester.
Do it on a Monday! You’ll have all week to fix any mess.
Image source:
http://hero.wikia.com/wiki/File:GEICO-Lizard-psd74226.png
Useful resources:
Simo Ahava’s Blog
https://www.simoahava.com/
LunaMetrics
https://www.lunametrics.com/
Weber, J. (2015). Practical Google analytics and Google tag manager for developers. Berkeley, CA: Apress.
Thank you. Questions?
Day Of The Dead &quot;Street Party&quot; Frida Kahlo and Diego Rivera, 8x10, Art Print Poster Mexican Folk Artist J Ellison
https://www.etsy.com/transaction/1334132907