How do I set the form submissions to update the correct record based on PURL?

Forum|Forum|5 years ago
August 17, 2020
1 reply
4527 views

I have a PURL site: https://discover.uindy.edu/junior/KayeMcclendon

Whenever I submit the form (right side of page), it updates a different record: https://discover.uindy.edu/junior/X2YGTU-1

I do not collect the email address on the form or have any other parameters in the URL. I'm using an embedded form and I dynamically insert it using a token.

I did clear my cache this morning, which might have caused the problem. What do I do to force the form to update only the record based on the Marketo Unique Name "KayeMcclendon"?

Marketo

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

Best answer by SanfordWhiteman

You can't use that method with a form embed (actually, it doesn't even work reliably with a named form, though you can get results that make you think it does!).

You have to export the tokens like this:

<!-- export lead tokens into HTML context because they're HTML-encoded -->
<datalist class="exported-tokens">
  <option data-mktoform-field="Email">{{lead.Email Address}}</option>
  <option data-mktoform-field="Company">{{company.Company Name}}</option>
  <option data-mktoform-field="FirstName">{{lead.First Name}}</option>
  <!-- ... add additional tokens following same pattern... -->
</datalist>
<!-- /export lead tokens -->

<!-- bind exports to form fields -->
<script>  
  MktoForms2.whenReady(function(mktoForm){
    const arrayify = getSelection.call.bind([].slice);
    
    const exportedTokens = arrayify(document.querySelectorAll(".exported-tokens option"));
    
    const mktoFieldsObj = exportedTokens.reduce(function(acc,nextToken){
            acc[nextToken.getAttribute("data-mktoform-field")] = nextToken.value;
            return acc;
          },{});
    
    mktoForm.setValuesCoerced(mktoFieldsObj);
  });
</script>
<!-- /bind exports -->

SanfordWhiteman

New Participant

When you submit the form without an explicit Email Address field, and the Munchkin session is already associated, it keeps the previous association. Otherwise, you end up creating an address-less lead (not the same as an anonymous lead, btw).

AFAIK, this standard form behavior is irrespective of the use of pURLs, which have their own maddening quirks.

Solving this is easy. You need to add the Email Address as a Hidden field on the form.

Kaye_McClendonAuthor

New Participant

Hi Sanford,

I added the Email Address field as a hidden field on the form using the default value "{{lead.Email Address}}" yesterday. It still created a new record with the literal string "{{lead.Email Address}}" in the email field. Below is a screenshot of the new record in the database. Am I setting the token wrong? I am using an embedded form, by the way. I don't know if that makes a difference.

SanfordWhitemanAccepted solution

New Participant

You can't use that method with a form embed (actually, it doesn't even work reliably with a named form, though you can get results that make you think it does!).

You have to export the tokens like this:

<!-- export lead tokens into HTML context because they're HTML-encoded -->
<datalist class="exported-tokens">
  <option data-mktoform-field="Email">{{lead.Email Address}}</option>
  <option data-mktoform-field="Company">{{company.Company Name}}</option>
  <option data-mktoform-field="FirstName">{{lead.First Name}}</option>
  <!-- ... add additional tokens following same pattern... -->
</datalist>
<!-- /export lead tokens -->

<!-- bind exports to form fields -->
<script>  
  MktoForms2.whenReady(function(mktoForm){
    const arrayify = getSelection.call.bind([].slice);
    
    const exportedTokens = arrayify(document.querySelectorAll(".exported-tokens option"));
    
    const mktoFieldsObj = exportedTokens.reduce(function(acc,nextToken){
            acc[nextToken.getAttribute("data-mktoform-field")] = nextToken.value;
            return acc;
          },{});
    
    mktoForm.setValuesCoerced(mktoFieldsObj);
  });
</script>
<!-- /bind exports -->

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded