Why two marketing platforms can claim the same enquiry
Marketing attribution assigns credit for an observed action to earlier interactions under a reporting model. Platforms can disagree because they observe different interactions, use different eligibility windows and apply different credit rules. Treat attribution as a defined view of the customer journey, then reconcile it with actual enquiry and sales records rather than add every platform’s claim together.
Put the advice into practice
Turn scattered marketing into a considered plan
Connect strategy, creative, channels and ongoing review around your sales process.
Explore our marketing services
Discuss an ongoing marketing partnershipUnderstand what attribution is assigning
A customer may encounter an organisation in several places before making contact. The eventual enquiry can be visible to more than one platform, while some earlier influences remain unobserved. Attribution provides a way to assign reporting credit within that partial view. It does not create a complete record of everything that influenced the person.
Google Analytics describes attribution models as rules or data-driven methods for distributing credit. Its attribution settings documentation also explains how a lookback window determines which earlier touchpoints are eligible. These settings matter when interpreting a report or comparing it with another system.
Keep the action itself distinct from its attributed credit. One genuine enquiry remains one enquiry in the organisation’s operational records even if several reports claim influence. A fraction of credit in a model is a reporting allocation, not a fraction of a customer or a separate sales opportunity.
Follow one hypothetical enquiry across several views
| Interaction | What a reporting system might observe | Question for interpretation |
|---|---|---|
| Reads a useful article after a search | An organic visit on a recognised browser | Can this visit be connected to later activity within the available data? |
| Returns through a campaign link | A campaign-tagged visit | Which interaction is eligible under the chosen reporting rules? |
| Discusses the service with a colleague | No direct platform observation | Does a sales conversation reveal an influence missing from the digital record? |
| Submits an enquiry later | A recorded form action and an operational enquiry | Is the action deduplicated and does it represent suitable work? |
The table illustrates possible observations rather than any platform’s exact default configuration. Different identity, consent, tagging and reporting conditions can produce different records. The useful question is what each report includes and excludes, not which screenshot appears most favourable.
Reconcile definitions before judging a discrepancy
Start with the conversion or key-event definition. Are both systems counting the same action, or is one counting an earlier click? Check for duplicate tags, test submissions and events that fire more than once. An attribution discussion cannot resolve a measurement definition that is already inconsistent.
Then compare the reporting period, time zone, lookback window and model. Check whether the report is grouped by the date of an interaction or the later action. Review the scope of channels eligible for credit and any relevant setting changes. Keep a record of the comparison so the next report can use the same assumptions.
Follow a small set of permitted test or known operational records through the process. Establish whether the underlying action is being captured correctly before trying to explain every aggregate difference. Protect personal information while doing this; the reporting team needs a controlled reconciliation method rather than a public list of identifiable enquiries.
Some differences will remain because the tools have different views. Explain that limitation rather than force the figures to match through an undocumented adjustment.
Use attribution as one input to a decision
Attribution can help the team understand recorded paths and compare activity under consistent rules. It should sit beside enquiry quality, sales feedback, delivery capacity and the actual work produced. A channel that receives reporting credit may also depend on service information or conversations elsewhere in the journey.
Avoid treating an attributed result as proof that the action would not have happened without that channel. Credit allocation and causation are different questions. A stronger causal conclusion needs an appropriate comparison or test designed for that purpose, with the limits of the method made clear.
For an ongoing service business, the first improvement may be a reliable enquiry definition and a consistent handover into sales records. Once that foundation is working, attribution reports can be interpreted with more confidence. Keep the commercial decision visible: whether to maintain a programme, improve an asset or test a specific change.
Our conversion data audit guide covers checks on the action being recorded. Resolve those issues before using attribution differences to justify a larger spending decision.
Put two conflicting reports beside the definitions, periods and settings they use. A measurement review can then distinguish a tracking problem from an expected reporting difference.
