Form Submission doesn't respect Custom Dedupe Key

[tess_kelley]

Hello Everyone!

We are running into problems regarding our custom de-dupe rules in Marketo and related to Landing pages. Can anyone here help advise us?

Our dedupe rule is currently configured as email address + person partition + custom field, because we have multiple instances of contacts with the same email address.

The form submission on Landing Pages is not respecting the dedupe key and, as a result, the activity is not mapped to the contact record who received the email, navigated to the landing page and then submitted the form. Instead, filled out form activity is getting mapped to any contact in our instance with the same email address OR creating a new contact, and we assume it’s based off of the Marketo cookie tracking.

We have tried adding the custom dedupe field as a hidden field on the landing page as well as a URL parameter, and this hasn’t changed our situation. We have also tried inserting the below code into the Landing Page, in an attempt to remove the Marketo cookie tracking, but this has also not worked for us - in our testing, this did not remove the cookie.

MktoForms2.whenReady(function (form) {
   form.addHiddenFields({ 
      _mkt_trk: "",
      mkt_tok: ""
   });
   
   form.onSubmit(function (form) {
      form.vals({ 
         _mkt_trk: "",
         mkt_tok: ""
      });
   });
})

Our Question: How do we configure our Landing Pages so that they respect our custom de-dupe key and map to the correct contact record who received the email?

[tess_kelley]

Hello @SanfordWhiteman! Do you have any advice for us here? Thank you!!

[SanfordWhiteman]

---

We have tried adding the custom dedupe field as a hidden field on the landing page as well as a URL parameter, and this hasn’t changed our situation. We have also tried inserting the below code into the Landing Page, in an attempt to remove the Marketo cookie tracking, but this has also not worked for us - in our testing, this did not remove the cookie.

MktoForms2.whenReady(function (form) {
   form.addHiddenFields({ 
      _mkt_trk: "",
      mkt_tok: ""
   });
   
   form.onSubmit(function (form) {
      form.vals({ 
         _mkt_trk: "",
         mkt_tok: ""
      });
   });
})

---

That code does remove the cookie from the form post data— which is what you want.

It doesn’t remove the cookie from the  browser’s cookie store, nor is it expected to. So I don’t know which of these outcomes you were testing.

With that code in place, Marketo will not respect any existing cookie association when the form is posted (nor will it reassign the cookie, but that’s another matter). You would of course need the custom field on the form or else it’ll be blank for everybody, so there wouldn’t be a way to act on it.

If you can ensure the field is on the form and link to your page I’ll see if anything else is amiss.

[tess_kelley]

@SanfordWhiteman Thanks for helping us, we so appreciate it!

Here is a sample landing page : http://362-XMZ-144.mktoweb.com/lp/362-XMZ-144/test.html

[SanfordWhiteman]

On a Marketo LP, put your custom form behaviors just before the closing </body> tag, since you have to ensure MktoForms2 (the global object) is available.

(I've also posted a function in the past that lets you put form behaviors anywhere, but it's easier to just adjust the LP in this case.)

[tess_kelley]

@SanfordWhiteman  We have made that fix in the LP link, can you take a look again? Thank you!

[SanfordWhiteman · Accepted solution]

We can see the identifying marks (mkt_tok, _mkt_trk) are not sent with the form post:

This form post is functionally identical to not having Munchkin loaded at all, so it won't be able to use an existing associated lead.

[Luba]

Hi @SanfordWhiteman thank you so much for your help with this!  The code works great for form submission and with this code implemented, the "fill out form" activity now points to the correct contact! 

But pre-fill does not work consistently:  it works in incognito, but when there is a conflict with the cookie - prefill gets disabled. I understand the security measures that Marketo takes to prevent from prefill to be avaialble when people forward links - we would like to have this option for various use cases.

And "visit web page" still does not point to a correct recipient who clicked through the landing page from email. 

I tried various solutions, including your suggestions from this post,  but cannot make it work, or doing this wrong. 

Is it possible to fix these two issues considering that we have a custom dedup key, and if yes, what would be the solution?  Thank you!!