Inferred Data - How and When is it captured? | Community
Skip to main content
December 21, 2015
Solved

Inferred Data - How and When is it captured?

  • December 21, 2015
  • 2 replies
  • 7542 views

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?

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 JohnCl9

Hi Shirleen,

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.

John

2 replies

JohnCl9Adobe EmployeeAccepted solution
Adobe Employee
December 21, 2015

Hi Shirleen,

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.

John

December 21, 2015

Hi John,

Thanks for that explanation. I'll double check with my web developer to make sure she is using that associateLead call.

Kenny_Elkington
Adobe Employee
Adobe Employee
December 21, 2015

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.

December 21, 2015

Hi Kenny,

Are you suggesting setting up that wait step in our lead is created smart campaign? Or in our Sync to SFDC smart campaign?

Kenny_Elkington
Adobe Employee
Adobe Employee
December 21, 2015

Hi Shirleen,

This usually just affects lead is created campaigns, but it depends on which campaigns are checking the values, so I can't really answer that in the abstract.