Resolve Overview

Resolve is FullContact’s Identity Resolution solution. Resolve uses the Identity Graph to map those identifiers to a single individual. The result is a unique, persistent identifier called a PersonID.

You can use Resolve to link your CRM, call center, mailing address, and other customer information from various platforms to get real-time, two-way consolidation and updating of customer information with high match rates and confidence levels.

What can you do with Resolve?

Unify your fragmented customer data points down to a persistent PersonID.

Resolve accepts fragmented user, customer and prospect data as multi-field identifiers, matching against the FullContact Identity Graph to recognize them down to a Person level. This match is expressed in what FullContact calls the PersonID, which is customer-scoped, unique per person, persistent and portable, and of course secure. Connections between customer and user databases can be established to the PersonID through FullContact Identity Streme, allowing FullContact customers to provide a unified client experience and journey.

Benefits of resolving identifiers to a PersonID:

Seamlessly stitch together customer and prospect data across your ecosystem
Recognize your customers and prospects in real-time, across numerous channels
To de-duplicate customer records down to a single person

Map fragmented customer records to FullContact’s persistent PersonID in your own Identity Streme

In addition to the PersonID, Resolve supports the ability to map custom identifiers, such as a customerID, loyaltyID, CDPID and any other internal database ID to the respective user/customer/prospect data (multi-field). You can also leverage this feature to associate analytics data (such as visitIDs and/or orderIDs) as you can map multiple identifiers to a single person.

Benefits of mapping custom identifiers to user/prospect data:

Immediately know which data set a person is a part of at the moment of resolution, based on which RecordIDs are returned
Optimize your first party data asset by stitching together customer records down to a unique PersonID for each of your customers
More securely query FullContact APIs with non-sensitive input parameters by using either RecordIDs or PersonIDs
Protect your customer’s PII by leveraging FullContact’s PersonID to access the entire Identity Graph

Recognize anonymous website traffic by leveraging Customer Recognition Tags

Resolve real-time traffic on your website down to a personID using an embedded webtag provided by FullContact.

Offer a prospect or customer a personalized experience, in-the-moment based relevant interests and affinities tied to a PersonID

A Simple Resolve API Use Case

Within the FullContact Platform, you’ll find a high-level demonstration of resolve in action . This guide walks through a customer journey and shows how FullContact’s Resolve offering can help identify and manage client and prospect data. Additionally, the demo walks through using Resolve to serve curated experiences to your customers.

What is our Resolve success rate?

Our average match rate for Resolve is 93%. Deduplication or overlapping records rate is dependent on the customer records. You can expect an average of 10-15% of duplicate records.

Can PersonIDs (PIDs) change? Why would this occur?

With our Identity Graph constantly updating, there are typically two instances when PID changes occur:

Merge Instances - this occurs when two or more PIDs that were previously returned based on inputted contact fragments are now found to be connected inside our Identity Graph.
Split Instances - this occurs when one PID has been determined to have connected two or more individuals together inside our Identity Graph. This is generally seen in household relationship use cases. In split instances, it is recommended that the first PID in the list should be used for ongoing customer recognition.