JD_Nelson

@SanfordWhiteman wrote:there's a tricky way still keeping that blog post close to the vest, eh?

I would recommend dynamic content, specifically Snippets. That way you can swap out content without editing all the different places that reference it. I've found that reporting on this becomes a bit of a downer, so you may want to setup some tagging when the email is sent in order to set a way to t...

not really.... although @SanfordWhiteman has teased a very complex scripted way to accomplish something similar a while back, but I have yet to see any reference to a way to do this successfully. More than happy to be proven wrong, but .... A possible work-around I've had, in the Email editor, is to...

I've started implementing point-in-time values, which would be similar to the use-case for querystring capture, but I'm doing it more from a lifecycle stamp period. For instance, what programs did someone attend as a Prospect (or MQL) vs. as a Customer. You can start to get a feel for resonance of c...

you've summarized the questions everyone has, pretty well. Unfortunately, no, there isn't a default way to sync to SFDC and a Campaign at the same time all while waiting for x-number of processes to run through your lifecycle. The normal way to do it is to have the Sync to SFDC flow step in your glo...

this is a common reason why people don't use the sync and prefer to make it a local action to the program and rely on a global lead lifecycle for all the processing. The problem with that being that you'd have a wait step in every campaign of undetermined length (your lifecycle time). It is an Idea ...

are you seeing the click activity for the lead that was sent the first stream email?

Probably a little late for you, but it does look as though the original email would still be sent. Once the send is initiated everything is placed, ultimately, into an Outbox if you will. It should also be noted that the time of the actual SEND (as opposed to the delivery, hour later) will be used i...

It's a bit difficult to visualize, but I think I may have done something similar, before. Ultimately, I found that it was better to do it all in one engagement program and simply manage the streams like you would your batch triggers. The assumption here is that your "irregular send times" could be a...