Alex_Stanton1

I like the fact that lead assignment can also be triggered in Mkto. I needed to put leads through a round robin only under certain circumstances and Mkto gave me that flexibility - I set up a two-tier round robin in Mkto (two separate triggered campaigns based on two sets of actions) and it is work...

Are you looking at setting up three models?

Heather, note that an SFDC queue will work fine if the records you send to it are SFDC Leads. If Marketo sends an already existing SFDC Contact to a queue, SFDC will create a new lead, hence a duplicate.

I tend to favor syncing all leads to SFDC (and it also helps preventing duplicates). When I sync pre-MQL records to SFDC I try to assign to a non-sales user that owns them until they MQL. Do you have a full lead lifecycle (with model) set up?

I would open a case on this one - it looks like something going on in the back end.

Did you set them up as a string type field?

I agree with Sanford. I would use an email script token. Here is how to create one: Create an Email Script Token - Marketo Docs - Product Docs

I would confirm this with support, but I have the feeling that since the standard object is called "Lead" calling the custom one "Lead" as well will create a problem.

Just a hunch, but did you name the custom object "lead"? If so, I would rename it to something that will not confuse Marketo. It has been my experience with fields that the naming itself can create a problem.