Best practices for managing additional lead owners and lead owner data | Community
Skip to main content
M
MichelleMc11
Level 2
December 8, 2017
Question

Best practices for managing additional lead owners and lead owner data

  • December 8, 2017
  • 2 replies
  • 3915 views

We have several different types of Sales Owners (Lead Owners, Regional Managers, Inside Sales etc.) some of these are available in Salesforce and some are not. We also have a need to capture additional information like Headshot, social handles, etc. to be used in email signatures that are specific to Marketo and not in Salesforce. Our current process is to create custom fields for the information we need and then create a workflow for every "owner" to populate that data. This method works fine if it’s just a handful of owners, but its not very efficient if there are more than that. We have tried creating Marketo custom objects to hold the data we need, but that limits the way we can use it in tokens and on the email (without velocity script). Has anyone figured out a better way to manage this or is there a way to simply update the custom field on the lead record with data from the custom object?

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

    2 replies

    Josh_Hill13
    Josh_Hill13
    Level 10
    December 8, 2017

    You would need a set of fields on both (ideally) systems to manage this. Most solutions for signatures involve snippets and/or tokens based on the fields attached to the Lead/Contact/Account. I haven't seen a Custom Object in Marketo to handle this, but you could do so.

    I guess what I'm asking is Why do you say this is a problem and what do you mean by setting up a "workflow" for every owner? Can you describe more about what you are doing for each type of Owner?

    SanfordWhiteman
    SanfordWhiteman
    Level 10
    December 8, 2017

    ...that limits the way we can use it in tokens and on the email (without velocity script)...

    I don't know why "without Velocity script" would be a requirement since this is exactly what Velocity excels at, and you don't have to continuously rewrite your VTL tokens.

    We've done what you describe by storing all owner metadata (picture, email, other contact info) in a global Velocity token that serves as a data library. Then another Velocity token displays the appropriate data for the current lead's owner field(s).

    M
    MichelleMc11Author
    Level 2
    December 9, 2017

    Does your global token just live in a folder at the top level of Marketing Activities, or is there a way to keep that seperated in the design studio or somewhere else?

    SanfordWhiteman
    SanfordWhiteman
    Level 10
    December 9, 2017

    Has to be at the top of MA.

    Terms & ConditionsAccessibility statement

    Loading footer...