Associating Annoymous behavior with SFDC Contact

Highlighted
Level 1

Associating Annoymous behavior with SFDC Contact

As users signup for a trial of our site we will be adding them to SFDC first:  As some need to be added as Contacts and some as Leads.  

We will then sync these users to Marketo.   Is there a way through the munchkin API to get the anonymous
ID, pass it to SFDC when the account is created,  then sync to Marketo passing a munchkin UID so that when the person record is created in Marketo it can recognize it as a known user and then associate it with the past activity?  #munchkin code#munchkin api#munchkinid

6 REPLIES 6
Highlighted
Level 10 - Community Moderator

Re: Associating Annoymous behavior with SFDC Contact

This will not happen automatically. You're on the right track, though.

You don't use the Munchkin API at all. You only need the Munchkin cookie (_mkto_trk). Post that as a hidden field to SFDC. Let it sync to Marketo. Once in Marketo, send a webhook to the loopback forms endpoint, including the cookie. Search for "loopback form post" and there are several threads on this.

Highlighted

Re: Associating Annoymous behavior with SFDC Contact

I have used the "loopback form post" since 2011 so it definitely works. On the bottom of this article is a screenshot with an example: https://nation.marketo.com/thread/26442

However, it is also fair to note that it has never been supported, so if you have any issues/questions, Marketo Support will not be able to help. Also, if the data center setup ever changes, it may stop working.

Alternatively, you can use the "Associate Lead" REST API, which is also a valid solution, but it would require the development of a "Proxy": the Webhook calls the Proxy, which then calls the Marketo REST API to do the association. 

Highlighted
Level 10 - Community Moderator

Re: Associating Annoymous behavior with SFDC Contact

Alternatively, you can use the "Associate Lead" REST API, which is also a valid solution, but it would require the development of a "Proxy": the Webhook calls the Proxy, which then calls the Marketo REST API to do the association. 

And has a DoS vulnerability because rarely if ever do people throttle the rate of intake through the SFDC form (thinking they have the headroom on the SFDC side).

Of course if you use an API gateway you can also use an alternative API authorization mechanism, which is what we do to keep API users below a certain # of calls per day. Rather brute-force, though.

Highlighted

Re: Associating Annoymous behavior with SFDC Contact

Yes, that's a valid concern. "loopback form post" is limited to 30 calls per minute, so that is being throttled also. I often use AWS API Gateway, which has an easy way to authorize and throttle calls, probably similar to what you are doing. 

Highlighted
Level 10 - Community Moderator

Re: Associating Annoymous behavior with SFDC Contact

I often use AWS API Gateway, which has an easy way to authorize and throttle calls, probably similar to what you are doing. 

Exactly what I'm doing.

We have a new policy, too, of validating against JSON Schema before hitting Marketo. It's been really handy when dealing with distributed teams, being able to say "just look at this JSON Schema, you don't even have to look at the Marketo docs".

Highlighted
Level 1

Re: Associating Annoymous behavior with SFDC Contact

Thank you, will have the team give this a shot in the next week or so and will post back the results.  Really appreaciate the insight and quick response.