
Measurement
Part of How AI marketing tools measurement and reporting work explained
How AI marketing tools' attribution methods differ
See how AI marketing tools such as GA4, Google Ads and HubSpot handle attribution differently, and how to test a model's figures before you report them.
AI marketing tools ship attribution built in, and they do not all agree on what a conversion is worth. Google Analytics 4, Google Ads, Meta Ads Manager, HubSpot and Adobe Analytics each apply their own model, their own lookback window and their own view of which channel can claim a sale. This guide sets out where those methods differ, how to test the numbers they produce, and what UK marketing teams need to record along the way.
What to take away
- Pick the method from the decision it feedsbudget shifts, channel cuts or board reporting.
- Last-click is cheap and clear, but it rewards the final click over the campaign that created demand.
- Platform multi-touch reports flatter each channel because they count the same sale more than once.
- Incrementality tests answer the harder question: what would have happened without the spend.
- Label every number with its method and its limits, so nobody reads a model output as proof.
How the main AI marketing tools differ on attribution
Google Analytics 4 runs a data-driven model by default, weighting the touchpoints in the account's own conversion history instead of applying a fixed position rule, so its numbers shift as volume shifts. Google Ads makes you choose, offering last-click, first-click, linear, time decay, position-based and data-driven models on each conversion action. Data-driven attribution there only becomes available once the account has enough conversions for the model to learn from.
Meta Ads Manager offers no model menu at all. It reports against an attribution setting that pairs a click window with a view window, and it counts only the conversions it can see, so its totals will not net against another platform's. HubSpot's multi-touch attribution reports sit on contact records and offer first touch, last touch, linear, U-shaped and W-shaped splits, which suits long B2B cycles because the CRM, not the ad platform, decides what counts as a touch.
Adobe Analytics exposes a similar menu through Attribution IQ, including an algorithmic model alongside the rule-based ones. Third-party tools such as Triple Whale and Northbeam sit outside the ad platforms, merging their data into one cross-channel figure, which is why they usually pair reporting with holdout testing rather than model choice alone.
Compare attribution methods by the evidence they carry
Last-click, first-click and linear models
These rules are cheap to run because the data already sits in your analytics or ad platform. They assign credit by position: the last click, the first click, or an even split.
Attribution Models Compared
Last-click
- Credit rule
- Last interaction
- Cost to run
- Low
- Data need
- Existing analytics
- Main weakness
- Ignores earlier touches
Multi-touch
- Credit rule
- Spread across touches
- Cost to run
- Low to medium
- Data need
- Volume + identity
- Main weakness
- Weights wobble at low spend
Data-driven
- Credit rule
- Historical patterns
- Cost to run
- Medium
- Data need
- Volume + identity
- Main weakness
- Weights wobble at low spend
The weakness is shared. A position rule describes the shape of a journey, not the cause of a sale. Switch from last-click to linear and the channel ranking changes, even though no customer behaved differently.
Multi-touch and data-driven attribution
Multi-touch models spread credit across several interactions. Data-driven versions weight those interactions using historical conversion patterns. Both need enough volume and reliable identity matching to stay stable.
At low spend the weights wobble from month to month. Compare like-for-like periods and record the sample behind each figure.
Test the number before you report it
Platform-reported attribution and its overlap
Each platform counts a conversion it can see. When a buyer sees a paid social ad, a search ad and an email, three dashboards may each claim the same sale. Platform totals will not sum to banked revenue.
Evidence Strength by Method
Platform-reported
- What it measures
- Platform-visible conversions
- Evidence strength
- Weak
- Disruption
- None
- When to use
- Contribution view
Holdout test
- What it measures
- Incrementality
- Evidence strength
- Strong
- Disruption
- Pauses spend
- When to use
- Budget decisions
Geo split
- What it measures
- Incrementality
- Evidence strength
- Strong
- Disruption
- Pauses spend
- When to use
- Budget decisions
Reconcile at the business level instead: total orders, total spend, blended cost per acquisition. Treat platform splits as a view of contribution, not a ledger. For the wider reporting chain, the guide to measurement and reporting shows how channel data reaches a board pack.
Holdout tests, geo splits and incrementality
A holdout test withholds spend from a randomly chosen group and compares the outcome with the group that kept it. A geo split does the same across matched regions. Both measure incrementality rather than correlation.
This is the strongest evidence available, and the most disruptive. Use it when the budget decision justifies pausing part of your spend for a few weeks.
Put attribution into your reporting routine
Consent, lawful basis and what you may record
Attribution runs on identifiers, and identifiers need a lawful basis. In the UK that basis comes from UK GDPR, while consent for cookies and similar tracking sits under PECR, with the ICO as the regulator. Most organisations that process personal data must also pay the ICO's data protection fee and appear on its register. The ICO's step-by-step guide to direct marketing for your small business walks small teams through consent records, privacy notices and the practical steps.
Consent choices change what you can match, so reported conversion counts move with your consent rate. Note that in the commentary rather than letting a smaller number look like a fall in demand. Where a case needs specific advice, the DMA's legal helpdesk is open to members.
A scoring rubric your team can argue with
Score each method before adoption, not after a budget review. The rubric below is a starting point; set your own weights against the decisions your team actually makes.
Last-click
- Decision it supports
- Daily channel checks
- Cost to run
- Low
- Time to a first read
- Days
- Evidence strength
- Weak
- Main risk
- Ignores earlier touches
Multi-touch
- Decision it supports
- Contribution views
- Cost to run
- Low to medium
- Time to a first read
- Days to weeks
- Evidence strength
- Directional
- Main risk
- Double counts across platforms
Holdout test
- Decision it supports
- Budget shifts
- Cost to run
- Medium to high
- Time to a first read
- Weeks
- Evidence strength
- Strong
- Main risk
- Needs volume and a clean control
A rubric turns a model preference into a documented choice. It also matters when a dashboard shows a recent month beside an older one built on a different rule. Teams that state the rule next to the metric, as in this walkthrough of a reporting dashboard, spend less time re-explaining old figures.
If an attribution figure ends up in a paid ad, the claim must be substantiated, and the ASA's explanation of how UK advertising regulation works sets out who enforces that rule.
Common questions
Which attribution method should a small team start with?
Last-click or first-click, because the data is already in place and the limits are easy to explain. Move to multi-touch or a holdout test when the budget decision is large enough to carry the extra cost.
Do platform attribution reports add up to total revenue?
Rarely. Each platform counts conversions it can observe, so overlapping journeys produce totals above banked revenue. Reconcile at the business level before quoting channel shares.
How often should the attribution rule change?
Change it when the decision it feeds changes, and not more often. Frequent switches make month-on-month comparisons meaningless, so record the rule and the switch date in your reporting notes.



