Darshil_Shah1

Thank you, Sandy! I think indexOf("expression") would be a better alternative then! 🙂

You can deploy custom a form JS to accomplish this. Below is the sample code FYR. Hope this helps.

We implemented something similar for one of our clients recently where we created duplicate lead records when corresponding contact record hit the QL stage, instead of relying on Marketo to create/update the duplicate lead records, we used a third party service to facilitate the sync and ensure that...

With emails being the prime content of your Engagement program, you can probably use custom tokens extensively in your emails for all the dynamic/editable fields. Upon cloning this EP, all of your tokenized emails within the program will be cloned, and later you can go on and update the email conten...

Off the top of my head, here's what you can do -Create a custom text {{my.passcode}} token local to your program (add a placeholder default value as the token value).Create an email, plug the {{my.passcode}} token where you want to display the passcode in the email.Create a trigger campaign with Cam...

Great post, thank you @Jacqueline_Hess! It would be great if instead of overwriting the reason field for every soft bounce if we build a history of soft bounces along with date stamps in a text area field. That way we would have entire log of soft bounce reason along with the respective date stamps ...

Hey @dcreagh,The update smart campaign endpoint let's you update name and/or description of the smart campaign. There's a campaign schedule endpoint that let's you schedule the smart campaigns to run either immediately or at a future date. Do note that this is a only one time batch run and not the s...

@fishmatt33 As of now the process of running the application is not automated, but certainly a cron job can be setup for the same to automate the exporting the data out of marketo and importing in to Analytics without much effort. Also the application can be run based on the requirement and volume o...

Yes, You're absolutely correct @SanfordWhiteman! Thanks 🙂