Let unique ID be assigned to data other than email address
Let unique ID be assigned to data other than email address. We have members and would like to use their membership ID number. Unique emails work until someone changes their email outside of Bronto and then you have one person that Bronto thinks are two different contacts. Contact list gets junky.
While I understand this is a frequent request, it is not something Bronto is looking to implement now or in the future. While this may change as part of our recent acquisition by NetSuite that would be far in the future, and is still an unknown. At this time a single email address (or SMS number) will continue to remain the primary key for all unique contacts in your account.
This is a must have.
Tabetha Carnahan commented
Definitely want to see this in place. We are attempting to clean our current email database. We find that our b2b contacts change their emails too often and we begin to see clutter build up. I need a way to overwrite an existing contact in Bronto with the correct email address without losing their RFM metrics.
User e-mail and phone numbers may change but their unique contact ID should persist.
Only the following constraints should apply per bronto account:
- IDs can be either numbers or text.
- Contact IDs must be unique.
We (bronto users) should be able to define the contents of contact ids. This would allow us to create a one-to-one mapping between users in our db and users in bronto, eliminating the need for redundant custom fields, and reducing overhead in our scripts that leverage the API associated with matching contacts in our data warehouse with their contact data in bronto.
Looking forward to see this in place!
Hopefully we'll also be able to merge some of those duplicate contacts when this is available.
Definitely looking forward to this one. We're using our own ID per account which would definitely help. In settings allow to chose which of the existing fields should be treated as UID.
This would help a lot. We have customers that share email addresses, so only one person can be added to the list.
I agree that make unique key a combination of different fields,
eg.. EmailAddress + Contactlist.
or EmailAddress + Account
or even a completely Unique Identifier that will allow us to have multiple email address on different list with different accounts.
Mary Ka Powers commented
Yes please! As a distributor who markets to companies, not individuals, we are more interested in a Dealer ID than an particular email address due to people coming in going in the company.
Alternatively, join email with another field to make a unique key
Agreed. Similar problems arise since we allow users to have multiple accounts under a single email address. We are stuck sending only one user's data in fields, and it leads to a number of service issues.