RevOps Docs for Startups
  • Welcome
  • Getting Started
    • Quickstart
    • About LeanScale
  • Growth Modeling
    • Building a Growth Model
      • Growth Model Assumptions
      • Growth Model Approaches
      • Growth Model Segmentations
    • Sales Capacity Plan
    • Marketing Plan
    • Customer Success Plan
  • Go-to-market Lifecycle
    • Go-to-Market Lifecycle
    • Lead Lifecycle
    • Sales Lifecycle
    • Customer Lifecycle
    • Proof of Concept Lifecycle
    • Lifecycle Measurement
  • Lead Attribution
    • Attribution Overview
    • Lead Source Taxonomy
  • Measuring Metrics
    • Reporting and Data Analytics
    • Sales Metrics
      • Created Pipeline
      • Weighted Pipeline
    • Marketing Metrics
      • Lead Impact Matrix
      • CAC to LTV
    • Customer Success Metrics
      • Net Retention
    • Partnership Metrics
    • Presenting Metrics
  • GTM Tech Stack
    • GTM Tech Stack Overview
    • When To Buy New Systems
    • Driving System Adoption
    • CRM Considerations
      • User-Oriented CRM
      • Data & Reporting CRM
      • Security-Focused CRM
  • Aligning Sales/Marketing
    • Alignment Overview
    • How to Align?
    • What is an SQL?
    • Building Marketing Operations
    • Defining GTM Process
    • Interviewing GTM Leaders
    • Finding The Right Talent
  • System Demos
    • Data Enrichment
      • Clay
      • Traction Complete
    • Conversational Intelligence
      • Gong
      • Unthread
    • CPQ
      • Dealhub
      • Salesbricks
    • Data Analytics
      • RevVue
      • QFlow
  • CRM Tips
    • Salesforce
      • Create Opp from Contact
      • Validation Rules in Flow
      • Roll Up Summary Field
      • Close Date Change Counter
      • Lead Stages
      • Sales Stages
      • Customer Stages
      • Next Step Fields
      • Lead Source Taxonomy
      • Proof of Concept Stages
      • Displaying Record Information
      • Display Dynamic Lists
      • Messages to End Users
      • Create Custom Buttons
      • Tips for Data Loader
      • Salesforce Inspector Reloaded
      • SFDC Navigator for Lightning
      • Bypass Validation Rules
      • Sales Manager Notes Field
      • Renaming Fields and Objects
      • Getting Faster to Record ID
    • Hubspot
      • Disable Picklist Options
      • Create Yesterday's Date
      • Create Today's Date
  • Strategic Walkthroughs
    • Revenue Operations Flywheel
    • Post-Fundraise Playbook
    • Building Board Decks
    • Building Dashboards
      • CEO Dashboards
      • Executive Dashboards
      • Marketing Dashboards
      • Sales Dashboards
      • CS Dashboards
      • Funnel Analytics
    • ChatGPT as a Salesforce Admin
    • Sales Commission Plans
    • Building Sales Territories
Powered by GitBook
On this page

Was this helpful?

  1. CRM Tips
  2. Salesforce

Lead Source Taxonomy

PreviousNext Step FieldsNextProof of Concept Stages

Last updated 7 months ago

Was this helpful?

Lead Taxonomy in Salesforce

Introduction

Lead sources are a critical component of Salesforce, as they allow organizations to track the origin of their leads and measure the effectiveness of their marketing campaigns. In this document, we will explore the technical aspects of configuring lead sources in Salesforce, including the objects and fields involved, field dependencies, and validation rules.

Objects and Fields

The following objects are related to lead sources in Salesforce:

  • Leads

  • Accounts

  • Contacts

  • Opportunities

  • Campaigns

Each of these objects has a "Lead Source" field, which stores the source of the lead. Additionally, each object has a "Lead Source Detail" field, which provides more information about the lead source.

Field Dependencies

Field dependencies are used to control the values that can be selected in a picklist field based on the value of another picklist field. For example, if the "Lead Source" field is set to "Demand", the "Lead Source Detail" field can only be set to certain values, such as "Email Marketing", "Blog Gated Content", "Podcast", or "Webinar".

To create a field dependency, navigate to the object that you want to add the dependency to and click on the "Fields" tab. Then, click on the "New" button and select "Field Dependency". In the "Field Dependency" dialog box, select the "Lead Source" field as the controlling field and the "Lead Source Detail" field as the dependent field.

Validation Rules

Validation rules are used to enforce data quality and integrity in Salesforce. For example, you can create a validation rule that requires the "Lead Source" field to be populated before an opportunity can be closed.

To create a validation rule, navigate to the object that you want to add the validation rule to and click on the "Validation Rules" tab. Then, click on the "New" button and enter a name and description for the validation rule. In the "Formula" field, enter the formula that you want to use to validate the data. For example, the following formula would require the "Lead Source" field to be populated before an opportunity can be closed:

AND(
  ISBLANK(LeadSource),
  ISPICKVAL(StageName, "Closed Won")
)

Conclusion

By following the steps outlined in this document, you can ensure that your lead sources are configured correctly in Salesforce and that your data is accurate and complete.