Minimize the data
Pennant is designed to analyze enrollment performance without requiring student names, email addresses, phone numbers, or street addresses.
PENNANTSecurity and privacy
Enrollment intelligence without student PII.
Pennant uses the performance attributes needed to connect marketing activity with enrollment outcomes while minimizing sensitive student data.
Pennant UActual product view · Value mappings
0Student names required
0Email addresses required
0Phone numbers required
1Shared reporting model
Privacy by design
Use what the decision requires—and leave the rest out.
A useful enrollment view needs dates, statuses, sources, costs, organizational dimensions, and outcomes. It does not need to become another store of student contact information.
Keep definitions visible
Source mappings and standardized reporting categories remain explicit so teams can review how the operating view is constructed.
Preserve accountability
Institutions retain responsibility for source access and definitions; Pennant documents, normalizes, and validates the agreed reporting inputs.
The data boundary
Performance context in. Direct identifiers out.
The final source design is confirmed during implementation based on your systems, governance requirements, and reporting goals.
- Pseudonymous record IDs
- Lead and outcome dates
- Funnel stages and statuses
- Source and campaign attributes
- Campus and program dimensions
- Spend, budgets, and goals
- Student names
- Email addresses
- Phone numbers
- Street addresses
- Message content
- Application essays
Transparent normalization
See how raw values become reporting categories.
Value mappings make the translation from CRM-specific language to standardized dashboard channels and stages reviewable.
- Source-to-channel mappings
- Status- and stage-to-funnel mappings
- Program standardization
- Visible mapped and unmapped states
Shared responsibility
Security starts with a clearly defined implementation.
Pennant and the institution agree on the minimum necessary sources, fields, access, validation process, and reporting scope before launch.
- Approves the source and field scope
- Provides appropriately governed access
- Defines internal users and data owners
- Validates institutional definitions
- Documents the source and field map
- Normalizes only agreed reporting inputs
- Surfaces mapping and data exceptions
- Supports implementation review and training
Start with your requirements
Review the data boundary before connecting a source.
Bring your security, IT, CRM, and enrollment stakeholders into the implementation conversation.
Contact Pennant