B2B lead attribution examples for UK marketing teams

What to take away

B2B lead attribution begins with a decisionwhich source should be credited for a sales qualified lead.
Attribution in HubSpot and Salesforce works when stages are defined once and reused across marketing and sales.
The table below summarises five examples; each row names the tracked signal, the attribution rule and the UK data note.

Start with the UK data rule, then the model

Before choosing a model, write down the lawful basis for each tracked signal. The ICO's lawful basis guidance sets out consent, legitimate interests and the other options. lawful basis guidance

Checklist for each tracked signal:

Name the lawful basis (consent, legitimate interests or another).
Record where the basis is stored (for example, in HubSpot or Salesforce).
Limit fields to what the model needs.
Review the basis at least once a year.

B2B lead source tracking mixes website analytics with HubSpot or Salesforce fields, so each field needs its own lawful basis.

First touch on a gated guide

A UK B2B software firm records 120 marketing qualified leads in January 2024. First touch credits the gated guide with 40 leads (33%), LinkedIn with 30 (25%) and organic search with 50 (42%). Of those 120, 30 become sales qualified leads.

Under last touch, the guide gets 9 of the 30 (30%), because 9 last touched the demo request page after reading the guide. This example is illustrative, not a benchmark.

Last touch on a demo request

In HubSpot, the demo request form URL becomes the last touch. If the same lead attended a webinar two weeks earlier, the webinar credit disappears. Last touch is simple for sales teams, but it can hide the webinar, review site or partner that warmed the lead. Use it as a reporting convention.

Multi-touch across a UK enterprise cycle

A UK industrial software firm runs a six-month cycle: LinkedIn ad, webinar, case study, sales call, proposal. Multi-touch attribution shares credit across those touches. multi-touch attribution is a common method, but the split depends on the rule you choose.

A linear rule treats every touch as equal. A position-based rule gives 40% to first and last and 20% across the middle. The choice changes the reported winner.

A comparison table for UK B2B lead attribution examples

The table below sets out five examples.

Five UK B2B attribution examples

Example

First touch on gated guide: Content download ID
Last touch on demo request: Form URL and timestamp
Linear multi-touch: Five campaign touches
CRM stage attribution: Opportunity stage history
Offline event lead: Badge scan upload

Tracked signal

First touch on gated guide: Did content create lead?
Last touch on demo request: Did demo page close lead?
Linear multi-touch: Which mix helped?
CRM stage attribution: Did sales activity change outcome?
Offline event lead: Did event influence pipeline?

Attribution question

First touch on gated guide: Record consent or legitimate interests
Last touch on demo request: Avoid free-text fields in analytics
Linear multi-touch: Keep identifiers minimised
CRM stage attribution: Restrict access by role
Offline event lead: Check notice and lawful basis

UK data note

First touch on gated guide
Last touch on demo request
Linear multi-touch
CRM stage attribution
Offline event lead

UK B2B lead attribution examples

Tracked signal

1. First touch on a gated guide: Guide download ID in HubSpot
2. Last touch on a demo request: Demo form URL in HubSpot
3. Multi-touch on a UK enterprise cycle: Five campaign touches in Salesforce
4. Salesforce stage attribution for a sales qualified lead: Opportunity stage history in Salesforce
5. Offline event lead: Badge scan upload

Attribution rule

1. First touch on a gated guide: First touch
2. Last touch on a demo request: Last touch
3. Multi-touch on a UK enterprise cycle: Linear or position-based
4. Salesforce stage attribution for a sales qualified lead: Stage credit
5. Offline event lead: Event credit

UK data note

1. First touch on a gated guide: Record consent or legitimate interests
2. Last touch on a demo request: Keep free-text fields out of analytics
3. Multi-touch on a UK enterprise cycle: Minimise identifiers
4. Salesforce stage attribution for a sales qualified lead: Restrict access by role
5. Offline event lead: Check notice and lawful basis

Salesforce stage attribution with a sales qualified lead

Salesforce and HubSpot hold the stage history that makes attribution possible. A sales qualified lead should mean the same thing in marketing and sales reports. Salesforce stage names are not standard, so define your own stages.

Record the lead source at creation, not later. Backfilling a source after qualification creates false history. A data map is the practical starting point, and this walkthrough on mapping personal data and device tracking explains each row before you connect systems.

A lead sees a paid search ad, attends a webinar, then a sales development representative qualifies it. Salesforce shows source as webinar, with paid search as an earlier touch. Report both. The sales qualified lead date should match between systems. A mismatch often means a field is overwritten by a later import. Keep the source field read-only for imports.

An offline event lead

An exhibition badge scan creates a lead. The follow-up email includes a booking link. If the Salesforce source is set to the event, the event gets credit. If the booking link overwrites the source, the event disappears. Agree a rule before the event and keep the original source in a separate field.

How to run a small attribution test

Run a small attribution test

Pick one sales qualified lead stage and one reporting period.
Export the lead source, first touch, last touch and stage dates from HubSpot or Salesforce.
Apply first-touch, last-touch and linear rules to the same rows.
Compare the winner under each rule and note where the source is missing.
Decide one budget or follow-up change, then set a review date.

GA4 data-driven attribution can show which channel path preceded a conversion. Get started with attribution explains the models available. Use the reports as a hint, then test with incrementality or holdouts. Server-side collection may reduce browser loss. For a build, this guide to GA4 data-driven attribution setup covers UK sites.

Common questions

Which lead source should get credit for a sales qualified lead?

Start with the decision the report supports. For demand creation, first touch can be useful. For sales conversion, last touch or Salesforce stage credit may fit better. Record the rule in the report.

How does UK GDPR affect B2B lead attribution?

Collect only what the model needs. The ICO's guidance covers individual rights. Keep consent records separate from analytics reports.

Can attribution prove that marketing caused a sale?

No. Attribution shows reported paths and stage changes. It does not show what would have happened without the marketing touch.

What is a simple first example to test?

Take a gated guide, a demo request and an SQL stage. Compare first touch, last touch and linear credit on the same leads. Then check whether the results change a budget or follow-up decision.