Skip to main content
Robert W
Explorer
Sep 16, 2026 9:35 PM UTC
Question

Zoom integration creating duplicates when name and email match

Hi, I've noticed the Every Action Zoom integration creates a lot of duplicates, even when the name and email are an exact match to an existing Contact Record. Are there any plans to fix this? 

Or if there is some way we can turn on stricter matching across our organization we would gladly do that too as we'd rather not have more than one contact record per email address anyway. Thank you!

2 replies

rachel moody
Community Manager
Sep 23, 2026 3:55 PM UTC

Hey ​@Robert W, When Zoom syncs registrants to EveryAction, it passes three fields: First Name, Last Name, and Email Address. These are the only fields used in the sync, and EveryAction's standard contact matching logic runs against those. The issue is that EveryAction's matching logic doesn't use email alone as a unique identifier — it considers the combination of name and email together, which means small variations (like a nickname vs. a full name) can cause the system to create a new record even when an identical email exists.

I can certainly pass this feedback along to our product team for you. 

We did just launch a new way to merge duplicates using Que, which is free for everyone right now and will make it a lot easier to merge your duplicates. Here’s some help articles that will walk you through how to use it: https://community.bonterratech.com/duplicate-management-408

Rachel at Bonterra
Robert W
Robert WAuthor
Explorer
Oct 27, 2026 4:22 AM UTC

Hey ​@rachel moody thanks for the reply about this and sorry for not responding sooner, though what I meant to ask about was new contacts being created when the name is also an exact match to an existing contact in addition to the email address.

An example of this is earlier this year my organization hosted a series of events over Zoom and I made a custom form (with Zapier) that registered people for all of the upcoming Zoom meetings in the series with the one form instead of having to register for each one individually, and this created a number of duplicate Contact Records - so this was Zoom registrations for multiple Zoom meetings with the exact same First Name/Last Name/Email, in some cases brand new Contacts that were created by the EA Zoom integration and had no other data besides Name/Email/Event registration (for some of the events), and then another new Contact Record would be created that also had the same Name and Email (and was registered for the rest of the events). This happened for around 20 of the 200 people who registered for multiple events with the one form, and I've looked through these duplicates to try to figure out if there's any pattern at all or any similarity between the duplicates or what events the duplicates were registered for but haven't been able to find any. 

This is one example I thought I'd mention since the Names/Email all came from one source and were identical, though these same Name/Email duplicates being created by the EA Zoom integration happens frequently outside of this too. And to touch on duplicates being created when the Names have slight variance (which isn't ideal but is more understandable), if there was any way to even match existing Contacts with Email and First Name that would actually vastly cut down on the duplicates being created - awhile back I pulled a list of everyone who ever attended a Zoom event and in a spreadsheet used some formulas to see how many duplicates there were created by the Zoom integration, and while there's dozens of duplicates with exactly matching names I have at least 600 examples of duplicates that have the same First Name and same Email, with some of them being things like their last name was "R." in one meeting and in another it was "R" so a new Contact Record gets created. So while even this would save us from having a massive number of duplicates and would be a huge help, I moreso wanted to ask about matching where First Name/Last Name/Email are the same, since that seems more like it's supposed to be the intended functionality of the integration that sometimes doesn't work. And thanks so much for your help!