GTM container positions: a summary of best & worst
•
0 likes•244 views
A history of GTM container positions over time showing the best practice set-up and issues to mistakes to avoid.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to GTM container positions: a summary of best & worst
Similar to GTM container positions: a summary of best & worst (20)
More from Phil Pearce
More from Phil Pearce (20)
Recently uploaded
Recently uploaded (20)
GTM container positions: a summary of best & worst
- 1. GTM container positions: A summary of best & worst
- 2. But first... ...a history lesson Before GTM... (i.e in the stone age) Google said...
- 3. Page <Head> Page <Body> ga.js Set-up GA classic like this... GA classic
- 4. Google then introduced GTM in 2012 GTM
- 5. Page <Head> Page <Body> dataLayer Google said install like this... gtm.js script ns.html noscript iframe GTM old position
- 6. However... most CMS`s such as Wordpress did not have a global top <body> GTM
- 7. So Google changed their guidelines in 2016... GTM
- 8. Page <Head> Page <Body> dataLayer Before gtm.js script GTM 2012 position ns.html noscript iframe
- 9. Page <Head> Page <Body> dataLayer After gtm.js script ns.html noscript iframe GTM 2016 position
- 10. However, some CMS still did not have a global <Body> GTM 2012 position
- 11. Page <Head> Page <Body> dataLayer No script in footer gtm.js script ns.html noscript iframe GTM footer position
- 12. The <noscript> bit only gets read by robots and old mobile phones (i.e wap phones) ns.html noscript iframe
- 13. Also for Google Search Console validation recommends DNS verification rather than inline GTM noscript or meta verification code
- 14. So... its fine to do this... noscript removed
- 15. Page <Head> Page <Body> dataLayer No script removed gtm.js script noscript removed GTM new position
- 16. Also if there`s no global <head>... GTM old position
- 17. Page <Head> Page <Body> dataLayer Placing everything in the <body> works gtm.js script ns.html noscript iframe GTM no head There will be a -1% reduction in reported traffic
- 18. If only a global footer is possible... GTM footer
- 19. Page <Head> Page <Body> dataLayer Placing everything in footer gtm.js script ns.html noscript iframe There will be a -2% reduction in reported traffic GTM footer
- 20. If you use jQuery...
- 21. Page <Head> Page <Body> dataLayer jQuery goes here... gtm.js script ns.html noscript iframe jQuery GTM new position i.e Don’t place jQuery after gtm.js as you wont be able to reliably call jQuery functions
- 22. Never do this...
- 23. Page <Head> Page <Body> Never place an iframe in <head> gtm.js script ns.html noscript iframe GTM wrong position It will break W3C validation & IE will trigger a warning
- 24. Lastly...
- 25. Page <Head> Page <Body> dataLayer 2 script gtm.js script1 ns.html noscript1 iframe GTM 2 scripts gtm.js script2 ns.html noscript2 iframe 1. The reason I don’t recommend this is there is a small increase in download size and JS execution cost from using 2 scripts. So, when possible try to consolidate into 1 script. 2. The GA360 zone feature uses a nested second script.
- 26. Summary...
- 27. Page <Head> Page <Body> ga.js GA classic was set-up like this... GA classic
- 28. Page <Head> Page <Body> dataLayer Google said install like this... gtm.js script ns.html noscript iframe GTM old position
- 29. Page <Head> Page <Body> dataLayer Before gtm.js script GTM 2012 position ns.html noscript iframe
- 30. Page <Head> Page <Body> dataLayer After gtm.js script ns.html noscript iframe GTM 2016 position
- 31. Page <Head> Page <Body> dataLayer No script removed gtm.js script noscript removed GTM new position
- 32. Page <Head> Page <Body> dataLayer Placing everything in the <body> does work gtm.js script ns.html noscript iframe GTM no head There will be a -1% reduction in reported traffic
- 33. Page <Head> Page <Body> dataLayer Placing everything in footer gtm.js script ns.html noscript iframe There will be a -2% reduction in reported traffic GTM footer
- 34. Any Questions?
- 35. Appendix