> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/collect-data/reveal/chord-reveal-data-attribute-definitions.md). # Chord Reveal data attribute definitions {% hint style="info" %} Chord Reveal will appear as a “group label” inside the existing Activities, Sessions, and Anonymous explores. Note: The data inside the Sessions, Activities, and Anonymous explores will only work when they are associated with data from Chord CDP. {% endhint %} ## Chord Reveal profile fields * **First Identifier Attempt At**: Indicates when the first reveal attempt occurred. * **Last Identifier Attempt At**: Indicates when the last reveal attempt occurred. * **First Identified At**: Indicates when the anonymous user was first revealed. * **Personal Email**: The personal email address of the identified user. * **Business Email**: The professional or work email address of the identified user. * **Age Range**: The estimated age range of the identified user (e.g., '25-34'). * **Company Address**: The full street address of the user's company. * **Company City**: The city where the user's company is located. * **Company Domain**: The website domain of the user's company. * **Company Employee Count**: The estimated number of employees at the user's company. * **Company Linkedin URL**: The URL for the user's company LinkedIn page. * **Company NAICS**: The NAICS (North American Industry Classification System) code for the company's industry. * **Company Name**: The legal name of the user's company. * **Company Phone**: The general phone number for the user's company. * **Company Revenue**: The estimated annual revenue of the user's company. * **Company SIC**: The SIC (Standard Industrial Classification) code for the company's industry. * **Company State**: The state or province where the user's company is located. * **Company Zip**: The postal code for the user's company. * **Department**: The department the user likely works in at their company (e.g., 'Marketing', 'Engineering'). * **First Name**: The first name of the identified user. * **Gender**: The gender of the identified user. * **Homeowner**: Indicates whether the user is a homeowner ('Yes'/'No'). * **Income Range**: The estimated household income range of the identified user. * **Job Title**: The user's job title at their company (e.g., 'Marketing Manager'). * **Ip**: The IP address of the user from which the enrichment was triggered. * **Job Title 2**: *No description provided.* * **Last Name**: The last name of the identified user. * **Linkedin URL**: The URL for the user's personal LinkedIn profile. * **Married**: Indicates the marital status of the user ('Yes'/'No'). * **Mobile Phone**: The mobile phone number of the identified user. * **Net Worth**: The estimated net worth of the identified user. * **Personal City**: The city where the user resides. * **Personal State**: The state or province where the user resides. * **Personal Zip**: The personal postal code of the user. * **Personal Zip4**: The extended 4-digit postal code (ZIP+4) for the user's personal address. * **Primary Industry**: The primary industry in which the user works. * **Professional Address**: The professional or business street address of the user. * **Professional City**: The city of the user's professional address. * **Professional State**: The state or province of the user's professional address. * **Professional Zip**: The postal code of the user's professional address. * **Professional Zip4**: The extended 4-digit postal code (ZIP+4) for the user's professional address. * **Referrer URL**: The URL of the page that referred the user to the site, if available. * **Seniority Level**: The user's seniority level within their company (e.g., 'Entry', 'Senior', 'C-Level'). * **Main Email**: Declares a primary email for the user. It prioritizes the personal email over the business email if both are available. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.chord.co/collect-data/reveal/chord-reveal-data-attribute-definitions.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.