We are seeing inferred data populate sometimes and sometimes not via the Web Service API. I've heard that inferred data populates on the second page hit? Is this true? If no inferred data is being populated does that mean that my leads are converting on their first visit? Is there any change we can make to settings so that inferred data is captured all the time?
Inferred data is captured the first time a lead encounters a munchkin tracked page. This data is currently saved in an anonymous record in your database, and when the lead becomes known that information is placed in the known record as well. This process depends on the lead using the same browser, and therefore having the same cookie throughout.
If leads are being created through the api, and are not getting associated with the previously tracked anonymous record through the cookie in their browser, then some records may not have inferred data upon becoming known. You'll want to be sure whoever set up your api calls is using the associateLead call.
Thanks for that explanation. I'll double check with my web developer to make sure she is using that associateLead call.
Hi John -
My web developer confirmed we use SyncLead API call for everything. Does that have the same function as the AssociateLead API call you suggested? Or could this be why a lead is not being associated with the anonymous record?
We have a similar question - we are using REST API to capture data with munchkin tracking on those pages. Currently we are using the create/update lead call. If we switch to the associate lead call, will it still create new leads? Or could we use both call types?
Any ideas, Sanford Whiteman?
Why would you expose your REST API call limit to abuse by malicious web users? There's basically never a reason to have every form post result in a REST API call.
If you switch to Munchkin associateLead, yes, it will both create and update leads.
Thanks Sanford. We've been OK limit wise, but do you have any other recommendations for capturing data from an external form? Currently, switching to or embedding a Marketo form isn't an option, so we're using REST.
Best practice is to use either a visible Marketo form or use the Forms 2.0 API to submit data from a 3rd-party form.
If you're trying to filter on this data upon lead creation, it will be hit or miss. The inferred data is populated asynchronously, so there's no guarantee that it will be available upon creation. You'll want to setup a wait step and check about 5 minutes after creation instead of at creation.