> For the complete documentation index, see [llms.txt](https://help.doctorlogic.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.doctorlogic.com/docs/apps/opportunities/click-to-call-tracking.md). # Click to Call Tracking Click to Call tracking captures a "call event" when a visitor clicks on any phone number link on your website. With Click to Call tracking our system will report that a website visitor displayed intent to contact your practice and showed a level of engagement. This will be classified as a Click to Call conversion, or CTC for short. It's important to note that the call event that is logged is a click and it may or may not result in an actual phone call being completed. Below is a representation of how Click to Call conversions will be displayed on the Opportunities dashboard.
With Click to Call tracking our system will also capture similar call events from your Google Business Profile as well. [Click here](https://help.doctorlogic.com/docs/apps/opportunities/click-to-call-tracking/google-business-profile-call-clicks) to learn more about GBP call event tracking. Finally, for customers in need of more advanced call tracking functionality, please review the details on DoctorLogic's [Premium Call Tracking feature](https://help.doctorlogic.com/docs/apps/opportunities/premium-call-tracking). --- # 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.doctorlogic.com/docs/apps/opportunities/click-to-call-tracking.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.