> 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/apollo.io.md).
# Apollo.io
### Identify & track Apollo email recipients on your website
#### Step 1: Track email opens
To track mail open/reads from your Apollo audience in LeadBoxer, you need to add a LeadBoxer tracking pixel to your campaigns or templates.
Here are the steps needed for adding the tracking pixel:
1. Go to your sequence templates
2. Choose the mail template you want to track
3. Switch to HTML view, so you can ad HTML code (< >)
4. Paste your email tracking pixel into the bottom of the HTML:
{% code overflow="wrap" %}
```html
```
{% endcode %}
5. Save
**Notes:**
* Don't forget to change the DATASET ID to your own.
* You can add additional data fields variables as parameters by simply adding these to the pixel, eg \&companyName={{company}}
* For more details on advanced data fields in Apollo see:
*
### Step 2: Track email clicks (click-thrus) and identify prospects on your site
To track email clicks, you need to modify the links inside your email campaigns and add this parameter to the URL of the link:
**\&email={{email}}**
This will allow us to identify the individual visitors when they land on your site.
Optional, but recommended; add additional parameters to enrich visitors with additional information from your database:
**example URL**
{% code overflow="wrap" %}
```url
https://www.YOURDOMAINNAME.com/my-landing-page/?firstName={{first_name}}&lastName={{last_name}}&email={{email}}&companyName={{company}}
```
{% endcode %}
NOTE: remember to update the landing page with your url.\
Tip: Best practice is to test before sending out a mass email
---
# 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/apollo.io.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.
.png?alt=media)
.png?alt=media)