GA4 knows everything that happened before the form was submitted and nothing that happened after. Your CRM knows everything after and nothing before. The value is in joining them, and the join is simpler than most people expect.
The identifier you need
GA4 assigns every browser a client ID, stored in a first-party cookie. If you capture it at the moment a form is submitted and store it against the CRM record, you have a key that links the two systems.
Alongside it, capture the campaign context that brought them in — source, medium, campaign, and the Google click identifier if the visit came from Google Ads. Do this in hidden form fields populated by GTM.
Step by step
- Expose the client ID. Create a GTM variable that reads the GA4 client ID and writes it into a hidden form field.
- Capture first-touch and last-touch campaign data. Store UTM parameters in first-party cookies on arrival — one set that never overwrites, one that always does — and write both into hidden fields.
- Add CRM fields for client ID, GCLID, first-touch source and last-touch source. Most CRMs need these as custom fields.
- Map the form fields to those CRM fields in your form integration.
- Report. You can now segment CRM pipeline and revenue by the marketing source that produced it.
Sending CRM outcomes back to GA4
The reverse direction is also valuable. Using the GA4 Measurement Protocol, you can send events such as lead_qualified or deal_won back into GA4 against the original client ID, so later stages appear in your analytics reports alongside the website behaviour that preceded them.
Be careful to send these with accurate timestamps and to avoid creating phantom sessions. Measurement Protocol is powerful and unforgiving.
Platform notes
HubSpot handles hidden fields well and its own reporting can then break pipeline down by source with no extra tooling.
Salesforce usually needs custom fields on Lead and Opportunity, plus a decision about what happens to those values on lead conversion — they are frequently lost at exactly that moment.
Zoho supports hidden fields through its web forms, and its integration with Google Ads makes offline conversion upload relatively straightforward.
What this makes possible
- Cost per qualified lead by channel, rather than cost per form fill
- Win rate and average deal size segmented by acquisition source
- Revenue attribution that finance recognises
- Offline conversion uploads back to ad platforms, so bidding optimises to pipeline
Where it usually goes wrong
Almost never in the technical setup. It goes wrong when sales does not maintain stages, when lead conversion wipes the original source fields, or when nobody agrees what a qualified lead means. Fix the process alongside the plumbing or the reporting will be precise and worthless.
Where to go from here
Connecting GA4 to the CRM is what turns analytics from a traffic report into a revenue report. If you want a second pair of eyes on your setup, our analytics and tracking team runs a free tracking audit that covers GA4, Google Tag Manager, conversion events, CRM integration and attribution.