SOLVED

Re: Inferred Fields in Activity Log?

Go to solution
Anonymous
Not applicable

Inferred Fields in Activity Log?

Hello everyone,

We have started routing leads that come into our database by Inferred State Region. While most leads have a value for this field, there doesn't seem to be a record of when the lead acquired the field in a lead's Activity Log. Is there a way to see the timestamp for when leads acquire Inferred field data?

This data is relevant because we will use it to adjust our routing, depending on when the Inferred fields are established.

Thank you,

Dan

1 ACCEPTED SOLUTION

Accepted Solutions
Grégoire_Miche2
Level 10

Re: Inferred Fields in Activity Log?

Hi Dan,

This information is logged when the Marketo cookie is placed and the anonymous lead is created in the DB. There is NO "data value change" event posted to the activity log when a lead is created as anonymous, and neither is there any when the lead is "promoted" to a known lead.

You will have to use the "created" datetime field, I am afraid. The drawback is that if the lead is created first from the CRM and comes later on your web site, the created date might be much earlier than the date at which the inferred data was captured.

-Greg

View solution in original post

2 REPLIES 2
Grégoire_Miche2
Level 10

Re: Inferred Fields in Activity Log?

Hi Dan,

This information is logged when the Marketo cookie is placed and the anonymous lead is created in the DB. There is NO "data value change" event posted to the activity log when a lead is created as anonymous, and neither is there any when the lead is "promoted" to a known lead.

You will have to use the "created" datetime field, I am afraid. The drawback is that if the lead is created first from the CRM and comes later on your web site, the created date might be much earlier than the date at which the inferred data was captured.

-Greg

SanfordWhiteman
Level 10 - Community Moderator

Re: Inferred Fields in Activity Log?

Yeah -- getting the datetime is possible by interrogating the `cookies` field via API (easier than the ActLog as a whole) -- but don't do this, you can't afford the API calls.