Right now we are setting up a campaign that sends out an alert to a homebuyer's real estate agent (the homebuyer is the lead, the real estate agent is an email address field we created on the buyer's lead card called 'realtor_email') when they reach a certain part of their homebuying journey. Seeing as a single real estate agent may be attached to multiple buyers in our system, we want to limit the number of times that the email address in the field realtor_email can be sent this particular message (essentially once per 6 months).
We currently do not want to make the addresses in realtor_email individual leads, as we already have too many leads in our system (these agents are contacts in CRM however).
This is the sort of logic we want to set up:
"if {{lead.realtor_email}} was sent alert (x) in last 6 months, do nothing"
Is there anyway to track whether or not the email addresses in 'realtor_email' were sent an alert, and reference those emails in a smart list (without creating new leads for the agents)?
Hi Patrick,
This would be possible using 2 webhooks:
The difficulty you would have is that web services are not "synchronous", so Marketo does not wait for the answer to continue the flow (see Are webhooks synchronous?). You will need to add a few minutes wait between the second webhook call and testing the result.
This will take some APEX development in SFDC to develop the web services.
And you may want to vote here :
-Greg
Thank you so much!
Unfortunately we use microsoft dynamics, would a similar solution be available for that CRM tool?
Hi Patrick,
I am not an expert on MSD Development, but I am quite sure the same kind of web service development should be possible. A key point will be to make them accessible from Marketo if you have an on premise instance. With a cloud instance, that should be really feasible.
-Greg
The difficulty you would have is that web services are not "synchronous", so Marketo does not wait for the answer to continue the flow (see Are webhooks synchronous?). You will need to add a few minutes wait between the second webhook call and testing the result.
I'd trigger on the Data Value Changed event, not rather than using a wait step.