Short answer: Mortgage marketing analytics begin with a written definition of each event, the source that records it, and the person who checks it. A dashboard number alone does not explain what happened, whether two systems are describing the same activity, or whether a record needs review.
Measure the activity your team can define
Use a small measurement dictionary before building a report. The goal is not to collect every available number; it is to make each important activity understandable to the person who must act on it.
| Measurement question | Definition to document | Review question |
|---|---|---|
| Where did a request begin? | Source label, landing page or campaign context, and record owner. | Can the team explain the source without relying on a vague channel name? |
| What interaction was recorded? | Event name, time recorded, and the system that collected it. | Does the event describe an observable action rather than an assumption? |
| What needs a person's follow-up? | Review trigger, next action, and accountable owner. | Where does the owner see the context needed to decide? |
| What should be reconciled? | Record identifier, reporting date, and exception path. | Can two reports be compared without silently counting different things? |
Use events as implementation evidence
Google Analytics describes an event as a measurable interaction or occurrence and describes key events as business-important actions selected by the site owner. Treat that documentation as an implementation reference, then verify the actual event and parameters in the team's own reporting before using it for a decision.
Primary-source context: Google Analytics: About events.
Review five records, not just one total
- Choose records associated with an approved marketing source or request path.
- Compare the event time, source context, record owner, and next action.
- Write down any missing context, duplicate activity, or difference between reports.
- Resolve the definition before changing a campaign, workflow, or report.
Recorded daily-workflow context
This BNTouch training walkthrough shows a daily view with tasks, status-driven workflow, tracker notes, and record-linked activity. It is useful visual context for a record-level review, not proof of report definitions, outcomes, or configuration for another organization.
Source: BNTouch Daily Dashboard and Intelligence Walkthrough.
Scope of this recorded source: The video demonstrates one training environment. It does not establish current product behavior, fields, permissions, timing, data transfer, commercial terms, or a required workflow for another organization.
Keep the evidence trail small and usable
Keep a measurement dictionary, a dated validation note, the record-level review, and the owner's next action together. That makes it easier to distinguish a reporting question from a workflow question.
For a broader mortgage CRM for loan officers overview, use the mortgage CRM system guide and the mortgage lead measurement guide.
