4 Replies Latest reply on Sep 20, 2017 11:42 AM by Sanford Whiteman

    Tracking Marketo ID

    Sargam Gera

      We want to track the unique ID of the user in Google Analytics if someone fills out the Marketo form. Is there a way we can call the Marketo ID or Lead ID of the user? I cannot find any token for this.

        • Re: Tracking Marketo ID
          Jim Thao

          Use {{lead.id}}

            • Re: Tracking Marketo ID
              Sanford Whiteman

              Jim, {{Lead.Id}} can't be expected to be available directly after form fillout, so this won't work reliably.

               

              Sargam to ensure you have a unique, non-PII ID, generate a random hidden field client-side and keep a history of that field in Marketo.

               

              Built-in sort-of-alternatives are the Munchkin cookie value (_mkto_trk) and the aliId parameter, but both are problematic (in the first case, the cookie can be used to locate personal information and also may be reused; in the second case, you need to make sure there's a Visit Web Page logged for the Thank You URL that contains the aliId).

              1 of 1 people found this helpful
                • Re: Tracking Marketo ID
                  Mike Mason

                  We're trying to do something fairly similar in that we're trying to pass info back to google post form fill-out for ad serving quality purposes.

                   

                  We recently had 78 form fill-outs, 55 of which were undesirable. We want Google to optimize for the 23 positive conversions. To do that, we need to be able to tie the Google conversion pixel ID to some unique Marketo ID so after we determine what is undesirable, we can pass the Google Conversion ID back to Google so they can optimize accordingly.

                    • Re: Tracking Marketo ID
                      Sanford Whiteman

                      Then your choices would be a custom random (String) field generated on the client and stored on the lead, or the Munchkin cookie value (which is an existing form of random id).

                       

                      I'd definitely prefer use the former as it doesn't confuse the purposes of the the cookie (and the cookie might be reassigned, breaking a later lookup).