> For the complete documentation index, see [llms.txt](https://docs.jentis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jentis.com/jentis-dcp-elements/tools/what-is-a-tool-instance.md). # What is a Connector Instance? A connector instance is used to define the properties of a service that you want to enable using the JENTIS Data Capturing platform. Connectors, in this case, refer to partner networks and databases such as Facebook, Google Ads or Google Analytics. Additionally, a connector can also be a configuration for a custom endpoint that your JTM server needs to interact with. A configuration instance of a defined connector is referred to as a "connector instance configuration". You can have multiple configuration instances of the same connector in your JENTIS DCP, for example, "Google Analytics Europe" and "Google Analytics US" to cater to different configurations per region. The most important wording in short: * **Connector**: A service definition in JENTIS Data Capturing Platform, ie. “GA4”. * **Connector Configuration** (or *Connector Instance*): A configuration of a connector in your account with a certain purpose, ie. “GA4 - [website.com](http://website.com)”. You can have multiple connector instances of the same connector configured in your account. --- # 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.jentis.com/jentis-dcp-elements/tools/what-is-a-tool-instance.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.