Study guide

5.1 Lead, Campaign, Account, Contact, and Opportunity Flow

Salesforce Admin Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Platform Administrator Orientation and Official Source Control

1.1 Credential Name, Current Outline, and Search Language 1.2 Exam Format, Fee, Score, and Reference Rules 1.3 Trailhead, Trailhead Academy, and Pearson VUE Delivery Workflow 1.4 Domain Weights, Agentforce, and Study Prioritization 1.5 Maintenance Modules, Credential Ethics, and Exam Security 1.6 Developer Edition, Trailhead Playground, and Practice Bank Workflow

2 Chapter 2: Configuration, Setup, User Management, and Org Controls

2.1 Company Information, Fiscal Year, Business Hours, and Locale 2.2 User Records, Licenses, Profiles, Permission Sets, and Login Access 2.3 Login Security, Session Settings, and Identity Basics 2.4 Setup Navigation, Release Readiness, and Change Control 2.5 UI Settings, Home Pages, Apps, and Navigation 2.6 Configuration and Setup Case Lab

3 Chapter 3: Security, Access, Identity, and Sharing Model

3.1 Org-Wide Defaults, Roles, Sharing Rules, and Teams 3.2 Profiles, Permission Sets, Permission Set Groups, and Muting 3.3 Field-Level Security, Page Layouts, and Dynamic Forms 3.4 Record Access Troubleshooting and Login-As Workflow 3.5 Identity, Login History, MFA, and Session Risk 3.6 Data Visibility, Reporting, and Analytics Security 3.7 Security and Access Case Lab

4 Chapter 4: Object Manager, Lightning App Builder, and Data Modeling

4.1 Standard Objects, Custom Objects, and Schema Fit 4.2 Fields, Formulas, Rollups, Validation, and Requiredness 4.3 Lookup, Master-Detail, and Junction Relationships 4.4 Record Types, Business Processes, Page Layouts, and Lightning Pages 4.5 Dynamic Forms, Dynamic Actions, and User Experience 4.6 Schema Change Risk, Data Quality, and Deployment Readiness 4.7 Object Modeling Case Lab

5 Chapter 5: Sales, Marketing, Service, and Support Applications

5.1 Lead, Campaign, Account, Contact, and Opportunity Flow 5.2 Sales Processes, Path, Products, Price Books, and Forecasting 5.3 Case Management, Queues, Assignment, Auto-Response, and Escalation 5.4 Knowledge, Entitlements, Service Console, and Support Productivity 5.5 Sales-Service Data Quality and Automation Boundaries 5.6 Application Configuration Troubleshooting 5.7 Sales and Service Applications Case Lab

6 Chapter 6: Data and Analytics Management

6.1 Data Import Wizard, Data Loader, Export, and Backup 6.2 Duplicate Management, Validation, and Data Quality Controls 6.3 Data Transfer, Ownership, Mass Update, and Mass Delete 6.4 Report Types, Filters, Summary Formulas, and Buckets 6.5 Dashboards, Components, Subscriptions, and Sharing Impact 6.6 Analytics Security, Visibility, and Executive Reporting 6.7 Data and Analytics Case Lab

7 Chapter 7: Automation, Flow, Approval, and Operational Processes

7.1 Automation Tool Selection and Order of Execution 7.2 Flow Builder: Screen, Record-Triggered, Scheduled, and Autolaunched Flows 7.3 Approval Processes, Email Alerts, and Notification Patterns 7.4 Validation Rules, Assignment Rules, and Escalation Rules 7.5 Automation Testing, Debugging, and Governance 7.6 Automation Performance, Recursion, and Maintainability 7.7 Automation Case Lab

8 Chapter 8: Productivity, Collaboration, Mobile, and AppExchange

8.1 Activities, Tasks, Events, Calendar, and Email Productivity 8.2 Chatter, Feeds, Groups, Notifications, and Collaboration Governance 8.3 Salesforce Mobile Navigation, Actions, and Page Design 8.4 List Views, Kanban, Path, and User Adoption Tools 8.5 AppExchange Evaluation, Installation, Permissions, and Risk 8.6 Productivity and Collaboration Case Lab

9 Chapter 9: Agentforce for Platform Administrators

9.1 Agentforce Use Cases, Admin Boundaries, and Fit 9.2 Trusted AI, Security, Data Access, and Permission Implications 9.3 Agent Builder, Prompt Builder, and Grounding Concepts 9.4 Testing, Deployment, Monitoring, and Feedback Workflows 9.5 Agentforce Service, Sales, and Internal Productivity Scenarios 9.6 Agentforce Risk, Troubleshooting, and Governance 9.7 Agentforce Case Lab

10 Chapter 10: Integrated Salesforce Admin Scenario Labs

10.1 New Sales Org Setup Integrated Lab 10.2 Service Team Case Management Integrated Lab 10.3 Data Quality and Analytics Integrated Lab 10.4 Security, Access, and Reporting Integrated Lab 10.5 Flow Automation and Change Control Integrated Lab 10.6 Agentforce and Adoption Integrated Lab 10.7 Full Admin Simulation Strategy

11 Chapter 11: Final Review, Maintenance, and Test-Day Strategy

11.1 Final 30-Day Salesforce Admin Review Plan 11.2 Trailhead Playground Hands-On Drill Plan 11.3 105-Minute Exam Timing, Flagging, and Review Workflow 11.4 Test-Day Checklist: Online or Test Center 11.5 Post-Exam Maintenance Modules and Next Certifications 11.6 Salesforce Admin Final Mixed Review

5.1 Lead, Campaign, Account, Contact, and Opportunity Flow

Key Takeaways Explain This Topic AI

Leads represent unqualified people or companies, while converted leads create or update Accounts, Contacts, and optionally Opportunities.

Campaigns track marketing effort and Campaign Members connect Leads or Contacts to that effort with member status and response data.

Accounts, Contacts, and Opportunities form the core sales data model, and admins must understand ownership, sharing, duplicate prevention, and conversion mapping.

A strong admin can troubleshoot lead conversion by checking required fields, validation rules, duplicate rules, field mappings, record types, and permissions.

Last updated: May 2026

Core Sales Data Flow

A Lead is a person or organization that has shown interest but has not yet been qualified into the customer model. Sales teams use Leads for inquiries from a form, list import, trade show, referral, partner event, or marketing campaign. A Lead can have a company name, contact details, source, rating, status, and owner. It is separate from Accounts and Contacts so sales development work can happen before the organization decides the person belongs in the durable customer database.

When a Lead is qualified, the user converts it. Conversion creates a new Account, creates a new Contact, and can create a new Opportunity. It can also attach the converted person to existing Account and Contact records when the user has access and the match is selected. The admin controls field mappings from Lead fields to Account, Contact, and Opportunity fields in Setup. A common mistake is adding a required custom field to Contact or Opportunity but forgetting that lead conversion must be able to populate it.

  • Object Primary purpose Admin decision point Common trap
  • Lead Unqualified interest Status values, assignment, conversion mapping Treating every inquiry as an Account

Campaign Marketing effort Member statuses, hierarchy, influence needs Using free-text source instead of member tracking

Campaign Member Person participation Status and responded flag Forgetting Leads and Contacts can both be members

Account Company, household, or customer entity Ownership, hierarchy, teams, duplicates Creating duplicate Accounts during conversion

Contact Individual tied to an Account Required fields, roles, privacy rules Assuming Contacts can exist without data stewardship

Opportunity Potential revenue event Stage, amount, close date, products Creating Opportunities for unqualified interest

Campaigns And Member Status

Campaigns are the Salesforce feature that tracks marketing activity inside core Sales Cloud. A campaign may represent a webinar, email series, advertisement, trade show, direct mail run, or partner event. Campaign hierarchy can roll up related efforts, such as a fiscal quarter program with several child campaigns. Campaign Members link Leads and Contacts to the campaign. Member status values, such as Sent, Registered, Attended, or Responded, should match the business activity.

For administrator work, the status design matters because reports and campaign influence depend on consistent member data. If one campaign uses Attended and another uses Showed Up, reporting becomes messy. If the Responded flag is not set correctly on the member status, response reporting is misleading. If users only populate Lead Source, they lose the ability to track multiple touches for the same person. Lead Source is useful as an original-source field, but Campaign Members are better for many-to-many marketing participation.

Conversion Workflow

A practical lead process starts before conversion. Decide how Leads enter Salesforce, how they are assigned, what statuses mean, who can convert them, what duplicate rules run, and which fields are required. Web-to-Lead and imports can create many records quickly, so validation and assignment rules should be tested with real sample records. Do not make the status path so complex that users work around it with notes or spreadsheets.

Admin checklist for lead conversion

Confirm Lead Status values include a converted status and match the sales process language.

Review Lead field mappings to Account, Contact, and Opportunity fields.

Check required fields on Account, Contact, and Opportunity before enabling new validation rules.

Test conversion as a standard sales user, not only as System Administrator.

Verify duplicate rules and matching rules warn or block at the right point.

Confirm record type selection and page layouts after conversion.

Report on converted Leads, conversion rate, source quality, and campaign response.

Accounts, Contacts, And Opportunities

Accounts and Contacts are the durable relationship records. Opportunities represent sales deals, renewals, expansions, or other revenue events. A B2B organization usually treats Accounts as companies and Contacts as people at those companies. A B2C organization may use person accounts if enabled and designed intentionally, but that is a major model choice. Platform Administrator scenarios usually focus on knowing which record owns which data and how the records relate.

Opportunities belong to Accounts and usually have a primary Contact Role or related Contacts through Opportunity Contact Roles. Contact Roles help show who is the evaluator, signer, economic buyer, or technical contact. Products and Price Books are discussed in the next section, but the key flow here is that an Opportunity should represent a qualified revenue pursuit, not a raw inquiry. If the team creates Opportunities too early, forecasts and pipeline reports become inflated.

Security, Ownership, And Automation Boundaries

Ownership drives record access when org-wide defaults are private or controlled. Leads, Accounts, Contacts, Opportunities, and Campaigns can have different sharing behavior, and users may be able to convert a Lead only when they have the right object permissions and field access. A conversion failure that looks like a sales process problem may really be Create permission missing on Opportunity, field-level security on a mapped field, or a validation rule blocking the target record.

Automation should support this lifecycle without hiding the business decision. Assignment rules can route Leads by region, product, queue, or source. Flow can stamp source details, create follow-up tasks, or notify owners. Duplicate rules can warn users before they create another Account or Contact. Avoid automating conversion itself unless the qualification criteria are truly objective and the downstream data requirements are stable. Bad automated conversion creates duplicates faster than humans can repair them.

Scenario Judgment

Suppose marketing imports 3,000 trade show attendees. The sales manager wants every attendee converted to an Account and Opportunity immediately. A strong admin would slow down and ask what qualifies a real Opportunity, whether the attendee company already exists, whether campaign membership should capture attendance, and whether SDRs should work the Leads first. The safer configuration is usually to import or capture them as Leads, associate them with the trade show Campaign, assign them through rules or queues, and convert only qualified records after duplicate checks.

For hands-on practice, create a small Campaign in a Trailhead Playground, add one Lead and one Contact as Campaign Members, customize member statuses, convert the Lead, and inspect the resulting Account, Contact, and Opportunity. Then add a required custom field to Opportunity and test conversion again. This exercise makes the common exam traps visible: required fields, mappings, duplicate behavior, owner assignment, and reporting expectations.