Why doesn't a form submission re-link a lead to it's token? | Community
Skip to main content
jtesmerapqc
jtesmerapqc
Level 2
October 14, 2021
Solved

Why doesn't a form submission re-link a lead to it's token?

  • October 14, 2021
  • 1 reply
  • 4017 views

Hi there.   I recently encountered a situation where a lead was navigating through our website but the visitWebPage and clickLink events were not being recorded as activities in the activity log.

I checked into the browser configuration and confirmed that:

  1. the JS was configured correctly and clickLink and visitWebPage events were being POSTed to Marketo
  2. Do Not Track was OFF

I expected the events to flow into the activity log.

Upon further investigation, I realized that the CURRENT token value for the user was not recorded in the cookies value on the lead record. (I tested this using postman). Lots of other token values were there, but not the current one.

I followed the advice on this post and filled out a form as this user: Solved: When does a Cookie meet and match it's lead? - Marketing Nation (marketo.com.

I can see in the cookie is sent in the form submit, but the cookie was not updated on the lead record:

 

After this, I used the associate.json endpoint to manually associate the cookie to the lead record:

After I did that, all of the web activity flooded in.

So my question is: why isnt the form submit sufficient to link the cookie to the lead record? Do we need to be doing anything differently? Should we be calling the associate endpoint for all of our requests once we identify the user, just in case the cookie changes?

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

Sounds like you’ve changed something on your form. It should not be sending a field named cookies. You should see the field _mkt_trk sent. This automatically contains the current _mkto_trk cookie.

 

Post a link to your page so we can see how you’ve altered the behavior.

1 reply

SanfordWhiteman
SanfordWhitemanAccepted solution
Level 10
October 14, 2021

Sounds like you’ve changed something on your form. It should not be sending a field named cookies. You should see the field _mkt_trk sent. This automatically contains the current _mkto_trk cookie.

 

Post a link to your page so we can see how you’ve altered the behavior.

    SanfordWhiteman
    SanfordWhiteman
    Level 10
    October 14, 2021

    And no, you absolutely should not be calling the REST API Associate Lead for every form post. Association is automatic. If you were to consume API calls like this you’d have an instant DDoS vulnerability.

      jtesmerapqc
      jtesmerapqcAuthor
      Level 2
      October 15, 2021

      Got it, thank you.

      Terms & ConditionsAccessibility statement

      Loading footer...