David_Gallaghe2

I believe in both go to webinar and webex it is Registration Error – but you may want to double check with GTW...

I set up a 3 minute wait step and in the event it came back as an error, I sent the confirmation only to those that had the status "registered", Those that were not "Registered," including "Registration Errors" were dropped on a static list tied to a trigger campaign that waited another 15 minutes ...

I had a huge issue recently where my sfdc api calls from marketo tripled in one day. It turned out it was due to a few in-line flow sync steps across a number of programs. The solution was oddly simple duplicate the program and for events just add an event asset insite the event... check out my repl...

You can sync based on member status, but it involves just a little work...Clone and create your program and end the name with " -- MKTO". Let's use the following as an example:-> Program Type = Event-> Channel = Live EventCreate a second program with the same Type, Channel and Name. I suggest ending...

I am really confused here. I was implementing a token strategy before Summit this year – (while I may be going nuts and likely am) I swear I was able to able to delete overridden tokens which would restore them to the inherited/parent value. Was there an unannounced beta that my instance was apart ...

Running our live test for a webinar next week -- all looks good so far. Press those thumbs and cross them fingers...

I'm planning on running an all new webinar program next month -- all internal tests look good across domains, and no reg errors reported to date... but we will see what happens with the initial run. I have a gut suspicion that there may be something on the client side that may be stripping the url #...

Yup -- both... even with wait steps... was really bizzarre. I had experienced this webex then it magically disapeared then reared up again when I started using GtW...

If you are working with invite lists, you can create sub email programs within your event, webinar and default programs.I leverage these for that exact reason... since technically these invitees are not in the parent program -- which could be in a syncopated rhythm with salesforce, you know turning ...

All emails are batch and blast (not email program nested).I leave a 2 minute wait step in there before sending confirmation emails and have an added constraint to only send confirmation emails to "registered" participants.Registration errors are run through an additional wait step (30 minutes) and ...