Re-sending Part of a Nurturing Stream | Community
Skip to main content
Joe_Reitz
Joe_Reitz
Level 8
February 24, 2015
Question

Re-sending Part of a Nurturing Stream

  • February 24, 2015
  • 3 replies
  • 1040 views
Hi all,

I'm wondering what the best practice is to share existing content that may have been sent 3 or 4 "touches" ago (i.e., in a nurturing stream). I have an email that I'm planning on sending early on in the stream, and then another a few months/emails later that will further expand the story. In that amount of time, I'm counting on the reader to have already deleted (or maybe forgotten) about the first email that touched on the subject matter, so I want to  provide a button or link in the second email that would re-send them the original info.

Is this possible, or is there a simple way to convert an old email into a new landing page?
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

3 replies

A
Anonymous
February 24, 2015
There's no push-button way to convert an email into a landing page, but you could convert the content over fairly easily I would think. 

If you wanted to allow the leads to trigger re-sending the original email to themselves, you could have a separate triggered smart campaign listening for that click in the email. The flow of that smart campaign would re-send the email. 
    A
    Anonymous
    February 24, 2015
    I'm also thinking - what about the "View this Email as a Webpage" link?  We don't use it, but perhaps there's a way that link could be preserved and linked to in your new email?  Just a thought, might be worth exploring.
    Joe_Reitz
    Joe_ReitzAuthor
    Level 8
    February 24, 2015
    Justin- THANKS! I think the smart campaign trigger will work well.

    Laura- I had that same thought too, but isn't the link unique to each recipient? For some reason, I have it in my head that that could throw off our reporting in SFDC...
    If it doesn't look cool, you're probably doing it wrong.
    Terms & ConditionsAccessibility statement

    Loading footer...