Email address is the only criteria in that smart list out of the box. You remembered it correctly.  ... View more

Hi, I'm assuming you are using Salesforce as your CRM so I would recommend doing this workflow through Salesforce. My company is also B2B and do most opp/product workflows off of the account and not the contact record so we definitely have most of our automated tasks set the way you want - for instance, if an opportunity isn't touched for a certain amount of time, it generates a task for the sales owner to reach out to the account (the sales team can decide who is best to contact).  Your SFDC admin should be able to set this up for you. ... View more

Hi Nate, This suggestion won't necessarily help with the exact internal mapping of Marketo but if you're looking to massage the data in Tableau, you may want to look at the Bulk Extraction options from Marketo.  This post is bit dated but might prove helpful with some information to consider: If you use Tableau to analyze your Marketo data, look here There is also this architecture document from Marketo Documentation site: http://developers.marketo.com/support/Marketo_DB_Reference_Architecture.pdf ... View more

Just spit balling an idea here: When you say SFDC Leads Only - do you mean that the lead should never make it's way to Marketo (basically, an unmarketable lead)? I ask b/c if you have a set group of emails that you know shouldn't sync, then you could create a smart campaign that listens for a new person to be created AND has the email address of a person you don't want to sync (this would require you to set up a smart list of the emails you don't want in the system), and then have the flow step delete that person (I believe this will beat the sync time to SFDC, but you'd need to test it for sure) BUT it does mean you would be deleting that person from Marketo as well. You could also use a similar method of performing a what/if flow criteria on any new person created, same idea - if the new person created has an email address that "does not" match anyone on your "no list", then sync using __whatever rule you have__ (could be auto assignment, depends on your business); additionally, remove the default choice so it says "do nothing" when a person does match to your "no list".  That should make it so that only people not on your "no list" should be syncing to SFDC. Again, just spit balling, I haven't tested these methods but I often have to create workarounds for similar issues, so I hope these ideas prove helpful to you. ... View more

Thanks Josh - I have a pretty good template going that can be used each day with little modification (but I'll definitely look into snippets for it ) but I'm more concerned with having to set up a new program (clone the program) every day to distribute the newsletter. I toyed with the idea of using a nurture campaign so that I'm only adding assets to the stream but I'm hoping there's a more elegant solution so that my teammate only needs to worry about cloning email templates and not the entire program. Especially since I need her to set it up a week in advance and not on the daily. ... View more