david-zweben

Hello,   I'm trying to set up a Smart Program that logs a change history of one of our fields into a text area field. The program is set up like this:   Smart List: Trigger when "Person Status" data value changes Flow: Change data value "Person Status History" to {{lead.Person Status History}}{{my.linebreak}}{{system.dateTime}} - {{lead.Lead Status}}   This is intended to append a new line that looks like this: 03/04/2022 8:45 AM - New Lead Status Here   Appending a value works as expected, the only problem is that the value that gets appended is the previous value, not the new one.   How can I set up this type of logging functionality and be sure to capture the just updated value of a field, rather than its old value? I'm pretty sure this is an issue with things happening asynchronously, but I don't know how to prevent it.   Thanks! ... View more

We're running a drip program in Marketo, and a handful of our own employees have signed up and become leads, probably to see the deliverables. We want to make sure the way we're treating these is in-line with best practices. We can see a few potential approaches:   Treat them like any other lead; let them sync to our CRM if they qualify, and Sales can classify them as a dead lead Create a new lead status specifically for this case, such as “Internal”, that they would hit instead of qualifying Block these people from entering our programs and lead list entirely Allow these people into our programs, but block them from becoming qualified leads Create a separate custom field on Leads that indicates this type of person, e.g. “Is Internal” and use that to prevent CRM sync   In terms of best-practices, what would be the best way to handle this?   Thanks, David ... View more

Hello. We have an ongoing program with a Smart Campaign that consists mostly of email blasts spaced apart with wait steps. By necessity, we've had to build out this program while it was live, meaning some members hit the end at email 1, some hit the end at email 2, etc. We now have most of the emails on there, but we're left with many members who hit the end of the program in a previous state, and did not get the emails we added later.   What's the best way to handle this now? We thought about resetting them to the beginning of the campaign via "request campaign", but it doesn't seem like we can skip the wait steps that shouldn't apply again. The only other thing we can think of is doing separate manual sends of each email, to the members who joined while the program was being built. Is there a better, more automated way to clean things up here to make sure everyone gets every email? Preferably they'd also get any future steps we add to the campaign automatically.   Thanks, David ... View more