Dave_Cunningham

This thread should provide you some helpful direction.Event scheduler in Marketo

One thing you might want to check is if you have another channel set up for mobile check ins. I recall running into an issue where I had one channel using it and then was trying to set up another, but it caused some issues.

We have a bunch of custom objects in our Microsoft Dynamics instance and the only way we have been able to use them as tokens in a Marketo email is by setting up program script tokens that use velocity script to reference the custom objects. It's a bit cumbersome, but it works. Perhaps there is a be...

That is good to know, Brian. That's what I have seen in my testing, but I was never able to get a "confirmation" on this behavior from Marketo... until now .I am running into an issue related to our field mapping for Company. The way it was set up when we synced Dynamics/Marketo is shown in the belo...

Dan is right. The Marketo/Dynamics sync has a big weakness in that MSI is the only way to expose lead's Marketo activity in Dynamics. We would love to be able to sync the individual activities back to Dynamics (email clicks, event attends, web page views, etc.) so that they can be both viewed on the...

Yes, makes sense. I was asking for the trigger / wait step scenario. Just interested to know how Marketo queues things up.

I probably should have been clearer on what I am trying to do. The program I am creating will be a template that all webinar programs will be cloned from. I am trying to limit, as much as possible, what the webinar team needs to touch. However, having to schedule a batch reminder might end up being ...

Thanks Devraj. We're trying to automate as much as possible so would like to avoid batch. You bring up a great point though with the long wait step. I sometimes overlook this. What I'm testing with here is a trigger on the program status changing to "Registered". There could be days/weeks between wh...

Thanks Dan. Just shared it using the "Share" option to the right of the page.