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 a credit union, soft signals could include viewing loan rates, using a payment calculator, reading eligibility requirements, opening a comparison page, or returning to a product page. Hard actions might include starting an application, submitting it, scheduling a consultation, or opening an account. The precise classification depends on the product and the purpose of the campaign; a booked appointment may be the primary outcome for one program and a supporting step for another.
Give each event a clear definition
Write down what triggers an event, where it can fire, and what it means. A rate review, for example, could mean that the rates section entered the viewport, that the visitor opened a rate table, or that they spent meaningful time comparing options. Those definitions lead to different counts. Choose an action that can be implemented reliably and explained in one sentence.
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
A simple hierarchy might be: awareness actions, product consideration, application intent, confirmed submission, and decision. This gives teams a way to diagnose a funnel. A campaign with strong rate reviews but weak starts may need a clearer offer or call to action. Strong starts but low submissions may suggest friction in the application. High submission volume with weak approvals may raise questions about audience fit, product messaging, or the quality of source data. These patterns are prompts to investigate, not automatic conclusions about cause.
Keep primary optimization goals close to the outcome. Soft actions can help a new campaign learn when completed applications are sparse, but they should not silently replace application milestones in performance reporting. If a platform optimizes to a rate-page view, say so. Review whether that signal actually predicts later submissions or approvals before assigning it more value.
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.