1 Reply Latest reply on Nov 16, 2017 5:41 PM by Sanford Whiteman

    Help implementing new GCLID parameters

    Kristina Blaire

      Due to the new privacy restrictions Apple implemented on it's Safari browser, Google has had to reconfigure tracking tags in order to capture traffic/conversions from Safari visits. In order to track AdWords conversions from Safari, we need to implement Google AutoTagging parameters which leverage the GCLID , (Google Click Identifier). The GCLID is used by Google to pass information back and forth between Google AdWords and Google Analytics. Once we enable URL auto tagging in Google AdWords, Google will append a unique GCLID parameter to our destination URLs at run-time.

      The problem comes from how to feed this into the Marketo platform for end-to-end sales pipeline tracking. Our current Marketo lead structures uses, "utm_campaign" - starts with - "SEM_" to categorize any leads into their applicable SF campaigns. With autotagging, we cannot specify a "utm" code.
      I need to update ALL of my Marketo "flow" setups to reflect the new structure, however I'm not sure how to identify this in the Marketo flow set-up.

      Is there a way to say that any traffic that contains "gclid" in the URL should be classified into the relevant Paid Search campaign?


      Appreciate the help!!

      Sanford Whiteman

      Grégoire Michel

      Joe Reitz


        • Re: Help implementing new GCLID parameters
          Sanford Whiteman

          You can catch the presence of the gclid by mapping it to a form field and/or constraining Visit Web Page by Query String [contains].


          You can't decode the valueof the gclid to anything meaningful within Marketo.


          In any case, gclid isn't really a replacement for persisting UTM tags. If you're trying to deal with Intelligent Tracking Protection, that pertains to all cookies, so if you store gclid in a cookie it's going to be deleted just like utm_campaign would after a certain period of time.