# First-party data | 121 CRM > A plain-English definition of First-party data, with a practical CRM example, related terms, common misunderstandings and implementation questions. First-party data means information an organisation collects directly through its own interactions and channels. The meaning is useful only when the business agrees how the term appears in its own records, decisions and customer journey. ## First-party data in a customer record Fictional example using Harbour Learning, an independent training provider. ## Capabilities explained ### Contacts Stores a person or lead with contact details, activity, ownership and related records. **How it works:** Stores or organises supported business data under configured fields, permissions and record rules. **Why a business would use it:** Gives a team one place to understand who a customer is and what has happened. **Limitations:** The platform does not make imported, duplicated or incomplete data accurate without review. **Human responsibility:** A data owner must define the record model and resolve quality, ownership and access exceptions. ### Forms Collects structured visitor details and maps supported responses into CRM records and workflows. **How it works:** Publishes or collects information through a configured visitor-facing page, form or content experience. **Why a business would use it:** Turns an enquiry into usable data instead of an unstructured email. **Limitations:** Generated or templated content is not automatically accurate, accessible, compliant or ready to publish. **Human responsibility:** A person must review content, test the journey and explicitly publish or change live assets. ### Conversations inbox Brings supported connected message threads into a shared operational inbox. **How it works:** Handles an eligible customer interaction through a configured inbox, number or connected channel. **Why a business would use it:** Helps a team see the customer history and coordinate replies from one working view. **Limitations:** Delivery, message types, geographic coverage, approval and charges vary by channel and provider. **Human responsibility:** A person must own sensitive conversations, failed delivery and any situation outside the approved script. ### Import and export Moves supported records through structured files, with mapping and validation needed before relying on the result. **How it works:** Stores or organises supported business data under configured fields, permissions and record rules. **Why a business would use it:** Supports controlled migration and operational extracts when the data is prepared and reconciled. **Limitations:** The platform does not make imported, duplicated or incomplete data accurate without review. Bulk migration requires mapping and reconciliation; do not treat a completed import as proof of accuracy or reversibility. **Human responsibility:** A data owner must define the record model and resolve quality, ownership and access exceptions. ## What first-party data means In this glossary, first-party data is information an organisation collects directly through its own interactions and channels. Different suppliers may label fields differently, so the team should document its working definition rather than relying on a menu label alone. ### The essential idea First-party data helps people describe a particular part of customer work consistently. Its value comes from a shared definition and an action or decision that follows from it. ### What it is not First-party data is not third-party data obtained from another organisation or external source. Keeping those ideas separate prevents reports, workflows and handovers from combining records that mean different things. ### Why the definition matters If two people use first-party data differently, counts and automation can appear precise while describing inconsistent situations. Agree the rule before measuring or triggering action. ## First-party data at Harbour Learning Harbour Learning uses the term in one bounded workflow. The example shows the definition in use without asserting a fixed 121 configuration. ### The situation Harbour Learning receives an enquiry through its website. A record is created with the source, contact details provided and a named owner for the next review. ### The classification The owner applies the written first-party data definition to the facts available. If information is missing or the case is unusual, it is held for a person rather than classified by guesswork. ### The consequence The recorded term changes what appears in the team view, which checks apply and what next action is expected. The team can later inspect the original facts and decision. ## Questions to settle before using first-party data A glossary definition is a starting point. Configuration still needs an owner, boundaries and realistic testing. ### Which record owns it? Decide whether first-party data belongs on a contact, company, opportunity, activity or another record. Avoid copying the same value into several places without a clear source of truth. ### Who may change it? Set the role allowed to create or change the value and the evidence they should use. Restrict consequential or sensitive changes to appropriate people. ### What happens next? Document any view, task, workflow or report that depends on first-party data. Test ordinary, missing, duplicate and exceptional cases before relying on the rule. ## Keep first-party data distinct from neighbouring terms Clear language reduces configuration mistakes and makes management reporting easier to challenge constructively. ### Use examples Keep two or three fictional examples that meet the definition and one that does not. Examples often reveal ambiguity faster than a longer abstract definition. ### Align the reports Check that dashboard labels and filters use the same definition. A report should state its population, period, exclusions and data-quality limits. ### Review after change Revisit the definition when the customer journey, services, data model or responsibilities change. Update dependent workflows and reports together. ## Frequently asked questions ### Is first-party data defined the same way in every CRM? No. The underlying idea may be common, but suppliers and businesses can use different labels and rules. Record the working definition used by your team. ### Can first-party data trigger automation? It may be used in configured rules where supported, but the definition, data quality, entitlement, timing, exceptions and human responsibilities must be checked before reliance. ### How should we introduce first-party data to staff? Explain the definition with examples, show where it is recorded, state who can change it and make clear what action or report depends on it. ### Does the first-party data definition confirm the configuration in a 121 account? No. It explains public concepts using evidenced product building blocks. Live fields, permissions, workflows and plan availability require separate verification. ## Related CRM pages - [/crm/guides](https://121.direct/crm/guides) - [/crm/guides/what-is-a-crm](https://121.direct/crm/guides/what-is-a-crm) - [/crm/features/customer-management](https://121.direct/crm/features/customer-management) - [/crm/glossary/crm](https://121.direct/crm/glossary/crm) This Markdown alternative contains public product information only. It provides no access to CRM accounts, records, credentials or payment execution.