# dotdigital
### Identify & track dotdigital email recipients on your website
#### Step 1: Track email opens
To track mail open/reads from your dotdigital 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 campaign or template
2. Create or edit an element in where we can add our tracking pixel, usually a footer element or similar.
3. switch to HTML view, so you can ad HTML code (\)
4. paste in your email tracking pixel at the bottom of the HTML:
{% code overflow="wrap" %}
```html
```
{% endcode %}
Close and Save
**Notes:**
* Don't forget to change the DATASET ID to your own
* You can add other data fields variables as parameters by simply adding these to the pixel, eg \&companyName={{ contact.data.company }}
* For more details on advanced data fields in dotdigital see:
#### Step 2: Track email clicks 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:
In dotdigital, this can be done automatically with the advanced feature called Link tracking.
1. FIrst make sure you have the Google Analytics tracking enambled
2. Then add your parameters to the list. You can add multiple parameters but **email** is required. use @EMAIL@ as value
This will allow us to identify the individual visitors when they land on your site.
Optionally but recommended, you can add additional parameters to enrich the visitor with other information from your database.
For more details see these pages from the dotdigital documentation:
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://help.leadboxer.com/leadboxer/integrations/email/marketing-emails/dotdigital.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.
