Handling social profile URLs for matching
When to use this guide: Use this guide when configuring or validating engagement platform integration behavior.
Social profile URLs can be formatted in different ways in your CRM. To ensure consistent matching, OutboundSync uses split and contain approaches to account for these variations, depending on whether the social profile URL contains .com/ or not.
Social profile URL with .com/
Section titled “Social profile URL with .com/”Split the social profile URL
Section titled “Split the social profile URL”If the social profile URL includes .com/, OutboundSync will split the URL into two parts: before and after .com/ in the URL string.
This means remove the domain information for the social media network (e.g. https://www.linkedin.com/ or www.linkedin.com/
And then we isolate everything in the public URL after .com/ (e.g. in/janedough).
This ensures that the following variations would both match correctly:
https://www.linkedin.com/in/janedoughhttp://www.linkedin.com/in/janedough
Contains username string
Section titled “Contains username string”OutboundSync then searches by what is contained in the remaining string. This means remaining string (e.g., in/janedough) will still match contacts whose LinkedIn field contains http://, https://, and/or www. For example:
https://www.linkedin.com/in/janedoughwww.linkedin.com/in/janedough
Social profile URL without .com/
Section titled “Social profile URL without .com/”If the LinkedIn URL does not include .com/, then OutboundSync:
- Will not split the URL.
- Will use the full URL as-is**.**
- Will apply contain search to ensure matches.
Example Variations
Section titled “Example Variations”Here are a few more examples of names and how they’re handled:
| Input URL | Match Strategy | Result |
|---|---|---|
https://www.linkedin.com/in/jane | Split at .com/ | Matches in/jane |
http://www.linkedin.com/in/john | Split at .com/ | Matches in/john |
john | No .com/ → no split | Full URL search using contain |
Why This Matters
Section titled “Why This Matters”This approach ensures that small differences in formatting (such as http:// vs. https:// or including www.) do not prevent successful matching.
When URL matching still finds multiple contacts
Section titled “When URL matching still finds multiple contacts”URL normalization fixes format differences but does not disambiguate two HubSpot contacts that store the same profile path — for example, an inactive former-role record and a newer active record after a job change.
When HubSpot returns multiple matches, OutboundSync uses the contact with the most recent create date. See When a lookup matches more than one HubSpot contact for the full tie-breaker behavior.
If duplicate contacts with the same social profile URL are intentional in your CRM, pass the target HubSpot record ID as os_objectlookup_id in your HeyReach lead list. See Using custom lead/contact object lookup ID.
