Match people to Salesforce records
Matching scenarios decide which Salesforce record a person updates. Each starts with email or phone, the first that finds a record wins, and no match creates one or skips.
ProOwner
On this page
When someone registers, Ovante looks for that person's record in Salesforce before it writes anything. Your matching scenarios say what has to agree for a record to count as the same person. A new connection matches on email alone.
How matching works
- A scenario is one or more rows, each an Ovante field compared with a Salesforce field. Every row in a scenario must match.
- Scenarios run top to bottom. The first one that finds a record decides, so put the strictest first.
- Each scenario's first row is Email address or Phone number. A name or a date of birth on its own can't tell two people apart, so it can only narrow a scenario that already has one.
- Phone numbers match on their digits, so "(555) 010-0100" and "555.010.0100" are the same number.
- Once a person is linked to a record, Ovante writes to that record from then on and doesn't match them again.
Edit the scenarios
- 1Open Settings → Integrations, and click Open on the Salesforce card.
- 2Under Matching criteria, on Update a contact when…, click Edit rules.
- 3In each row, pick the Ovante field on the left and the Salesforce field it compares with on the right. Ovante picks the standard field for you.
- 4Click Add field to add a row to a scenario, or Add scenario for another scenario.
- 5Drag a scenario by its grip to change the order.
- 6Pick what happens under If several contacts match.
- 7Click Save, then Save changes at the bottom of the page.
When several records match
| If several contacts match | What Ovante does |
|---|---|
| Update latest | Links the most recently changed record |
| Update all | Links every matching record, and sends each one every update, Campaign membership and Task. Duplicates in Salesforce stay duplicates. |
| Don't update any | Writes nothing. History shows Not sent and names the records, so you can merge them in Salesforce. |
When nothing matches
Create a new contact… decides:
- in all other scenarios creates a record.
- never writes nothing, and History says no record matched.
A new record goes through your Salesforce duplicate rules. A rule set to alert lets the record through and lists the pair in Salesforce's duplicate report. A rule set to block stops it, and History says which record it collided with. See Salesforce made a duplicate record.
- When
- No matching rule finds a Salesforce record for a person
- Then
- Ovante creates one, unless Create a new contact… is set to never; then it skips the person and History says why.
Good to know
- Labels say "contact" for both objects. If Salesforce object is Leads, scenarios look for Leads and skip converted ones.
- Ovante reads at most a small set of candidate records per lookup: their name, email and phone, and only for the registration's own email or phone. See What Ovante reads in your CRM.
Was this helpful?
Related
Map contact fieldsChoose which Salesforce field each Ovante contact field writes to, and whether an update overwrites what Salesforce has or only fills empty fields.Read the History tabHistory lists every item Ovante sent to your CRM, or decided not to send, with the reason in a sentence. Gray means Ovante chose to skip it; red means it failed.Salesforce made a duplicate recordWhen no matching scenario finds a record, Ovante creates one, and Salesforce's duplicate rules let it through unless they block. Add a scenario or change the rule.Connect SalesforceSign in to Salesforce from Settings, Integrations. Ovante then acts as that Salesforce user, with exactly that user's access.