What each model does, and how nod. Mix V3 separates Created, Intent Captured and Final Closed.
Switch the model on your dashboard and the numbers move, sometimes a lot. That's expected. Every model reads the same underlying data; it just splits credit across the touches in a customer's path differently. This article explains what each model does, and which one answers which question.
nod. computes five credit models: First click, Last click, U-Shape, nod. Mix, and Data-driven. All five are calculated live, every time you load a report, from the same frozen touch path for each order. Nothing is precomputed or locked in per model, so switching models never requires a data migration or a recompute. If nod. improves a model's math later, your historical numbers update automatically. (The sixth entry in the picker, Unique, counts participation instead of splitting credit: every entity on a path gets the whole conversion, so its column can add up to more than your conversions.)
A path with only one touch gives that touch 100% of the credit under every model.
nod. Mix starts from a distinction the other models don't make: some touches create demand, others capture demand that already existed. A Meta ad that put your product in front of someone for the first time did different work than the brand search they typed a week later to find you again. One number that blends the two flatters the harvester.
nod. Mix V3 starts with a 70% Creation job and a 30% Capture job, then exposes three roles:
Three rules complete the picture:
A worked example: Meta verified view, then a Meta click with seven active minutes, then Google Brand with a newsletter subscription, then an email click and purchase. With eligible verified evidence, Meta competes for the 70% Creation job; the seven active minutes can raise the click's share against the view or another observed Creation touch, but only through the bounded square-root curve and only when engagement health passes. Google Brand receives 15% Intent Captured and email receives 15% Final Closed. If the verified provider feed is unavailable, the view receives no credit and the Meta click takes the full 70% Creation job. The result is clicks-only, explicitly labelled.
The 70/30 Creation/Capture split is the workspace calibration dial, and its provenance is visible. A fresh workspace shows "Start value, not calibrated yet". A passing brand-pause, geo-split or budget-step calibration can produce a new revision. It does not silently rewrite historical methodology.
The dial accepts 50/50 through 90/10. The 7-day observed-click default, 1-day verified-view default, 30-second view/click deduplication, 50% Intent Capture split, active-time curve and evidence release rules are versioned method safeguards, not hidden channel multipliers.
Observed means the credit came from advertiser-observed evidence. Verified means an eligible provider linked an exposure to the same conversion under a permitted contract. Provisional means the verified feed has not settled through the requested period. Unavailable means nod. cannot use that evidence class. Withheld means privacy or provider release rules suppress the filtered cell. Unavailable and Withheld are never displayed as zero.
Because brand search is where capture bias hides, nod. splits Google Ads into two rows wherever campaign names or search terms allow it: Google Brand and Google Generic. The split reads your workspace's brand terms (seeded from your workspace name, editable in Settings under Channels) against campaign names, and falls back to a plain Google row when a campaign can't be classified. nod. never guesses brand.
Data-driven is meant to be a statistical model that removes each channel from the path and measures the actual drop in conversions instead of applying a fixed weighting rule. It isn't built yet. Today, requesting data-driven returns the same numbers as U-Shape, and the dashboard badges it as a fallback so you can see that at a glance. This holds regardless of how much order volume you have. Treat data-driven as U-Shape with a different name until that badge changes.
Every model works from the same frozen path of touches for a given order. nod. doesn't re-collect or alter data when you switch models. What changes is only the weighting formula applied to that path. This is also why comparing across models is safe: revenue totals, order counts, and the underlying customer journeys are identical underneath. Only the split of credit shifts.
If you want to understand how nod. builds that touch path in the first place, see how attribution works. For a breakdown of the report layouts themselves, see reading the attribution dashboard.