FAQs

What is Global Name?

Global Name is a web service used to split full names, assign genders and create salutations.

Typical uses for this service are Real-time splitting and genderizing during data entry, or integration into a custom written application seamlessly (i.e., without shelling to another application).

What is Global Name available as?

Global Name is available as a web service. It is currently unavailable as an on-premise API. Global Name parsing can also be found in our SSIS Global Verify Component.

What is required to use the service?

A valid Melissa product license, the URL endpoint and an input Name (and Country) to be parsed are the minimum parts which can make up a valid request.

Is single record or batch processing available?

You can send a single REST or batches of 100 records in XML or JSON format in a single request.

Do names have to be formatted the same? Forward? Inverse?

No, names can be in different formats like John L. Smith, Smith Jr., John or Mr. John Lydon Smith Jr. PhD. and be processed simultaneously. The service will be able to distinguish first name from last name from prefix, etc. regardless of their order.

How are dual names handled?

Global Name can recognize various dual name patterns such as Mr and Mrs John Smith, Mr John & Jane Smith, and Mr. John Smith and Mrs Jane Seymour along side of records like Mr. John Smith, returning two sets of parsed output names when necessary.

Does Global Name have UTF-8 Compliance?

Global Name will also proper case extended and UTF-8 characters as well as special case known tokens.

Does Global Name detect and delete vulgar names?

Vulgar, Suspicious, and Company Indicator names will be flagged as such via response result codes, but the name is not removed.

Is there international processing?

Global Name will distinguish between extended characters and an additional input Country to return parsing across different countries and languages.

Is customization available?

Yes, there are many options such as name hint, gender aggression and salutation option which let you help the parsing engine assign parsed properties and customize how the response answers will be returned.

How often is the service updated?

Global Name Web Service is updated on a monthly basis. Updates include additional ‘name’ sources, added country support or general service updates.

What is the expected service throughput?

The expected throughput is approximately 1,500,000 records per hour.

Service Endpoint	Throughput (records / hour)
doGlobalName	1,500,000 – 2,00,000

Service factors effecting throughput

Distribution of the data. Being a Global Service, if inputs are randomly distributed over a wide range of Countries, searching for a name will require more of the underlying data to be accessed. Input data sets containing low country recognition may take longer – as the underlying data will search for records longer before it is determined to be an unknown name

Number of threads: the above benchmark is for a single thread of 100 record batches. Increasing the number of threads can greatly increase throughput. Users should thoroughly test the effects of the number of threads against network configuration to determine the most optimal usage.

Average Response Time	Average (ms / record)
Single Request	70ms
P95 Latency	80ms

Privacy

Certifications and Compliance

As a company, Melissa is fully GDPR compliant and holds various certifications. We are proud to take privacy and security very seriously, and aim to be transparent when detailing how we handle your data.

All Global Email requests are secured with HTTPS and the latest TLS.

Please refer to our compliance page for more details.

What We Store and Why

We store some minimal information from each Global Email request for logging, diagnostic, debugging, and optimization purposes.

Melissa does NOT give or sell this information to any other entity. It is all strictly for internal use.

Also, we do NOT use received emails for any marketing or advertising purpose. Again, they are only used internally for Global Email.

Aside from standard diagnostic and debugging information, Global Email does use a cache of emails. This cache stores the result of the last check on that email so that users who verify an email within a short time of another user verifying the same email can get the same results faster.

For European users, emails are additionally encrypted using a one-way hash, which means that emails are impossible to decipher and are not human-readable.

See the following sections for more details.

Outside of Europe

For users not affected by any extra privacy regulations, Global Email securely logs emails and other internal diagnostic information. As mentioned above, all Global Email requests are sent with current HTTPS and TLS encryption.

This cache is just emails with several numerical values attached to them. This is used for internal logging purposes, and more importantly to improve speed without sacrificing accuracy. There is nothing to tie any email to any individual, whether that be the owner of the email or the user who verified the email.

Europe and GDPR

As of the 25th of May 2018, the European Union implemented the General Data Protection Regulations (GDPR).

These regulations apply to anyone who processes data gathered or stored in the European Union, regardless of where the data processor is located.

Overall, GDPR obligates all data collectors and processors working in Europe or with European data to transparently collect, store, and process that data, and to do so with only the minimum amount of data needed for the task at hand.

Additionally, GDPR dictates that data systems must implement data privacy and protection by default.

For more information, see this summary of GDPR from the European Union itself, or the full text of the regulations.

Emails specifically are less sensitive compared to other personal data, such as full names or addresses. GDPR does allow companies to store emails - no encryption or other obfuscation required - as long as it is hard to connect any email to any other piece of personal information, whether internally or in the event of a breach.

Other information related to emails, namely information about domains, is not considered personal data. You may find that some requests do include contact information about the domain owner, but this information is gathered from external sources, all of which are GDPR compliant in their own right.

Interestingly, since GDPR allows companies to store unencrypted emails as long as they cannot be connected to other personal information, our method of caching outside of Europe was already GDPR compliant.

But, for Global Email specifically, we have gone beyond simple compliance.

We store information about the connection status of the MX server in the form of encrypted hashes. This means that users get the best of both worlds: the performance of our non-European email verification, and the assurance that we are more than fully GDPR compliant. As mentioned previously, all encryption is one-way.

Please do not hesitate to reach out to us with any questions regarding our GDPR compliance.

Data Across Borders

It is important to note that GDPR does allow companies to leverage data gathered and stored outside of the GDPR sphere of influence. Therefore, we use our US-hosted cache of nearly 800 million emails to bolster email verification in Europe in only a read capacity.