Attribution
Connect outcomes to the evidence behind them.
The intended attribution model connects relevant events to market, address, representative, channel, campaign, source, order, installation and activation—where source records support it.
The problem
Several channels may influence one household. Adding their conversion totals can double-count customers, while incomplete records can leave the origin of an activation unresolved.
The operating model
Capture permitted source context
Potential channel classes include door, direct mail, search, paid social, referral, community and partner. Channel labels alone do not prove causation.
Match events and preserve uncertainty
Review identifiers, timing and duplicate records. Carry partial, conflicting and unknown attribution instead of forcing a single source.
Reconcile confirmed outcomes
Connect provider-confirmed activation to supporting records, with an agreed attribution method and a record of revisions.
Evidence and provenance
Permitted source and campaign records, address matches, interaction timestamps and provider outcome evidence are needed. Reporting must identify its scope, attribution method and missing sources.
Limits and boundaries
Perfect deterministic attribution is not promised. Association is not proof of incremental lift. This page adds no tracking pixels or analytics events, and customer PII must not be sent to public analytics.
Related solutions
Related Envoy OS modules
Start with the workflow and its evidence.
Confirm current scope, provider responsibilities and implementation status with Envoy. Do not send private customer or financial records in an initial inquiry.