I am trying to create a program that anytime a lead is created in Marketo it is assigned to a rep in salesforce based on state.
I have the following set up, but while it creates the lead in salesforce it is not assigning it to the correct rep.
What am I doing wrong?
Who do the leads get assigned to? Someone you specified in your smart campaign or some else altogether?
Hard to say what exactly throws the assignment off from the info you provided, but here are a few things to consider:
1. Data standardization - Do you have your state names standardized on all your forms?
For your set up to work all your incoming leads must have state name in the 2 letter format; let's say if a lead has "Pennsylvania" as a state instead of "PA", none of your constraints will apply and this lead will get assigned to whoever you have in the default choice.
2. Lead assignment rules in SFDC - check what you have on SFDC side
It is usually a better practice to set up lead assignment rules in the SFDC, so that no matter how leads get into your CRM they all run through the same assignment process
You need to use IS,
CONTAINS is going to screw it up.
+1 for "Is" instead of "contains". If necessary revisit your forms to make sure that the "state" picklist is correctly configured to store the 2 letters acronyms for states.
You can also run data quality smart campaigns that fix the values and have you smart campaign above to react also on "change data value" on the state field.
-Greg
To avoid complications, you can configure your assignment rules in salesforce and sync your leads using auto-assignment rules.You can configure this in salesforce setup area. In the search bar, type Lead assignment rules and make the necessary changes there.
And the "contains" has to be changed to "is"
On your marketo system, you can create a trigger that assigns the right state codes to different states so that you are pushing the right codes to salesforce when you sync. I really hope this helps.
I agree. It wouldn't work for already existing leads. Thanks Greg
Hi Kenneth,
If you read the comments in the idea, you will see that we have a workaround, though.
-Greg