Currently if a email recipient forwards that email to a peer, their lead information goes with it. I'd like to see this fixed - lead information should not go along with the email.
@Cheryl - Yes, absolutely. In fact, we had both this (the social sharing feature) and the "forward to a friend" feature as part of our prior email service provider (Campaign Monitor - which isn't even an enterprise-level platform like Marketo is). Now that we've migrated to Marketo, we're anxiously awaiting to have this functionality again. BTW, with the forward-to-a-friend feature, all links within the forwarded email were modified on the fly to contain unique tracking code based on the recipient of the email. And the reporting showed us who forwarded emails to friends (but didn't show us who those people were due to privacy laws).
We're also very interested in seeing Forward to A Friend functionality. We've used this heavily in Eloqua as a core feature. The social sharing within an email would also be great to have but not quite as important to us.
Will I be able to add this "forward to a friend" Link to an article within my newslettter and not just the entire newsletter? If I just wanted to share(forward) a particular section of the newsletter, is that being considered?
The Forward to a Friend was a part of of our old maketing system EmailNow and the lead info did not go with it, so not sure Glen, what you mean by this.....
"Unfortunately, the way all of the world's email works is that once an email is sent, the sender no longer has no control over the content.
I'm with Todd on this one! It's be really great to have a "Refer a Colleague" functionality that allows the recipient to enter a colleague's name and email address.
This could then trigger an email to the colleague referencing the referrer and containing details about whatever they are being referred to.
Is there a possible timeline on this? I have a campaign that hinges on sharing!!
We struggle constantly with records being overwritten when people forward emails to colleagues. I think most users don't have any idea how often this is happening. I've used systems on the past - MarketFirst for example - where we had a trigger built into each form/LP "If the information below is not yours, please click here to clear the form" - which effectively blew out the stored cookie data and allowed the user to register as a new record. I think this type of functionality woudl go a long way to curbing data getting overwritten in these circumstances...
We struggle constantly with records being overwritten when people forward emails to colleagues. I think most users don't have any idea how often this is happening. I've used systems on the past - MarketFirst for example - where we had a trigger built into each form/LP "If the information below is not yours, please click here to clear the form" - which effectively blew out the stored cookie data and allowed the user to register as a new record. I think this type of functionality woudl go a long way to curbing data getting overwritten in these circumstances...
.png)