Is there a way, using a Smart Campaign to take some information from one lead's record and put the same information into another lead's record?
Some context: we currently have each of our sales representatives in our database. In each rep's record is their full name, a link to their photo and their rep code. In each of our customers' records, we only have their rep's code (that rep who sold to them). Is there a way to populate the customer's record with the rep's information into the correct, already-created rep info fields? We have over 120 reps, and would like the easiest, most efficient way of doing this.
generally no. If you want to do something like this, I'd suggest programming it into apex code or a formula field in SFDC.
Could you not just export the list, update the information in Excel, and then re-import?
Our objective is to have this happen as new customers are added to the database without having to manually make the changes, which would be a lot of manual work. It would also be ongoing, so exporting and importing is not ideal. Thanks for the suggestion though!
You could check out CALCITNOW - Field formula calculations – Marketo LaunchPoint
Perhaps this will help you,
You can upload all your reps' data into a Marketo custom object. Using the rep code, you can tie the rep information to the customer record in Marketo. Whenever you want to send an email with that information, you can pull the field into the email using the Email Script token.
Much like any other field on the lead record, you can use smart list filters to query customers by rep information as well. The only downside is if you rep details are constantly changing, you would need someone to upload the spreadsheet into the custom object (see here: Import Custom Object Data - Marketo Docs - Product Docs ) but you can automate this process pretty easily if you have an API developer.
We have something like this running on a daily batch program in Data Management folder.
If DV Rep XYZ (in field Rep Code) change DV Rep Mobile to 0123456789, change DV Rep Name to Mr Black, and so on.
If DV Rep ABC (in field Rep) change DV Rep Mobile to 1111111111 etc etc
In this way we can avoid all 'complications' of API/Custom Objects etc and it's easy to make a global change to any details such as a change of Rep phone number etc.
Hope this helps.
Sarah, while I def'ly agree this is the right approach for small data dictionaries, it breaks down when you have large and complex search and replace tasks.
It's true, though, that literally pulling data from one lead's custom fields and putting it into another -- in triggered/near-real-time -- isn't possible at scale because of API limitations. So you either need to use some kind of external database+app to "bulkify" this task, or store the lookup map outside of a single lead (for example, in a webhook descriptor, or in a dictionary field on *every* lead that can be used in remote webservice lookups, or in a my.token).
If you still looking to automate this, check out
You can use a variation of the following webhook from this Web Hook Library
This is kind the 'webhook descriptor' Sanford mentions.