Non-trackable landing page is still identifying me | Community
Skip to main content
Dan_Stevens_
Dan_Stevens_
Level 10
October 27, 2015
Question

Non-trackable landing page is still identifying me

  • October 27, 2015
  • 5 replies
  • 6619 views

I've build a non-trackable landing page template that includes the following code:

<!-- CREATE EMPTY MUNCHKIN COOKIE - TO ESENTIALLY MAKE THE PAGE UNTRACKABLE -->

  <script>document.cookie = "_mkto_trk=;path=/;domain="+window.location.host+";expires=0"</script> 

<!-- END -->

 

<!-- Clear the Marketo tracking cookie value on submission of the form, without having to delete the cookie itself from the user’s browser. -->

  <script>

//add a callback to the first ready form on the page

MktoForms2.whenReady( function(form){

    //add the tracking field to be submitted

        form.addHiddenFields({"_mkt_trk":""});

        //clear the value during the onSubmit event to prevent tracking association

    form.onSubmit( function(form){

        form.vals({"_mkt_trk":""});

    })

})

</script> 

<!-- END -->

I then use this template to build a landing page with a form where no tracking or identification should occur (this page will be used internally to approve/deny event registrants).  Yet when I visit the page, all of the pre-fill fields are auto-populated with my name.  Am I forgetting another piece of code?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

5 replies

SanfordWhiteman
SanfordWhiteman
Level 10
October 27, 2015

window.location.host is the FQHN of the current page that appears in your browser's location bar.

In other words, for the Community site, nation.marketo.com.  You want to clear cookies that apply to the parent and all subdomains: .marketo,com.

Dan_Stevens_
Dan_Stevens_Author
Level 10
October 27, 2015

I'm not sure I'm following exactly.  Here's the landing page:

https://pages.avanade.com/Template---Roadshow---Head-Space-Event-Approval_approved.html?EmailAddress=daniel.r.stevens@av…

What changes are needed in the above code?

SanfordWhiteman
SanfordWhiteman
Level 10
October 27, 2015

Can't see the source from my mobile, but you probably want to replace

document.location.host

with

'.avanade.com'

Note that the quotation marks _are_ included.

Grégoire_Miche2
Grégoire_Miche2
Level 10
October 27, 2015

Hi Dan,

Pardon my question, Isn't "non traceable" landing page template working  ?

Why is that ?

-Greg

Dan_Stevens_
Dan_Stevens_Author
Level 10
October 27, 2015

Hi Greg - I understand what you're asking.  Can you clarify?

Grégoire_Miche2
Grégoire_Miche2
Level 10
October 27, 2015

My question is why do we need to add theses codes to non traceable LPs?

I haven't tested intensely, but it seemed to me that a non traceable should not be able to recognize you, but this post seems to suggest otherwise, so I am troubled.

-Greg

SanfordWhiteman
SanfordWhiteman
Level 10
October 27, 2015

The code that calls MktoForms2 methods must appear after the forms2.js script is loaded.

Dan_Stevens_
Dan_Stevens_Author
Level 10
October 27, 2015

So this can't be part of landing page template and instead needs to be manually added to any page that uses a form?

Dan_Stevens_
Dan_Stevens_Author
Level 10
October 28, 2015

...and if that's the case, how do you force it to appear after the forms2.js script is loaded when we can't alter the placement of those scripts (HTML snippet)?

Grégoire_Miche2
Grégoire_Miche2
Level 10
October 28, 2015

Hi all,

Development is nice, but using built-in features will be better.

Hence this idea :

-Greg

    J
    Jeff_Bedford
    Level 2
    January 16, 2019

    This is an awesome thread. I have a couple of questions:

    1) What is a good way in y'alls opinion to test out whether or not you have made the page untrackable?

    2) If I understand correctly - the 'untrackable' sentiment really refers to cookies/munchkin - and things like trigger campaigns, etc. will work just fine. I just want to make sure of that - if anybody could confirm?

    SanfordWhiteman
    SanfordWhiteman
    Level 10
    January 16, 2019

    2) If I understand correctly - the 'untrackable' sentiment really refers to cookies/munchkin - and things like trigger campaigns, etc. will work just fine. I just want to make sure of that - if anybody could confirm?

    "Untrackable" is probably an overly generic term.

    When discussing a form, it means submitting the form does not result in Munchkin session re/association with the submitting lead.  The Filled Out Form activity is still logged and the lead updated/inserted.

    When discussing a web page, it should mean viewing the web page does not result in a Visited Web Page activity. But unfortunately in this thread we're using the form definition... while talking about "the landing page." (I'm guilty of this, not pointing the finger at anyone.)

    When discussing a link in a web page, it means clicking the link does not result in a Clicked Link in Web Page activity.

    When discussing a link in an email, it typically means clicking the link does not result in a Clicked Email activity, nor does it result in Munchkin session re/association from the subsequent Visited Web Page activity  These two (in)actions can actually be decoupled so only the first applies, but usually are not.

    Obviously these cases can all be intermingled depending on what you need.

    1) What is a good way in y'alls opinion to test out whether or not you have made the page untrackable?

    Assuming you actually mean the form given my rundown above, depends on how technical you are.  I would watch the network tab to see that the POST to /save2 doesn't include the cookie.

      Terms & ConditionsAccessibility statement

      Loading footer...