Google Workspace → CRM Lead Merge
How RevSure collapses GW leads into Salesforce / HubSpot
Core idea: When a Google Workspace lead and a Salesforce/HubSpot lead share the same email, RevSure does not keep two leads. It overwrites the GW lead’s ID with the CRM lead’s ID — so both rows share one identity. Activities then attach to that CRM lead.
Step | What happens | Result |
|---|---|---|
1. Create GW lead | From Gmail/Calendar, create a person + GW lead only when no lead already exists for that email (and domain is on Target Account List). | GW placeholder lead exists |
2. Match by email | Find GW leads whose person email = a Salesforce or HubSpot lead email. If multiple CRM matches, pick the closest by created time. | GW lead ↔ CRM lead pair |
3. Overwrite GW lead ID | UPDATE the GW lead: set id = CRM lead id. The GW row now carries the same ID as the SF/HS lead. | One shared lead identity |
4. Point activities + cleanup | Remap GW email/meeting activities to the CRM lead (SF preferred over HS). Drop leftover GW RS_NULL placeholders when CRM already exists for that email. Suppress GW activities that duplicate existing SF activities. | Engagement lives on CRM lead; |
Bottom line: Salesforce/HubSpot remains the system of record. Google Workspace fills in email & meeting engagement. Matching is by email; unification is done by rewriting the GW lead ID to the CRM lead ID.