RevOps and engineering leads
Attribution on the contact record or in a separate dashboard?
By the MarqIQ operations team · Updated
The short answer
If the source lives only in an attribution dashboard, marketing can see it and nobody else can act on it. When first-touch and most-recent source are written onto the CRM contact, sales sees it on the record, routing and scoring can use it, and any CRM report can group pipeline by it. MarqIQ takes the second approach: it writes attribution into HubSpot, Marketo and Salesforce fields you own, and reports on top of that.
Four places attribution can live
These are not mutually exclusive, and larger teams run more than one. The question is which one is your system of record for "where did this person come from".
- Web analytics (GA4 and similar). Strong on sessions and on-site behaviour. It is anonymous by design, so it cannot tell you that this opportunity came from that campaign.
- CRM-native attribution reports. Convenient and already paid for. They depend on the CRM’s own tracking and bucketed source values, and the multi-touch revenue reports usually sit in the top pricing tier.
- Warehouse-based attribution platforms. The most flexible modelling, for teams with a data warehouse, an analyst to run it and a quarter to implement it. The output is a dashboard that lives outside the CRM.
- Source written to the contact record. Less glamorous. The data sits in ordinary CRM fields, so every existing report, list, workflow and sales view can use it on day one.
Why we put it on the record
From an engineering seat, the deciding factor is ownership. Fields in your CRM are yours. They survive a vendor change, they are covered by the access controls you already have, and they need no new pipeline to maintain. A dashboard that holds the only copy of your attribution is a dependency you will pay for at renewal.
From a RevOps seat, it is about who can act. An SDR opening a contact sees "First touch: Forrester, Analyst" and opens the call differently. Lead routing can send press-sourced enterprise leads to a named rep. Neither happens when the insight sits in a tool that only marketing logs into.
The trade-offs, stated plainly
Writing to the record means living within CRM field limits and API quotas, so each person’s form fills, with the first and last source on every one, stay in MarqIQ while the summary values go to the contact. Modelling is less elaborate than a warehouse platform: four models — first touch, last touch, linear and time decay — each worked out from the first and the last source on a form fill, without custom algorithmic models. If you have a data team and need bespoke modelling across ad-platform cost data, a warehouse tool will do things we do not.
What you get in exchange is time to value measured in days, no developer, and attribution your sales team can actually see.
Quick answers
What is the difference between GA4 attribution and CRM attribution?
GA4 attributes anonymous sessions and conversions. CRM attribution attaches the source to a named contact, so it can be followed through to opportunities and revenue and used by sales, routing and scoring.
Do I need a data warehouse for B2B marketing attribution?
No. A warehouse helps with custom modelling at scale, but first-touch and multi-touch attribution can be captured in the browser, resolved on a server and written straight onto CRM contact fields with no warehouse.
Which CRMs does MarqIQ write attribution into?
HubSpot, Marketo and Salesforce have the full guided setup. MarqIQ also maps UTM attribution for Zoho CRM, Pipedrive, Microsoft Dynamics, Pardot, Mailchimp, Salesforce Marketing Cloud, Adobe Campaign and Adobe Journey Optimizer.
Read next
Check your own numbers first
Connect one tool and run the audit. It shows how much of your lead source data is missing, and the report is yours to keep either way.