Badges
Accepted Solutions
Likes Received
Posts
Discussions
Ideas
Blog Posts
Yes, I would agree with Greg above, did you upgrade to Email Editor 2.0? If not, it doesn't look like those are valid HTML comments, which could be causing the issue. Valid HTML comments are structured like But that doesn't explain why this is suddenly showing up, unless it's because your team swit...
I tried uninstalling and reinstalling and it didn't work! How strange! You can upvote my idea here: And maybe someone will comment and let us know that there is a (non-intuitive) way to accomplish this.
When you swipe left to dismiss a card, there is no way (that I can see) to recover it. I tried logging out and logging back in, force closing and reopening, and even uninstalling and reinstalling the app. This is a critical missing feature because it is easy to accidentally swipe left on a card. And...
Yeah I definitely agree. If you go to the menu and then the "Done" section, does it show up there?
Have you tried closing and reopening the app? Last ditch effort you could delete the app and reinstall.
You could edit the Block Field Updates from the unsubscribe to block updates from Salesforce. But then sales people wouldn't be able to unsubscribe people manually, so that could cause a separate problem.
Can you share a screenshot of their activity log? Also have you opened a support case?
I just came back to say the same thing as Michael! If you're using Email Editor 2.0, this could be the problem: Email Editor 2.0 lets trigger based emails soft bounce
James is right. You can also use a segmentation. We have a database segmentation for "Marketable" leads that I use to exclude anyone who has unsubscribed, bounced, is a competitor, or doesn't meet our buyer requirements. I also have some lists that I have received to upload that Sales does not want ...
Soft bounces are very tricky. It's because of a server rejection of the email so it may soft bounce sometimes and not others, which is why Marketo doesn't automatically mark your email as "Email Invalid" because of a soft bounce. The batch vs. trigger has nothing to do with it. Correlation not causa...