ExplainerPublished
Identity resolution is the process of recognising that different identifiers, such as an email, a phone number and a device ID, belong to the same person. It turns scattered records into one view of each customer, which every audience, match and measurement depends on.
Customers don't use one identifier. The same person might be an email address in a CRM, a mobile number in an app and a device ID in an ad account. Without resolution, they look like three different people.
That fragmentation shows up everywhere: duplicate records, audiences smaller than they should be, low match rates when audiences are sent to ad platforms, and measurement that can't connect who saw a campaign with who bought.
Identity resolution links the identifiers that belong together and gives them one ID. There are two broad approaches:
The links are usually kept in an identity graph: a map of which identifiers belong to which ID, updated as data changes.
Resolving identity means handling personal data, so how it's done matters:
An identity graph is only as good as the data it was built on. Many were built on US or European data, then extended to other regions.
In Saudi Arabia, that can miss local patterns: mobile numbers written as +966 or 05, people with more than one number, and Arabic names written in Latin script in many ways (Mohammed, Muhammad, Mohamed). A graph designed around local data handles these from the start.
EleeNID resolves the emails, phone numbers and device IDs your team maps into one pseudonymous ID per person, designed around Saudi data from the start. Identifiers are hashed before they're compared, resolution runs where your data lives, and each source shows its resolution rate. See how EleeNID works.
Keep reading
Get started
Tell us which identifiers you hold and where they live. We'll go through how EleeNID would read them in place.
What happens next
Try it
410,000
People resolved
Example figures only.
