AnsweredAssumed Answered

FT/LT/MT Cookie Scripts

Question asked by Sean Richards on Sep 30, 2018
Latest reply on Oct 1, 2018 by Grégoire Michel

Like • Show 1 Like1
Comment • 10

Dan Stevens. I've tried (and getting close) ti reverse engineering your UTM/Lead Source acquisition program/fields etc, combined with other posts and related conversations in the community to create my own UTM/lead source master program in Marketo to capture FT UTMs and LT UTMs, plus referrer data and feed this into Marketo on form submit, stamping the FT if empty, MT historys etc.

I am so close to having a complete understanding, but I am stuck on the website/JS side of things.

I get how it's meant to work with scripts like Yanir's (FT/LT UTM cookie script (Shoutout to Yanir!) - Q&A pretty please ) but I am unable to see how this is working on your website.

I've been trying to test on your website.

When I hit the avanade website with zero pre-existing cookies with the following parameters (e.g. avanade.com/en-au/technologies/data-analytics?utm_campaign=test&utm_medium=test&utm_source=test&utm_content=test&utm_term=test), or with an existing UTM stamped link (https://www.avanade.com/en-au/industry/banking/digital-disruption-report?utm_campaign=banking+report&amp;utm_medium=bitly&amp;utm_source=twitter) and then click to your contact page, on inspecting the cookies, I can't see where you are capturing the UTM's and passing them into fields for your last touch UTM capture and lead source attribution logic.

Your website also does some funky rewriting which stores the "ref" variable and passing it around as a URL parameter.

What am I missing here? I was quite sure you were capturing the UTM and referrer data into cookies for last touch reporting, and submitting it into Marketo forms, to feed it into your own lead source attribution logic, but can't find it in your javascript anywhere, nor see it on your forms?

Thanks in advance.

Sean

No one else has this question

Outcomes

Dan Stevens.

Oct 1, 2018 4:58 AM

Sean, we don't use js to keep those values persistent during the current session. Right now, we're just capturing those values on the initial landing page containing the form. Once we start using UTMs across all of our channels, we will use a more advanced method.

Actions

Sean Richards @ Dan Stevens. on Oct 1, 2018 5:53 AM

As always Dan, thanks for being awesome at responding.

You must be missing out on all the goodness of seeing organic, social

referral and direct lead source values by not having it setup this way

though.

On another note I took a look at the data demand base was filling in on my

session... Dam it was impressive!

Cheers,

Sean

On Mon., 1 Oct. 2018, 9:59 pm Dan Stevens, <marketingnation@marketo.com>

Actions

Dan Stevens.

@ Sean Richards on Oct 1, 2018 7:38 AM

We’re already addressing by integrating Bizible into our environment. Btw, Bizible doesn’t even rely on UTMs (but we’ll continie to use for our GA reporting).

Actions

Grégoire Michel @ Dan Stevens. on Oct 1, 2018 2:49 PM

Hi Dan,

Without any form of URL parameters, how does Bizzible do beyond identifying the referrer ?

-Greg

Actions

Dan Stevens.

@ Grégoire Michel on Oct 1, 2018 5:12 PM

Greg - their tracking script takes care of some of this. But you're right - you will loose a level of insight/attribution if you're at least not using source, medium and campaign (which we are). I do know, however, they are able to capturer "referrer" without UTMs. We're still in the infancy with Bizible - maybe Justin Norris can chime in with more info.

Actions

Sanford Whiteman @ Dan Stevens. on Oct 1, 2018 5:23 PM

They can only capture what the referring site agrees to send. If the referring site suppresses the referrer entirely, they'll have nothing to go on.

Actions

Justin Norris

@ Dan Stevens. on Oct 1, 2018 8:01 PM

Dan Stevens. Grégoire Michel

Bizible does leverage UTMs and it will also capture the referrer, if its available.

When a person visits a site that has the Bizible script running on it, Bizible logs data on the web session into its own cloud and then, after a form has been submitted, it checks the connected CRM for a record matching that email address. When it finds a match, the data points for the session are pushed into a custom touchpoint object linked to that record, and the UTM values are pushed into system-managed fields on the touchpoint.

You can configure a set of cascading rules in the Bizible interface using both UTMs and referrer strings to bucket these touchpoints into channels and sub-channels. Bizible is smart enough to detect some common channels (like organic search) automatically through pre-configured rules or through its integrations with services like Adwords.

The nice part of these cascading rules is that they can be modified and the data re-processed if needed - so for example if you make a typo in a UTM value, you can add the exception into your rules so that the touchpoints are categorized correctly.

1 person found this helpful

Actions

Dan Stevens.

@ Justin Norris on Oct 1, 2018 8:24 PM

Thanks for clarifying, Justin. We were given some incorrect information during our last demo of Bizible.

Actions

Grégoire Michel @ Justin Norris on Oct 1, 2018 11:38 PM

Thx Justin.

Actions

Grégoire Michel Oct 1, 2018 6:31 AM

More and more, for companies that have a minimum size, I tend to foster the use of separate tools to do what they do best. Meaning using a web analytics tool to capture the source of the traffic and the sessions, sharing common ID's between Marketo and the analytics and reconciling both in a datawarehouse. At the end of the day, it be less complex, and provide better, more comprehensive results, easier to leverage since the datawarehouse can easily be queried with a BI froint end (Google Data studio, cliq, tableau, ... You name it) that provide a top notch reporting service.

Emphasize needs to be placed on tagging correctly the inbound links (the UTM's) and share enough data between the analytics and Marketo to make the reconciliation accurate down to the interaction level. This means sharing form ID's to Analytics via GTM form instance.

-Greg

1 person found this helpful

Actions

10 Replies

Dan Stevens. Oct 1, 2018 4:58 AM
Mark Correct
Correct Answer
Sean, we don't use js to keep those values persistent during the current session. Right now, we're just capturing those values on the initial landing page containing the form. Once we start using UTMs across all of our channels, we will use a more advanced method.
Like • Show 0 Likes0
Actions
- Sean Richards @ Dan Stevens. on Oct 1, 2018 5:53 AM
  Mark Correct
  Correct Answer
  As always Dan, thanks for being awesome at responding.
  
  You must be missing out on all the goodness of seeing organic, social
  referral and direct lead source values by not having it setup this way
  though.
  
  On another note I took a look at the data demand base was filling in on my
  session... Dam it was impressive!
  
  Cheers,
  Sean
  
  On Mon., 1 Oct. 2018, 9:59 pm Dan Stevens, <marketingnation@marketo.com>
  Like • Show 0 Likes0
  Actions
  - Dan Stevens. @ Sean Richards on Oct 1, 2018 7:38 AM
    Mark Correct
    Correct Answer
    We’re already addressing by integrating Bizible into our environment. Btw, Bizible doesn’t even rely on UTMs (but we’ll continie to use for our GA reporting).
    Like • Show 0 Likes0
    Actions
    - Grégoire Michel @ Dan Stevens. on Oct 1, 2018 2:49 PM
      Mark Correct
      Correct Answer
      Hi Dan,
      
      Without any form of URL parameters, how does Bizzible do beyond identifying the referrer ?
      
      -Greg
      Like • Show 1 Like1
      Actions
      - Dan Stevens. @ Grégoire Michel on Oct 1, 2018 5:12 PM
        Mark Correct
        Correct Answer
        Greg - their tracking script takes care of some of this. But you're right - you will loose a level of insight/attribution if you're at least not using source, medium and campaign (which we are). I do know, however, they are able to capturer "referrer" without UTMs. We're still in the infancy with Bizible - maybe Justin Norris can chime in with more info.
        Like • Show 0 Likes0
        Actions
        Sanford Whiteman @ Dan Stevens. on Oct 1, 2018 5:23 PM
        Mark Correct
        Correct Answer
        They can only capture what the referring site agrees to send. If the referring site suppresses the referrer entirely, they'll have nothing to go on.
        Like • Show 0 Likes0
        Actions
        Justin Norris @ Dan Stevens. on Oct 1, 2018 8:01 PM
        Mark Correct
        Correct Answer
        Dan Stevens. Grégoire Michel
        
        Bizible does leverage UTMs and it will also capture the referrer, if its available.
        
        When a person visits a site that has the Bizible script running on it, Bizible logs data on the web session into its own cloud and then, after a form has been submitted, it checks the connected CRM for a record matching that email address. When it finds a match, the data points for the session are pushed into a custom touchpoint object linked to that record, and the UTM values are pushed into system-managed fields on the touchpoint.
        
        You can configure a set of cascading rules in the Bizible interface using both UTMs and referrer strings to bucket these touchpoints into channels and sub-channels. Bizible is smart enough to detect some common channels (like organic search) automatically through pre-configured rules or through its integrations with services like Adwords.
        
        The nice part of these cascading rules is that they can be modified and the data re-processed if needed - so for example if you make a typo in a UTM value, you can add the exception into your rules so that the touchpoints are categorized correctly.
        1 person found this helpful
        Like • Show 0 Likes0
        Actions
        Dan Stevens. @ Justin Norris on Oct 1, 2018 8:24 PM
        Mark Correct
        Correct Answer
        Thanks for clarifying, Justin. We were given some incorrect information during our last demo of Bizible.
        Like • Show 0 Likes0
        Actions
        Grégoire Michel @ Justin Norris on Oct 1, 2018 11:38 PM
        Mark Correct
        Correct Answer
        Thx Justin.
        Like • Show 0 Likes0
        Actions
Grégoire Michel Oct 1, 2018 6:31 AM
Mark Correct
Correct Answer
More and more, for companies that have a minimum size, I tend to foster the use of separate tools to do what they do best. Meaning using a web analytics tool to capture the source of the traffic and the sessions, sharing common ID's between Marketo and the analytics and reconciling both in a datawarehouse. At the end of the day, it be less complex, and provide better, more comprehensive results, easier to leverage since the datawarehouse can easily be queried with a BI froint end (Google Data studio, cliq, tableau, ... You name it) that provide a top notch reporting service.

Emphasize needs to be placed on tagging correctly the inbound links (the UTM's) and share enough data between the analytics and Marketo to make the reconciliation accurate down to the interaction level. This means sharing form ID's to Analytics via GTM form instance.

-Greg
1 person found this helpful
Like • Show 0 Likes0
Actions

FT/LT/MT Cookie Scripts

Outcomes

Related Content

Recommended Content