---
schema_version: "1"
id: 8a690032e472402b8916c27a331ea2eca28f06fc148e511ab0b46eb79d0e4ebf
title: Fully Qualified Keys
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/data/264-0-0/c360_a_fully_qualified_keys.md
canonical_url: https://help.salesforce.com/s/articleView?id=data.c360_a_fully_qualified_keys.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: b572989182ef154108f959f4de9e4db337c2be76164b10a93427096698f46c29
description: Use Fully Qualified Keys (FQK) to avoid key conflicts when data from different sources are harmonized in the Data 360 data model.
products:
  - Data 360
release: "264"
---
# Fully Qualified Keys

Use Fully Qualified Keys (FQK) to avoid key conflicts when data from different sources are harmonized in the Data 360 data model.

Configure key qualifier fields for all data lake object (DLO) fields that contain a key value to use FQKs. The field can be a primary key or a foreign key field.

- **[Data Interpretation with Fully Qualified Keys](https://help.salesforce.com/s/articleView?id=data.c360_a_data_inter_fqk.htm&release=264.0.0&type=5)**  
    Fully qualified keys help to accurately interpret data ingested from different sources. Each data stream is ingested into Data 360 with its specific keys and attributes. When multiple data streams are harmonized into a single data model object (DMO), the various keys can conflict and records can have same key values. Fully qualified keys avoid conflicts by adding key qualifier fields and interpreting the data accurately.
- **[Best Practices for Fully Qualified Keys](https://help.salesforce.com/s/articleView?id=data.c360_a_key_qualifier_best_practices.htm&release=264.0.0&type=5)**  
    Use fully qualified keys (FQKs) to help Data 360 accurately interpret data ingested from different data sources.
- **[Fully Qualified Keys in Data Objects](https://help.salesforce.com/s/articleView?id=data.c360_a_dlo_dmo_key_qualifiers.htm&release=264.0.0&type=5)**  
    Data 360 adds key qualifier fields to data lake objects (DLOs) and data model objects (DMOs). Key qualifier fields can also be added when you create object relationships and object mappings between DLOs and DMOs.
- **[Fully Qualified Keys for Query API](https://help.salesforce.com/s/articleView?id=data.c360_a_query_api_key_qualifiers.htm&release=264.0.0&type=5)**  
    Use Query API to query data in Data 360. Identify key qualifier fields in a data lake object with the Data 360 Metadata API, and include key qualifier fields in all table joins to get accurate results.
- **[Configure a Key Qualifier Field](https://help.salesforce.com/s/articleView?id=data.c360_a_add_or_view_key_qualifier.htm&release=264.0.0&type=5)**  
    After creating a data stream, add key qualifiers to your data lake object (DLO) fields to create fully qualified keys (FQK). Configure key qualifiers for all DLO fields that contain either a primary or foreign key. You can add up to 20 active key qualifiers. A key qualifier is active when it's used for a DLO field. Data 360 automatically adds and removes key qualifiers to and from data model object (DMO) fields. You can't edit these system fields.
- **[Remove or Delete a Key Qualifier](https://help.salesforce.com/s/articleView?id=data.c360_a_remove_and_delete_key_qualifier.htm&release=264.0.0&type=5)**  
    To reduce clutter and avoid reaching your org's limit for key qualifiers, remove and delete unnecessary key qualifiers from the system. To delete a key qualifier, first remove it from all the data lake object (DLO) fields that it’s associated with and then delete it. You can also just remove a key qualifier from a DLO field but not delete it from the system. Removing a key qualifier from a DLO field can potentially affect the accuracy of calculated insights, segments, activations, and API queries.