How to remove tracking from landing pages

[Dan_Stevens_]

We need to create an internal landing page that we can provide to our telemarketing team to directly submit the status of leads that are generated.  Since a single user will be entering multiple leads, we don't want this user to be tracked/cookied.  But I don't see anywhere within our landing page templates where the Munchkin code exists (so that we can create a version without the code).  Therefore, how do we create non-trackable landing pages?

[SanfordWhiteman]

@Bryan that's good to hear -- if you can confirm again this is working then I can officially put my script together into a "HOWTO".

[Anonymous]

Just a follow up note, we added the empty cookie script to the LP along side of turning off the tracking in the menu and that seems to prevent the tracking.

[Anonymous]

@ Dan

When you edit the LP template

Template Actions Menu > Enable /Disable Munchin Tracking



I can tell you though this didn't entirely work.  Each form also adds munchkin tracking lines also so it may be both the cooking clearing line + this.. still trying to work it out ourselves..

[Tim_Madel1]

Seems as though that option no longer exists?  I do not have the option to Enable/Disable Munchkin Tracking

[SanfordWhiteman]

@Megan R Your phone calls page (if it's still http://offers.netgainit.com/phonecalls.html) does not have the cookie-clearing code that I recommended.

[Megan_Reed1]

@Sanford that would be wonderful. Thank you for your help!

[SanfordWhiteman]

Yes, that is all in line with what we've been saying. But if you have the cookie-clearing line in there this cannot happen, because there is nothing to associate with at the time the form is processed. I'll take a look at your page later to see if the code is in the right place and is firing.

[Megan_Reed1]

@Sanford Yes, I believe Marketo support gave a valid reason for what I was seeing though:

Removing munchkin from the form page will cause only that page to not track leads. If the lead goes anywhere else it will set a cookie if the page contains munchkin. It will be anonymous until the lead identifies. In this case, the lead was already cookied, so the anonymous lead with page visits was merged with lead form fill activity when the lead became known. 

[SanfordWhiteman]

@Megan R are you still experiencing the earlier behavior, even with the cookie being overridden with that script snippet and the Munchkin tracking code not loading?

[Megan_Reed1]

Yes, Marketo support shared that new feature with me. 

Dan - You have to make the LP mobile compatible first. On the top, right hand corner of the LP you should see a button for "Make Mobile Compatible." After that's completed a drop down appears on the top left that says "Template Actions" where you can select to disable munchkin tracking. 

[Dan_Stevens_]

Bryan, where is this option located?  I don't see that anywhere within the landing page editor.

[Anonymous]

Landing page templates no longer have the <php tracking line> but now have a drop down menu that allows you to enable and disable tracking

[Megan_Reed1]

Hi Sanford - I apologize for that and greatly appreciate your help. The URL is working again if you have a chance to take a look. 

[SanfordWhiteman]

http://offers.netgainit.com/phonecalls.htm now redirects to your home page so I can't really comment on that.

[Megan_Reed1]

Strange results - I tested 3 form fill outs, one after the other and inbetween visited a couple of pages on www.netgainit.com.

Test 1 obviously worked.

Test 2 worked (I visited 2 pages on the site with Munchkin tracking and they did not appear in the activity log.)

Test 3 didn't work. Test 3 shows the 4 pages visits I made (2 inbetween test 1 & 2 and another 2 pages inbetween test 2 &3). Then shows the form fill out and subsquent page visits. 

Weird, huh?

[SanfordWhiteman]

@Megan R Actually the scenario you're describing is different from the exit link.  What's happening in your case is the automatic cookie association with the latest lead, which occurs because there is an existing cookie.

Try adding the following in the HEAD of your LP:

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

The idea here is that we create an empty Munchkin cookie for the offers.netgainit.com subdomain only.  This won't overwrite the the Munchkin cookie that someone has elsewhere, but should prevent that "knowable" cookie from being sent with the form post.

 

[Ryan_Allen]

Hey @SanfordWhiteman , similar vein to this thread, having some issues with event sign in landing pages (program setup to mark as "attended" upon form fill) Munchkin tracking is turned off, I realize this thread is 5 years old so not sure if that script is still valid, but the issue I'm trying to address is the same GAClientID being assigned to each lead upon form fill. Since these are all done from the same device it presents an issue with reporting/ accurate tracking.  Any chance you can point me in the right direction? 

Thanks!

Ryan

[SanfordWhiteman]

Kind of confused about what this has to do with Munchkin?  GA doesn't get its info from the Munchkin cookie, totally different. (Unless you make them the same programmatically.)

[Ryan_Allen]

Ok thanks for clarifying! Will discuss with our developer further. 

[Megan_Reed1]

That makes sense. I was testing it by clearing all of my cache and cookies, visiting the landing page, filling out the form then visiting a few pages on www.netgainit.com to make sure those were not displaying in the activity log. Then I went back to the landing page (without clearing my cache/cookies and only by knowing the URL, the URL is not linked from any other page or to any other page), filled out the form with another email and looked at that activity log which showed the webpages I visited on www.netgainit.com. 

With your clarity, it must be because I visited the pages then filled out the form which would be an "exit link". I just tested by continuously filling out the form (as the caller would) and it work. Although it seems I'll have to have our internal person clear their cache/cookie before they start (in case they had been on our website for any reason that day). 

Is this the best/only way to accomplish this task?