On this page
Salesforce and GA4 disagree because they are built to answer different questions. GA4 counts website events, sessions, and users. Salesforce counts the records sales works: Leads, Contacts, Accounts, Opportunities, and Campaign Members. A form submit can show up in both, but it is a different object in each system.
Why the counts diverge
One website form can create a GA4 event, a Salesforce Lead, and later a Contact, an Account, and an Opportunity. Each record carries its own dates and rules. When a rep converts a Lead, it becomes a Contact and an Account, and optionally an Opportunity. Converted leads also drop out of many standard lead views unless the report includes them, so a “leads this month” number can shrink after sales works the list. Nobody has to make a mistake for the totals to split.
Duplicates and spam push the numbers apart in both directions. One person can submit several forms, which creates several GA4 events, while Salesforce duplicate rules or a rep may merge them into one Lead or Contact. Test and spam submissions may be deleted in Salesforce but still counted in GA4. Salesforce also holds records with no website event at all, such as list imports, events, sales prospecting, partner leads, and phone calls.
| Mismatch | Salesforce view | GA4 view | Report rule |
|---|---|---|---|
| Lead count | Leads, plus Contacts after conversion | Form events and sessions | Use Salesforce records for pipeline; use GA4 events for web behavior |
| Traffic source | One Lead Source picklist, set or overwritten by hand | Session source, assigned automatically per session | Name which field is the source of record |
| Source detail | UTMs and click IDs lost unless hidden fields are mapped | UTMs and click IDs captured on the session | Map UTM and gclid hidden fields on the form |
| Timing | Lead Created, Converted, or Opportunity Close Date | Event date | Pick one date field and state the time zone |
| Revenue | Opportunity Amount on closed-won opportunities | No view unless revenue is imported | Use Salesforce for revenue |
Start with the reporting question
The first question is not, “Which system is right?” It is, “What decision is this report supposed to support?” If the question is lead quality from a campaign, the report needs GA4 for the web side and Salesforce for what each lead became. If the question is pipeline or closed-won revenue, Salesforce leads. If the question is why traffic moved, GA4 leads.
Reconcile before the meeting
- Name each metric as a traffic, conversion, lead, contact, opportunity, pipeline, or revenue figure.
- Write the exact GA4 event name and the exact Salesforce object and field used for each number.
- Lock the date field, date range, and time zone before exporting anything.
- Decide how converted leads, duplicates, and test or spam submissions are counted, and apply the same rule to both systems.
- Store the UTMs and click IDs on the Lead so the join does not depend on a rep remembering the source.
- Explain each expected gap in the report itself, not in a follow-up thread.
Where Salesforce should win
Salesforce should be the source of truth for leads, contacts, accounts, opportunities, pipeline stages, and closed-won revenue. Opportunity Amount on closed-won opportunities is the revenue figure, because GA4 has no view of it unless revenue is imported. Campaign credit in Salesforce is only as good as the Campaign Members and opportunity contact roles behind it, so those need to be kept current before a campaign report is trusted.
Where GA4 should win
GA4 should be the source of truth for website behavior: sessions, users, events, landing pages, engagement, and traffic movement. It is the right place to see whether a campaign changed volume or quality before that change reaches Salesforce. GA4 attribution uses its own model across channels, so its credit will not match Salesforce campaign credit. The problem comes when a team uses GA4 to defend pipeline, or Salesforce to explain every website session.
Go further with the HubSpot and GA4 comparison, the multi-touch attribution guide, and the platform mismatch guide. If you want a second pair of eyes on the numbers, book a tracking audit: bring the disputed report and we’ll map the first workflow you can trust.
Frequently asked questions
Why does Salesforce show fewer leads than GA4 form submissions?
Salesforce counts records, not events. Duplicate submissions can merge into one Lead or Contact, test and spam records can be deleted, and converted leads drop out of many standard lead views. GA4 still counts the events it received. Salesforce can also show more leads when imports, events, or phone calls create records with no website event.
Should Salesforce or GA4 be the source of truth?
Use Salesforce for leads, pipeline, opportunities, and closed-won revenue. Use GA4 for website behavior and traffic. Join them with UTMs and click IDs stored on the lead.
Why is Lead Source wrong in Salesforce?
It is often not wrong, just different. Lead Source is one picklist value that reps can set or overwrite by hand, while GA4 assigns a session source automatically for each session. Compare the two using the UTMs and click IDs stored on the lead before deciding which one to trust.
Can MetricMaven reconcile Salesforce and GA4?
Yes. We map the Salesforce fields, GA4 events, UTMs and click IDs, date rules, and exclusions so the team can explain what changed and why without rebuilding the report by hand.