A practical CRM attribution event model

Capture events before choosing credit

Store timestamped campaign touches, source identifiers, sessions where permitted, lead creation, qualification, opportunity creation, and revenue events. Attribution models are views over that history; if the raw events are overwritten, the models cannot be reproduced.

Document identity stitching and consent boundaries. Anonymous and known activity should not be joined merely because it is technically possible.

Keep model assumptions visible

First-touch, last-touch, position-based, and data-driven approaches answer different questions. Report the lookback window, eligible channels, direct-traffic treatment, and revenue definition next to the result.

Use attribution as decision support, not proof that one touch caused the outcome.

• Event type
• Occurred at
• Person/account key
• Campaign/source
• Object milestone
• Model eligibility

Reconcile with financial outcomes

CRM revenue can differ from invoices because of probability, currency, tax, refunds, recognition, or duplicate opportunities. Define the reporting purpose and reconcile totals to the appropriate system.

Monitor unattributed volume and changes in tracking coverage; a cleaner-looking chart may simply exclude more activity.