We used to use BriteVerify as a stand alone tool but now have it as part of the Everest platform.
Are you bulk loading list or using the API?
We have mostly bult loaded lists every now and then and try recheck our whole database twice a year, we have recently started testing real time email address check through the API in one of our smaller markets which looks to be working well.
We primarily use BriteVerify for data we need to import into our CRM or email automation system (Acoustic). These are usually done via bulk upload, but occasionally we'll use the API to do one-off verifications. These could range from a few hundred addresses to 300,000 (when we've brought over legacy data from older systems). We've found that any time we import data that is 2 years old or older, we see a significant number of invalid addresses. We are B2B, and it makes sense, particularly with the pandemic and so much flux in the global jobs market. Being able to remove invalid addresses before we import keeps our data cleaner, but also makes sure our deliverability and sending reputation stays healthy.
I use the bulk load and the option via DemandTools. Depends on how I receive the data and where it will reside. I run this every day and Marketing/Sales has become very reliant on the information!
We use it every day! Myself and another user in Marketing field requests, along with our own needs, to append/load/update data on a daily basis. We use it to standardize our data and keep the email addresses verified (#Briteverify).
As soon as the SDFC window is open on my computer, the DemandTools is opened next.
One of the best values of DT is I use it to match data from other systems and audit the information every month. Without it I would be at least two weeks manually reviewing using spreadsheets. Now I can complete it in about 2 days. This includes 100k+ of data rows.
I also use it to load financial data which has approx 50 fields per record. The scenarios keep me organized and I can quickly load the information.
I have survived 15+ years within SFDC thanks to DemandTools!
