AbiliTec IDs are identifiers that are tied to a record in the AbiliTec offline identity graph. They allow you to identify and consolidate records across multiple systems. When you make API calls with two distinct sets of PII, and AbiliTec reconciles them to the same entity, then the same AbiliTec ID is returned for each request.
You can structure the API call to return only the best match for the input data, or you can choose to receive multiple identifiers for input data that matches to multiple identifiers.
When the AbiliTec ID is returned, you don't see the underlying ID, only a version of the ID. A Client Domain identifier will have a different value for each client even if the underlying LiveRamp Domain identifier is the same. This aids client privacy and reduces the probability of collusion.
There are three types of AbiliTec IDs:
- A ConsumerLink represents an individual.
- An AddressLink represents a site or physical location.
- A HouseholdLink represents adults living together at the same location who exhibit a persistent relationship.
You can specify what AbiliTec ID type is returned by calling specific endpoints and including parameters such as the document class parameter.
There are two versions of AbiliTec IDs:
- Maintained versions
- Derived versions
When you make an AbiliTec API call and there is a match in the AbiliTec Identity Graph, a maintained AbiliTec ID is returned. This version of an AbiliTec ID is maintained and is persistent.
Maintained IDs can change over time, due to new information being added to the identity graph. Running your data through AbiliTec allows you to update the maintained AbiliTec IDs for records that have changed.
When you make an AbiliTec API call and there isn't a match in the AbiliTec Identity Graph, a derived AbiliTec ID version is returned. AbiliTec IDs that are derived versions are algorithmically derived and persistent—if you input the exact same PII string, the response will show the same derived AbiliTec ID. Derived AbiliTec IDs are not maintained in the identity graph.
Derived versions are returned so that there is an identifier for every record. Because they are algorithmically derived, the exact same input data must be sent to receive the same derived ID.
A derived AbiliTec ID can be updated to a maintained AbiliTec ID as new data is added to the identity graph. Running your data through AbiliTec allows you to update the derived AbiliTec IDs for records that have changed.
AbiliTec IDs are returned in a "Link" format, which identifies the Link type (ConsumerLink, AddressLink, or HouseholdLink) and the versions (maintained or derived).
What about DocIDs?
The DocIDs that are returned function as LiveRamp internal identifiers and can be ignored.
AbiliTec Links have a 16-byte alphanumeric structure that indicates the AbiliTec customer (the “domain”), the country code, the ID type and version, and the entity value.
The Link format has 4 components:
|Domain||The 4-digit code that uniquely identifies the AbiliTec customer.|
|Country Code||The 2-digit country code for the underlying data used in the matching. For maintained Links, this will be “US” for United States.|
|Link Type||The 2-digit code for the link types:|
01: Maintained ConsumerLink
02: Maintained ConsumerLink
03: Maintained AddressLink
08: Maintained HouseholdLink
11: Derived ConsumerLink
13: Derived AddressLink
18: Derived HouseholdLink
|Value||The 8-digit alphanumeric ID value that uniquely identifies the associated data.|
Maintained ConsumerLink Link Type
While there are two link type codes for a maintained ConsumerLink - 01 and 02 - these do not have any practical meaning. These codes were historically used to differentiate links for an internal use case, but today both prefixes are used in the creation of ConsumerLinks and can be treated as equivalent, both representing maintained individuals. Note that link DDDDCC0100000123 and DDDDCC0200000123 represent different people!
Updated almost 2 years ago