Not every interaction signals the same intent
A product page view, a rate review, and a submitted loan application all indicate engagement, but they are not interchangeable. Soft interactions show that a visitor is learning or considering an option. Hard interactions show a more direct step toward the business outcome. If every action is labeled a conversion, reporting can make a campaign look productive even when application activity is flat.
For an auto loan, soft signals may include reviewing APR information, using a payment calculator, or checking eligibility. For a checking account, they may include comparing account features or reading fee disclosures. Harder actions include a verified application start and a confirmed submission in the appropriate vendor platform. Approval, funding, or account opening is a later outcome with its own timing and source system. A consultation request can be primary for a mortgage program but only a supporting action for a digital checking campaign.
Give each event a clear definition
Write down what triggers an event, where it can fire, and what it means. A “rate review” should have a specific trigger: perhaps opening the auto loan rate table or interacting with a rate selector. Merely loading a page where rates are below the fold is a weaker signal. State which product and action the event represents, where it fires, and whether repeated interactions count once per visit or more often. A clear definition prevents a redesign from making engagement appear to double overnight.
For hard events, confirm the actual system state. An Apply click is an intent signal; it is not proof that the application began. A start should reflect the intake platform's first meaningful step, and a completion should reflect a confirmed submission. If the application system provides an ID, carry it into approved reporting workflows so a later decision can be joined to the original source without putting personal details into ad platforms.
Create a useful hierarchy
For each product, display a progression: product visits, rate or feature reviews, Apply clicks, verified starts, confirmed submissions, and decisions. If auto loan rate reviews rise but starts do not, examine the offer and Apply path. If starts rise but submissions stall, inspect the vendor form and mobile experience. If submitted volume grows while approvals lag, first account for decision timing and application mix. These patterns guide investigation; they do not establish why an individual applicant was declined.
Give media platforms a conversion signal that reflects the intended product outcome when volume and integration permit. A rate review can be a temporary learning signal for a new loan campaign, but label it separately from submitted applications. If the platform is optimizing to Apply clicks, report that fact to the credit union team. Compare those clicks with verified starts and submissions before calling the campaign successful.
Maintain the event plan
Events need ongoing care. Page redesigns, vendor updates, consent changes, and duplicate tags can alter what gets counted. Give every important event an owner, test it after releases, and compare its trend with adjacent steps. Sudden jumps in starts without corresponding intake records are a signal to inspect the implementation.
A good engagement framework makes the journey understandable to both the media team and executives. It lets marketing show how interest develops into applications while keeping the final outcome visible.
A starting scorecard
For each product, choose a small set of events: one or two consideration signals, an application launch or start, a confirmed submission, and a decision where available. Report the count and the rate between adjacent stages. Segment by channel only when campaign source survives the journey. Keep an unknown-source category so the team can see how much attribution is missing.
Review the scorecard with both marketing and the intake owner. If a rate-review event doubles after a page change while starts remain flat, inspect the event before celebrating. If submissions rise but approvals have not arrived yet, account for decision lag. The hierarchy is useful only when its definitions remain credible over time.