> 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/spotler-mail+.md).

# Spotler mail+

Formerly known as Spotler or MailPlus

### 1. Track Spotler Email opens or reads:

1. Add a new HTML or code block to the footer of your template

   <figure><img src="https://3748765316-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy0YIHtmtqLfLnxMS5laM%2Fuploads%2Fgit-blob-4b0bfd239770b8e1ace1e0bb9f4d57757826bb37%2FSpotler%20(2).png?alt=media" alt=""><figcaption></figcaption></figure>
2. Clcik the HTML/code view and add the tracking code

   <figure><img src="https://3748765316-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy0YIHtmtqLfLnxMS5laM%2Fuploads%2Fgit-blob-f826009068acb7fc44b826f2b1283d67d9b5e70a%2FSpotler%20(3).png?alt=media" alt=""><figcaption></figcaption></figure>

{% code overflow="wrap" %}

```html
<img src="https://track.leadboxer.com/log?datasetId=YOUR-DATASET-ID&campaign=Spotler-Campaign-[date:en|dd-MM-yyyy|now]&email={email}&firstName={Voornaam}&lastName={Achternaam}&companyName={Bedrijfsnaam}">
```

{% endcode %}

{% hint style="info" %}
Make sure you change YOUR-DATASET-ID in above snippet.

Unfortunatly, Spotler does not have the option to dynamically use the title of the email in the campaign variable, meaning you will need to either use a generic campaign name with a dynamically generated date or manually change this for each email that is send out.
{% endhint %}

### 2. Tracking Spotler clicks

First we recommend you enable the Google Analytics integration, so that UTM tags are added to all the URLs

Secondly, we need to add identification parameters to every URL. This can be accomplished by using the 'Extra parameters' feature. We recommend to add the email and company parameter.

<figure><img src="https://3748765316-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy0YIHtmtqLfLnxMS5laM%2Fuploads%2Fgit-blob-d09dbe1099743d983ec9615af6487f1bb5cae9b7%2FSpotler%20(4).png?alt=media" alt=""><figcaption></figcaption></figure>

Even though it looks like it is enabled for for all emails like this, we found It might be necessary to manually enable this again in the emails/ newsletters themselves.

Click on the Analytics button at the top of the email

<figure><img src="https://3748765316-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy0YIHtmtqLfLnxMS5laM%2Fuploads%2Fgit-blob-6c49a815d12d42f03b0abee974220f38a3f52066%2FSpotler%20(1)%20(1).png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3748765316-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy0YIHtmtqLfLnxMS5laM%2Fuploads%2Fgit-blob-5787f49978391676ae538a9a55a8e460598f93a4%2FSpotler%20(5).png?alt=media" alt=""><figcaption></figcaption></figure>

The Extra parameters feature only allows for 2 additional parameters, so if you need more you can still manually add them like this:

{% code overflow="wrap" %}

```url
https://www.leadboxer.com?firstName={vNaam}&lastName={aNaam}&email={email}&companyName={bedrijf}
```

{% 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/spotler-mail+.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.
