WebmasterID logoWebmasterID
Attribution models

Algorithmic vs rules-based attribution

Attribution models split into two families. Rules-based models apply fixed, human-chosen weights to touchpoints by position — last-click, first-click, linear, time-decay, U/W-shaped. Algorithmic (data-driven) models learn credit from observed conversion paths using methods like Shapley values or Markov chains. This page contrasts the two and explains when each is appropriate.

Verified against primary sources

What this means

Rules-based attribution encodes a belief about which touches matter — last-click says only the closer matters, linear says all matter equally, time-decay says recent matters more. The weights are chosen by people and stay fixed regardless of the data.

Algorithmic attribution instead estimates credit from the data itself. It compares converting and non-converting paths and assigns credit based on how channels' presence changes conversion likelihood, using techniques such as Shapley value averaging or Markov removal effects. Google's data-driven attribution is the best-known production example.

Trade-offs

Rules-based models are transparent, reproducible, need little data, and are easy to explain to stakeholders — but their weights are arbitrary and can systematically misvalue channels. Algorithmic models adapt to your actual journeys and avoid hand-picked weights, but they need sufficient conversion volume, are harder to audit, and can quietly understate channels that are undertracked.

Neither family proves causation on its own. Both describe how recorded credit is distributed; for causal claims you still need incrementality experiments or marketing-mix modeling.

How it appears in analytics and logs

If credit follows a fixed positional formula, the model is rules-based; if credit shifts as the underlying path data changes, it is algorithmic. Each implies different trust and data conditions.

Diagnostic use case

Decide between a transparent fixed rule and a data-driven model by weighing interpretability and data requirements against the risk of arbitrary weights.

What WebmasterID can help detect

WebmasterID provides first-party path data that can feed either approach, so you can apply a simple rule for clarity or supply an algorithmic model with the journeys it needs.

Common mistakes

Privacy and accuracy notes

Both families operate on touchpoint paths, not identity. Algorithmic models need more path volume but still work on aggregated, de-identified journeys.

Related pages

Sources and verification notes

Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.