> For the complete documentation index, see [llms.txt](https://support.emarketeer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.emarketeer.com/changelog/2022-and-earlier.md).

# 2022 and earlier

{% updates format="full" %}
{% update date="2022-11-26" tags="feature,improvement,fix" %}

## Email templates, lead score summary, and campaign fields

* **New email templates** — holiday templates built on new root code for better display across more email clients. Includes more content blocks, higher image resolution, and a new settings box for preheader, Google font, and social share preview.
* **Lead score summary** — see how each contact earned its current score. A "Score summary" tab on the contact card lists the fulfilled score rules and shows a score timeline.
* **Rich text editor in campaign fields** — format campaign field text with bold, italics, hyperlinks, and more.
* **Sort campaign fields** — reorder campaign fields with drag-and-drop and add field descriptions.
* File uploads now accept more extensions, including ics and woff2.

<details>

<summary>Fixed</summary>

* SuperOffice CRM contact imports fix.
* Fixes to handling empty default fields in SuperOffice CRM.
* Fixed forms that resulted in a blank thank-you page when the "Note" field was left empty.
* Minor bug fixes in lead scoring calculations.
* The user interface language now matches the browser language.

</details>
{% endupdate %}

{% update date="2022-03-28" tags="feature" %}

## Clone block in email editor and more campaign field types

* **Clone block** — copy any content block while building an email. Hover over the block and click the duplicate icon.
* **More campaign field types** — text, text area, rich text, date and time, images, droplist. Date and time of the latest update is now available in the API.
* **Sort campaign fields** with drag-and-drop; add field descriptions to keep an overview.
  {% endupdate %}
  {% endupdates %}


---

# 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://support.emarketeer.com/changelog/2022-and-earlier.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.