Capturing Lead to Opps conversion date. | Community
Skip to main content
A
Anonymous
July 8, 2013
Solved

Capturing Lead to Opps conversion date.

  • July 8, 2013
  • 4 replies
  • 1340 views
All, 

I wonder if there's an easy way to capture the lead to Opps conversion date? My Marketo and SFDC instances are synced such that when a lead is converted into an opp, that information can be seen under the Opportunity Section of the lead. Still I struggle to report on that data at a granular level (lead by lead). Thank you for your help! 

Cheers,

Gio
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
I see your point. You could create two custom fields, one just for the conversion and one for the Opportunity: Converted Date and Added to Opportunity Date. You could do this within the same campaign. The trigger would remain the same, the flow steps would change. I would start with a wait step of 2 minutes because Mkto can struggle with timing if a Lead is converted and an Opportunity is created at the same time. Then, the next step would be change data value of Converted Date to the current date with {{system.DateTime}}. Then add another flow step of Change Data Value with a choice. For Choice 1, "If Has Opportunity TRUE," then "Attribute: Added to Opportunity Date is {{system.DateTime}}". If you have a Lead where these dates match, then you know it was converted with an Opportunity. If they don't, then they were just converted. 

You can create more data management campaigns that add a date when they are added to an Opportunity (opposed to creating one upon conversion). Then, you can null that value out when the Opportunity stage is changed to anything that implies that the Opportunity is closed (Won, Lost, Project Gone/Changed, etc.).

4 replies

A
Anonymous
July 8, 2013
Hey Gio,

I would create a custom field called "Converted Date" within Mkto. Then set up a simple campaign that has "Lead is Converted" as the trigger and in the flow steps use "Change Data Value" to change the value of your new "Converted Date" field to the current date by utilizing the system date token: {{system.Date}}
A
Anonymous
July 8, 2013
Jeff, thanks for your prompt follow up. This only captures when the lead is converted. What if it is converted into an Account and  contact vs. an Opp? How do I distinguish between the two? Any tips?
A
Anonymous
Accepted solution
July 8, 2013
I see your point. You could create two custom fields, one just for the conversion and one for the Opportunity: Converted Date and Added to Opportunity Date. You could do this within the same campaign. The trigger would remain the same, the flow steps would change. I would start with a wait step of 2 minutes because Mkto can struggle with timing if a Lead is converted and an Opportunity is created at the same time. Then, the next step would be change data value of Converted Date to the current date with {{system.DateTime}}. Then add another flow step of Change Data Value with a choice. For Choice 1, "If Has Opportunity TRUE," then "Attribute: Added to Opportunity Date is {{system.DateTime}}". If you have a Lead where these dates match, then you know it was converted with an Opportunity. If they don't, then they were just converted. 

You can create more data management campaigns that add a date when they are added to an Opportunity (opposed to creating one upon conversion). Then, you can null that value out when the Opportunity stage is changed to anything that implies that the Opportunity is closed (Won, Lost, Project Gone/Changed, etc.).
A
Anonymous
July 8, 2013
Thanks Jeff!!
Terms & ConditionsAccessibility statement

Loading footer...