> 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/capture-website-and-email/email/marketing-emails/hubspot.md).
# HubSpot
{% hint style="info" %}
Make sure you also enable our [HubSpot Integration](/leadboxer/integrations/other/hubspot.md), as this will sync all your existing contacts with LeadBoxer and allow you to enrich your HubSpot contacts with LeadBoxers rich firmographic and marketing data.
{% endhint %}
Tracking HubSpot marketing emails is easy.
To track email open events, either add this tracking image to your template as a piece of HTML
{% code overflow="wrap" %}
```html
```
{% endcode %}
Alternatively, you can add an image from an URL like this:
 
***
Make sure you enable the HubSpot integration so we can connect your HubSpot contacts with LeadBoxer leads.
See instructions here:
Optionally, you can also identify your HubSpot contacts using merge tags on the links to your site.
To track link clicks and identify these readers on our site you need to be appended with a parameter like in this example:
{% code overflow="wrap" %}
```url
https://www.leadboxer.com/?email={{contact.email}}&firstName={{contact.firstname}}&lastName={{contact.lastname}}&companyName={{company.name}}
```
{% endcode %}
---
# 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/capture-website-and-email/email/marketing-emails/hubspot.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.