Google Tag Manager - 5 years. What have we learned?
Sep. 23, 2017•0 likes•5,633 views
Download to read offline
Report
Internet
Looking back on five years of Google Tag Manager. Has the tool changed? Have we? What's coming up in the next 5 years?
My talk at MeasureCamp #11 (London).
3. Simo Ahava
Senior Data Advocate, Reaktor
Google Developer Expert, Google Analytics
Blogger, developer, www.simoahava.com
Twitter-er, @SimoAhava
Google+:er, +SimoAhava
9. Google Tag Manager
Lets you create and deploy tracking
and measurement scripts with ease.
Facilitates interaction between various
departments within your organization.
10. Google Tag Manager
Lets you create and deploy tracking
and measurement scripts with ease.
Facilitates interaction between various
departments within your organization.
Allows you to focus your time on analysis
rather than implementation.
19. Landing Page, Session, and Touchpoint are terminology of a
stateful machine.
The web page feeds data to the server, which builds the data
pipeline. Thus state and sessionization are handled in the backend.
21. {"sessionCount": "2", "firstTouch": "cpm"}
Could we introduce state?
Why doesn’t Google Analytics tell us details about
the session in the server response?
22. {"sessionCount": "2", "firstTouch": "cpm"}
Could we introduce state?
Why should Google Analytics tell us details about
the session in the server response?
30. Why it’s about marketing.
1. Tags collect data for digital marketing purposes, first and
foremost.
2. TMS abstracts the underlying code — low barrier of entry
for people with little coding experience.
3. Semantic data collection is easy to deprioritize by
developers who are more invested in the presentational and
experiential layers.
31. Why it’s about development.
1. It’s a freaking code injector!
2. You can add all sorts of malicious / website-breaking /
malware-infested code with the click of a button.
3. If something goes awry, developers will be held
accountable as they own the processes.
4. A TMS can actually make development work easier, too.
32. Why it’s about organizations.
1. Data flows through the entire organization - it doesn’t care
about job titles.
2. Data quality can be compromised at every junction of the
data process - not just collection.
3. Any company/platform/tool/service collects absurd
amounts of data each passing second - only a mature
organization can tackle this overload.
36. You can write fragile fixes to the
document object model.
37. If you use a TMS to fix issues that
should be fixed in the page
template or site JavaScript, you’re
using it wrong.
39. Things you can do with a TMS, if
the browser doesn’t execute
JavaScript:
40. Things you can do with a TMS, if
the browser doesn’t execute
JavaScript:
41. At its best, a TMS can be used to…
Deploy the latest versions of marketing, advertising, and
analytics trackers with ease.
42. At its best, a TMS can be used to…
Create, manage, and distribute semantic information on the
page.
43. At its best, a TMS can be used to…
Facilitate the agile analytics process - so crucial to any service
development.
44. And more!
1. Proof-of-concept experiential & presentational changes to
get buy-in from developers / HiPPOs.
2. Inject semantic markup (JSON-LD, META)
3. Resolve scripting conflicts on the site.
4. Load 3rd party libraries (e.g. jQuery) asynchronously.
5. Consolidate the codebase, write ad hoc JavaScript, inject
HTML elements, etc.