Uploaded image for project: 'jboss.org'
  1. jboss.org
  2. ORG-3713

Disable / delete the Google Tag Manager (GTM) rule which is responsible for inserting the legacy Eloqua Tracking Scripts

XMLWordPrintable

    • 5
    • MWES 2017-09-19

      Background:
      The Eloqua Tracking Scripts are responsible for recording web visitor tracking in Eloqua, with the intention of connecting pages views directly to an email address for the purpose of later segmentation.

      Example: Send this email to all the Eloqua Contacts in the United States, who have downloaded ABC Whitepaper in the last 30 days, and/or have visited XZY webpage (by URL) in the last 10 days.

      The key to this functionality is a connection between a unique GUID dropped into a Cookie called "GUID" for .eloqua.com and an email address of an Eloqua Contact, which is facilitated by:
      1- An email is sent to an email address, and that email is opened / clicked-through (depending on the email client, click-through might be required)
      2- A form submit, on an Eloqua hosted landing page, directly to an Eloqua form

      #2 can also be accomplished by using javascript to pull the value of the GUID Cookie from the .elqoua.com, and submit it to a hidden field on the Eloqua form-end point called "elqCustomerGUID"

      And by convention, because "elqCustomerGUID" is not a visible field within the Eloqua Form Submission Data UI, we (Marketing Operations) asks our integration partners to also post the value of the GUID Cookie from the .elqoua.com, and submit it to a hidden field on the Eloqua form-end point called "A_ElqVisitorGuid."

      To make this integration easier for our integration partners, when Red Hat's DPAL is deployed on the web property, the data of the GUID Cookie from the .elqoua.com, will always be available in the rh_elqCustomerGUID

      Change Request:
      A- Please disable / delete the Google Tag Manager (GTM) rule which is responsible for inserting the legacy Eloqua Tracking Scripts (https://www.redhat.com/j/elqNow/elqCfg.js and/or https://www.redhat.com/j/elqNow/elqImg.js)

      • Once (A) is complete, then we will monitor for data flowing in to the Eloqua Form called "Integration Form: Jboss.org" / jboss-org-integration as a result of Account Create, Login, Update Profile and Download events to confirm the A_ElqVisitorGuid is still being populated in 70-80% of form submissions. We will wait for 1 weeks after the (A) is complete and then assess if additional changes need to be made.

            lkrzyzan@redhat.com Libor Krzyžanek
            gmanetti@redhat.com Greg Manetti (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: