Potential inputs
- Pseudonymous record IDs
- Lead, application, and enrollment stages
- Source, campus, and program fields
- Stage dates and status history
PENNANTCRM integration
Connect Salesforce to enrollment decisions.
Connect agreed lead, application, enrollment, source, campus, and program fields to the Pennant reporting model.
Connection approachImplementation-scoped CRM connection
Available when the institution can provide approved Salesforce access, fields, definitions, and historical coverage.
Pennant UActual product view · Mappings
Source-specific reporting
Use the data for questions it can actually answer.
Every implementation confirms access, definitions, historical depth, refresh cadence, and validation before the source becomes part of a decision view.
Decisions supported
- Which sources produce confirmed enrollment outcomes?
- Where does funnel progression weaken?
- How do campuses and programs compare?
Implementation requirements
- Approved Salesforce permissions
- Documented objects and fields
- Agreed stage and outcome definitions
What to validate
A connected source still needs context.
Pennant preserves the distinction between platform signals, reporting inputs, and institution-confirmed enrollment outcomes.
- Custom Salesforce implementations require custom mapping
- Available history depends on retained source records
- Pennant does not require student names or contact details
Integration FAQ
Questions teams ask about Salesforce.
Does Pennant replace Salesforce?
No. Salesforce remains the CRM and system of record. Pennant uses agreed fields to provide a normalized enrollment marketing decision layer.
Can Pennant support custom Salesforce objects?
Potentially. Custom objects and relationships are reviewed during implementation to confirm access, meaning, coverage, and reporting value.
Learn more about source mapping and validation, data reconciliation, and Pennant security and data minimization.
Confirm the fit
Review your Salesforce reporting environment.
Available capabilities depend on your configuration, permissions, data quality, and agreed implementation scope.
Book a demo