Update Identifier Matching Key

Matching key values are not updated

When a field is mapped as a Matching key its value is not updated. However, because existing Send2CRM identification takes precedence it is possible for a visitor be identified against a record where the key doesn’t match. In these cases you may wish to update the value.

Consider the following scenario:

1. A website form uses a mapping that identifies as a Salesforce Lead, using Email as the matching key. The first time a visitor submits the form a new Lead is created.

2. The visitor comes back to the website and wishes to re-submit the same, or another, form using a different email address - perhaps it has changed, or perhaps it was mis-keyed the first time.

3. The form submission goes through successfully. Send2CRM knows that the visitor is already identified, so the Lead associated with the visitor record is used. The Email address on the Lead is not updated.

4. An automated email goes out from Salesforce to the Lead as a result of the form submission. But it isn’t using the updated email address!

Update with additional mapping

Send2CRM supports multiple mappings for the same field, so we can simply add another to update the email address where required. Make sure to use the Weight option here to ensure that the Matching key mapping is processed first.

Open

Now when subsequent form submissions are made, the Email will be updated for previously identified visitors. It will also still function as a Matching key for un-identified visitors.