Skip to content
Glossary · Tracking

Identity resolution

How it works

At first, a tracking script only knows visitors: a browser with a random ID in a cookie. But one person can be several visitors, for example on their phone, on their laptop and after clearing cookies. Identity resolution links these visitors through identifiers that clearly belong to one person:

  • Email address and phone number, for example from a form
  • External IDs, such as a customer number from the CRM

When a visitor submits a form with their email address, their browser belongs to that person from then on. If the same address shows up on another device or in an update from the CRM, that's linked to them as well. The stored network of these links is called the identity graph.

Why it matters

Without identity resolution, a customer's path falls apart into fragments. The ad click on the phone and the enquiry on the laptop look like two different people, and a deal in the CRM can't be linked to any ad click. Attribution can then only work with what happened to occur in the same browser. TSO merges visitors and identifiers such as email, phone and external ID into people per project, with safeguards against wrong merges, for example on shared devices or with weak signals.

Example

During her lunch break, Anna clicks a Meta ad on her phone and looks at the offer. In the evening she searches Google for the company on her laptop and fills in the form with her email address. Three weeks later, the CRM reports a won deal with the same address.

  • Without identity resolution: the enquiry goes to Google search, the Meta click remains an anonymous visitor, and the deal isn't linked to any touchpoint.
  • With identity resolution: phone, laptop and CRM record belong to Anna. The Meta click is her first contact, and the deal can be credited to her touchpoints.

Common mistakes

  • Underestimating wrong merges: a family laptop, an office PC or test enquiries from your own agency can merge strangers. A wrong link does more damage than a missing one.
  • Not normalizing identifiers: "Anna@Example.com" and "anna@example.com" have to be recognized as the same address, and so do phone numbers written in different formats.
  • Using names as a key: two people easily share a name. Names add to a profile but don't link people.
  • Expecting miracles: someone who never leaves contact details and switches devices remains several anonymous visitors.

How TSO handles it

Articles on this topic

Related terms

From the term to clean measurement.

TSO connects ads with leads, deals and revenue and reports them back to the ad platforms.