Non-Marketo From Submission & Push Lead API -- Preventing Conflicts | Community
Skip to main content
Dave-Silva-2
Dave-Silva-2
Level 3
October 14, 2025
Solved

Non-Marketo From Submission & Push Lead API -- Preventing Conflicts

  • October 14, 2025
  • 1 reply
  • 937 views

Hi,

 

We are using a Salesforce Commerce experience with a non-Marketo form, which creates leads in Salesforce, which then sync over to Marketo. However, no Marketo web visit data is being collected, so I'm looking to use the Push Lead to Marketo endpoint to send the submission to Marketo and tie it to the web visit data being collected by Munchkin (already installed on the commerce site).

 

How do I do this to avoid conflicts with the same lead being created in both systems?

Can I just associate the lead that is initially created in SF with the munchkin cookie somehow?

 

Thanks!

Best answer by SanfordWhiteman

Attach the Munchkin cookie to the SFDC form post as a hidden field. When the person is created in Marketo or that field changes, call a webhook. The webhook-compatible service loops back to call either Associate Lead or Push Lead.

 

Main difference between the 2 endpoints is Associate is completely silent in the activity log — which may either reduce or increase confusion 😉 — while Push logs its own activity and adds the person to a program and is easier to audit. Choose based on your desired outcome.

 

Todd @ Sponge lays out one such setup here. It’s not necessarily exactly the way I do it as of late 2025, but it definitely works!

1 reply

SanfordWhiteman
SanfordWhitemanAccepted solution
Level 10
October 14, 2025

Attach the Munchkin cookie to the SFDC form post as a hidden field. When the person is created in Marketo or that field changes, call a webhook. The webhook-compatible service loops back to call either Associate Lead or Push Lead.

 

Main difference between the 2 endpoints is Associate is completely silent in the activity log — which may either reduce or increase confusion 😉 — while Push logs its own activity and adds the person to a program and is easier to audit. Choose based on your desired outcome.

 

Todd @ Sponge lays out one such setup here. It’s not necessarily exactly the way I do it as of late 2025, but it definitely works!

    Dave-Silva-2
    Dave-Silva-2Author
    Level 3
    October 15, 2025

    Thanks Sanford, that makes sense!

    When I visit a page with our Munchkin code and grab a token value and use it via Push or Associate, it doesn't work. Any idea on why that approach doesn't work for testing?

    SanfordWhiteman
    SanfordWhiteman
    Level 10
    October 15, 2025

    Have to be more specific than “doesn't work” I’m afraid.

     

    Are you making sure to URL-encode the cookie if using Associate (since it’s in the query string, you need to encode it like any other param).

     

    What’s an example payload you’re sending to Associate or Push?

    Terms & ConditionsAccessibility statement

    Loading footer...