> 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/integrations/other/tracking-calendly-conversions-on-your-site.md).

# Calendly

## Tracking Calendly Conversions on your site

If you are using Calendly to let people schedule meetings or appointments on your site, you can use LeadBoxer to identify these leads and see all their behaviour.

Here is what you need to do:

* Make sure you are using the Pro version of Calendly
* in your event settings, open the Confirmation page element and set it to redirect to a confirmation page and make sure to enable the "pass event details.." checkbox. This will add all the event details to the URL as parameters.
* On your site, create this confirmation page and make sure the LeadBoxer tracking pixel is installed
* You will need to add some javascript to grab the values from the URL and pass these to LeadBoxer:

```
<script>
var url_string = window.location.href
var url = new URL(url_string);
var invitee_full_name = url.searchParams.get("invitee_full_name");
var invitee_email = url.searchParams.get("invitee_email");
var answer_1 = url.searchParams.get("answer_1");
var answer_2 = url.searchParams.get("answer_2");
var answer_3 = url.searchParams.get("answer_3");
  
setTimeout(function(){ 
  if (invitee_email != null) {
	var map = new OTMap();    
	map.put("name", invitee_full_name);    
	map.put("email", invitee_email); <br>
	// add any additional fields like this
	map.put("companyName", answer_1); 
	map.put("title", answer_2);
	map.put("phoneNumber", answer_3);
	  
	OTLogService.sendEvent("meeting booked", map, false); 
	};
}, 1000);  


</script>
```

Thats it!\
You can now find these leads easily by setting a URL filter on your Confirmation page URL

![](https://d33v4339jhl8k0.cloudfront.net/docs/assets/565e1cb7c697915b26a5c214/images/5fc274364cedfd00165b4b97/file-fP060YlZn6.png)

Still need help? [Contact us](mailto:hello@leadboxer.com)


---

# 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/integrations/other/tracking-calendly-conversions-on-your-site.md?ask=<question>&goal=<user_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.