> For the complete documentation index, see [llms.txt](https://help.leadboxer.com/leadboxer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.leadboxer.com/leadboxer/using-the-app/elements/import-and-export/custom-properties.md). # Custom Properties Add your own data to the mix ### Adding lead /client or customer data to LeadBoxer I want to submit information to LeadBoxer, is this possible?\ For example, I have a database with a list of properties, and I would like to add the information from the database to my LeadBoxer leads. In other words, can information known about a visitor (lead) to a site tracked by LeadBoxer be sent to LeadBoxer and displayed on the leadboard? The answer is yes! The way to send data to leadboxer is along with an event that is being measured, for example a login event. Data can be submitted to LeadBoxer in the form of ‘Properties’. The engine is event-based, so you need to send properties when an event is triggered, ie logging in to a site. When a login-event occurs, you grab all the information from your db that you think is interesting for that login, and send it along to LeadBoxer. The document tagging leads with properties explains how to do this in technical terms. In other words, how to get things into the leadboard with an event (download or pageview). --- # 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://help.leadboxer.com/leadboxer/using-the-app/elements/import-and-export/custom-properties.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.