Best way to match SFDC to MKTO records?

[Geoff_Krajeski1]

How best would one recommend that a record that has activity via munchkin, but was first known/created in SFDC, to associate the records?

Is there any way aside from a mk_tok email string or form fill otherwise?

Would an API call upon submission be needed to accomplish this or might there be another way?

[Amit_Jain]

Hi Geoff,

As a best practice, the leads should be first created in Marketo and then should flow to SFDC otherwise, as you may already know, you will have lead duplication issues. Not sure but is there anything specific limitation/reason why you are not creating records directly in Marketo?

If you are already planing to develop API to achieve the result you want, why don't you integrate your other system with Marketo instead of SFDC? I'm sure pretty much everything can be integrated with Marketo using API.

Regards,
Amit

​

[Nina_Gonzalez1]

Amit, good point and when practical we start all leads in Marketo, but there are exceptions. Ecomm requires a lot more fields than we need in Marketo, API calls for each Ecomm step plus integration with our billing system. We've thought about APIs to both Marketo and SFDC, but at this time we think the flow is more direct to go into SFDC. If the lead is known, we update the existing record. And if the lead is unknown we are successfully syncing with Marketo. The only missing link is creating a connection between anonymous data in Marketo when a lead is first known in SFDC.

Similar scenario with Drift. Drift offers better integration with SFDC for appointments and chat transcripts, but then you lose the anonymous data that is stored in Marketo.

[SanfordWhiteman]

As a best practice, the leads should be first created in Marketo and then should flow to SFDC o

I don't agree that that's "best practice." Some orgs require that all records are born in SFDC first, and that's totally fine.

[SanfordWhiteman]

Do you know the Munchkin cookie value? The approach here needs to be to attach the Munchkin _mkto_trk value to the SFDC record, wait for the record to sync to Marketo, then call a webhook to do the association from the Marketo side. This is how we associate leads from CMS forms, for example.

[Geoff_Krajeski1]

Sanford Whiteman so if I have a Munchkin cookie of "id:123-ABC-789&token:_mch-americordblood.com-1549563917278-70845",

what would be the best way to read the munchkin cookie value?

Is this where the REST API or javascript or blank form comes into play?

[Jay_Jiang]

Gap here is... how did the lead get into SFDC first? manual entry? or SFDC web-to-lead?

[Geoff_Krajeski1]

Scenario: Our ecommerce checkout flow adds people directly into SFDC.

They have already been to the site and have an anonymous record and are cookied through Marketo.

Desired outcome: We need to tie the SFDC newly created lead to the existing anonymous Marketo record.

I think Sanford Whiteman​ may have the method above. Talking with my dev. team to help implement.

[SanfordWhiteman]

...if I have a Munchkin cookie of "id:123-ABC-789&token:_mch-americordblood.com-1549563917278-70845",

what would be the best way to read the munchkin cookie value?

You don't need to read the Munchkin cookie value -- you have it right there.

You need to associate the value with the lead, which is where you'd use the REST API Associate Lead or loopback form post from a webhook.

[Nina_Gonzalez1]

Sanford, Geoff and I are working on this together. Can you clarify what you mean by "you have it right there." What is the best method for attach the Munchkin _mkto_trk value to the SFDC record? Thanks for your help.

[SanfordWhiteman]

You store the cookie value in a hidden field on the SFDC form. That field is synced with Marketo. When the lead enters Marketo (and/or the field changes) you use a webhook to associate the lead with their cookie.

[Nina_Gonzalez1]

Excellent, that makes sense.