Search (1 results, page 1 of 1)

  • × author_ss:"Farney, T."
  • × theme_ss:"Metadaten"
  1. Farney, T.: using Google Tag Manager to share code : Designing shareable tags (2019) 0.01
    0.011030916 = product of:
      0.03309275 = sum of:
        0.03309275 = product of:
          0.0661855 = sum of:
            0.0661855 = weight(_text_:publishing in 5443) [ClassicSimilarity], result of:
              0.0661855 = score(doc=5443,freq=2.0), product of:
                0.24522576 = queryWeight, product of:
                  4.885643 = idf(docFreq=907, maxDocs=44218)
                  0.05019314 = queryNorm
                0.26989618 = fieldWeight in 5443, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  4.885643 = idf(docFreq=907, maxDocs=44218)
                  0.0390625 = fieldNorm(doc=5443)
          0.5 = coord(1/2)
      0.33333334 = coord(1/3)
    
    Abstract
    Sharing code between libraries is not a new phenomenon and neither is Google Tag Manager (GTM). GTM launched in 2012 as a JavaScript and HTML manager with the intent of easing the implementation of different analytics trackers and marketing scripts on a website. However, it can be used to load other code using its tag system onto a website. It's a simple process to export and import tags facilitating the code sharing process without requiring a high degree of coding experience. The entire process involves creating the script tag in GTM, exporting the GTM content into a sharable export file for someone else to import into their library's GTM container, and finally publishing that imported file to push the code to the website it was designed for. This case study provides an example of designing and sharing a GTM container loaded with advanced Google Analytics configurations such as event tracking and custom dimensions for other libraries using the Summon discovery service. It also discusses processes for designing GTM tags for export, best practices on importing and testing GTM content created by other libraries and concludes with evaluating the pros and cons of encouraging GTM use.