Build better products with our product team
As many know, but some may not, some email servers produced an email is delivered code, then subsequently reject the email and it get marked as both delivered and bounced i nthe Marketo activity log for that lead. It is documented and discussed here:Under what circumstances can an email be delivered and bounced?These emails will not have actually made it to the customer, so all analytics reports are inaccurate and also using the 'email is delivered' filter is inaccurate.This idea is for Marketo to retroactively go back to the activity log and remove 'email is delivered' if the email in fact bounced.
Hi,Since the introduction of the email send campaign we've been using it a lot. Mostly to send invitation and reminder emails for the simpler batch and blast campaigns.One of the troubles we're having is with the random samples not being available in the email send campaign. Metering a campaign by spreading it out over 10 weeks requires us to have 10 email send campaigns within a bigger campaign. However, there's no way to (easily) split the audience over the 10 email send campaigns other than generating 10 static lists or 19 smart lists.The way we would like to do it is by adding let's say 2000 people to the parent campaign and sending to a random sample. Once an email is delivered we would change the membership status of the Email Send Campaign and the Parent Campaign. Rinse repeat the next week.As we're able to leverage the 'Random Sample' filter in a Smart List, why can't we use this in an Email Send smart list? Sounds straight forward enough.Thanks,Stijn
It would be great if we could activate or deactivate a smart campaign by simply right clicking the same way we approve/unapprove assets.
Allow for SFDC Campaign tokens to be used in the "Added to SFDC Campaign" trigger within a smart list. Currently it doesn't accept the token, even though most all other flow step actions having to do with SFDC campaigns do accept the token type.
Hi Marketo team,would be nice if in the transition rules of the engagement programs we could use advanced filter logic, with AND/OR conditions.We are aware of the current workarounds available, but using advanced logic in the transition rules themselves would make it easier for the user to follow up on all filter criteria details.Many t !hanks,Stilyana
It would be awesome to have SF user profile information available as tokens for MSI emails. This would allow us to dynamically populate a signature based on who is sending the email, the same way SF templates do.Many sales teams have multiple sales reps that handle a single lead/contact, so using the Lead Owner/Contact Owner, or any other custom field that contains a point of contact, doesn't provide a fail-safe way of populating a signature in MSI emails.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.