The Feed has always supported duplicate checking by Email & Name & Company. However, I don’t think it’s ever worked correctly.
Keap supports two kinds of Company fields: a simple string value (name), and a formal Company record (just another kind of Contact)In earlier versions, the Feed could ask the Keap server for a three-valued duplicate contact check during Contact creation. This duplicate check, enabled on a Feed’s Settings page, selects a key from of three possible keys: 1) Email; 2) Email & Contact Name; 3) Email, Email & Contact Name, Company Name. The Keap server looks for a Contact with a matching key, creating a Contact when no match is found, and updating a Contact when a match is found.
The feed stored the Company Name in a text field, and didn’t create formal Company record. The server-side check never found a duplicate key on those three key values because it checks for a Name match in the formal Company record. It doesn’t check the Company text field for a possible match.
As part of the move to the REST V2 API, I was prepared to drop the 3 value duplicate check. When the V2 API was announced, Keap was not planning to implement a server side duplicate test during Contact creation. This meant any Feed rewrite must include a duplicate check for the two remaing keys: 1) Email and 2) Email and Name. In the first week of April, Keap announced they would implement a duplicate Contact test on the server.
Implementing such a test on Keap’s servers is a Good Thing. It improves the Feed performance, which improves the site visitor experience.
Keap’s implementation obviates the need for such duplicate checks in the Feed.
Nevertheless, this still means the Feed won’t support the 3 value duplicate key check. The Feed doesn’t create a formal Company record. It can ask the Keap server to check for a 3 value duplicate key. Keap will dutifully test Contact Email, Name, Company (formal) before Contact create. This test will always return “missing”, which will create, not update, a Contact.
Leave a Reply