This content has been marked as final. Show 5 replies
Marketo architecture thinks in terms of people. Is there a field on the lead or contact layout that determines expiration? You may need to map this data from the account to the appropriate lead or contact. Marketo will see the data value change here and you can trigger off of it.
Thanks for your response. Yes, I do a field on the lead/person account which is called "Lease end date". Issue is I'm struggling to querry this on a dynamic ongoing basis. The campaign I'm trying to create is - 90 days prior to end of a car lease, I want to a new lead for that person and then send email campaign to renew or take up a new lease.
I can create a smart list with a static date but not pass on a dynamic date field.
You should be able to see the data value change down in Marketo when this field value hits 90 days on the next update sync. At this point you can request the engagement program you have built around renew.
Have you tried creating an aging formula field in SFDC based on a lease end date - today's date = 90 days calculation? You could then pass that value to Marketo so you can use as a smarlist filter on your campaign or use a Data Value Change trigger and check for that value = 90. When the condition is true -value of the custom aging field reaches 90- then send the email, etc. Just a thought.
The only problem with formula fields is it doesn't updat the last modified date in SFDC thus it wouldn't send this data through to Marketo. If you have formulas like the above where the date would be changing every day (like a formula), you'd have to use a SFDC trigger to push the update through to Marketo on a batch. To prevent a huge data load pushing through the API you'd set up the filter to only trigger on those records who fit the above criteria.