> 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/references/faq.md).

# FAQ and troubleshooting

Short answers to common questions about eMarketeer, including features eMarketeer doesn't have and what to do instead.

Short answers to common questions, with links to the full guides. Click a question to see the answer.

## Contacts

<details>

<summary>Does eMarketeer delete contacts automatically?</summary>

No. eMarketeer never deletes contacts on its own, and no Journey step or automation can delete them. A contact is only deleted when a user deletes it, for example with the [bulk actions tool](https://support.emarketeer.com/guides/contacts-lists/bulk-actions-tool.md), or when an integration your organisation has built deletes it through the [eMarketeer API](https://support.emarketeer.com/references/apis-developer/api-endpoints-overview.md). Deleted contacts can't be restored from within eMarketeer. If you've deleted contacts by mistake, contact support.

If a contact seems to be missing, it usually still exists but isn't where you're looking:

* Search for the contact's email address in the **Contacts** section.
* Check whether the contact was removed from a contact list, for example by a Journey's [Contact List](https://support.emarketeer.com/guides/journeys/journey-steps/journey-step-contact-list.md) step or a bulk action. Removing a contact from a list doesn't delete it.
* If you're looking in a contact filter, check whether the contact still matches its conditions.

If the contact exists but didn't receive your email, see [Identifying why an email was not received](https://support.emarketeer.com/guides/guides/email-content/identify-email-not-recieved.md).

</details>

<details>

<summary>What happens to reports when I delete a contact?</summary>

Permanently deleting a contact doesn't change the counters in your reports, such as emails sent or submitted form answers. It doesn't change metrics such as open rate or click-through rate either. But the contact is removed everywhere it used to be referenced.

* **Emails:** if a contact opened an email and you later delete the contact, the **Opened** counter doesn't go down. You can still click the number, but the contact no longer shows in the list of contacts who opened the email.
* **Forms:** the contact's form engagement is removed, but the submitted answers remain. This means the data a deleted contact submitted still exists in the form report. You no longer see who submitted it, unless the answers themselves include the respondent's contact details.

</details>

<details>

<summary>Can I find contacts with an invalid email address?</summary>

No. There's no filter for contacts with an [invalid email address](https://support.emarketeer.com/references/glossary.md#invalid-email-address). To find them, export your contacts and check the addresses in an external tool, such as a spreadsheet.

</details>

<details>

<summary>Can I create companies in eMarketeer?</summary>

No. Companies aren't records of their own in eMarketeer, so you can't create them or search for them. Instead, eMarketeer builds a company profile automatically from the domain of a contact's email address, as part of enriching the contact.

To see a contact's company profile, open the contact card, go to the **Overview** tab and click **View company**. See [The company card](https://support.emarketeer.com/guides/lead-board-scoring/the-lead-board.md#the-company-card).

</details>

## Leads

<details>

<summary>Can I add a contact to the lead board manually?</summary>

Yes. Open the contact card, go to the **Lead** tab and make the contact a lead. You choose the lead stream to add the lead to. See [The lead board](https://support.emarketeer.com/guides/lead-board-scoring/the-lead-board.md).

</details>

<details>

<summary>Can I move a lead to another sales team's lead board?</summary>

Not directly. A lead board shows the leads from the [lead streams](https://support.emarketeer.com/guides/lead-board-scoring/lead-streams.md) that deliver to its sales team. To send a lead to another team, change the lead stream instead.

For example, a contact fills in your English form and matches a lead stream for your English sales team, but the contact is clearly French. On the **Lead** tab of the contact card, remove the contact from the lead board, so it's no longer a lead. Then make the contact a lead again from the same tab, and choose the lead stream that delivers to your French sales team. The lead then appears on that team's lead board.

</details>

## Journeys

<details>

<summary>Can I test a Journey?</summary>

No. The Journey builder has no test mode. To try a Journey on a single contact, turn on **Make Journey available on Contact Card** in the [Journey settings](https://support.emarketeer.com/guides/journeys/creating-your-first-journey.md#make-journey-available-on-contact-card). You can then start the Journey for one contact from their contact card, without the contact having to match the starting point conditions.

The steps run for real, so use a test contact with your own email address.

</details>

## Emails

<details>

<summary>How do I set the height of an image in an email?</summary>

You can't set it directly. Each image block in the email editor shows a recommended width, and the height follows from that width and the image's proportions. To make an image taller, crop its sides so the image has the proportions you want at the recommended width. See [Upload an image](https://support.emarketeer.com/getting-started/campaign-basics/basics-creating-email.md#upload-an-image).

</details>

<details>

<summary>Can I attach a file to an email?</summary>

No. eMarketeer doesn't support email attachments. Instead, upload the file to **Files** in eMarketeer and link to it from the email with the **Link to file** option in the link menu. See [Add a button with a link](https://support.emarketeer.com/getting-started/campaign-basics/basics-creating-email.md#add-a-button-with-a-link).

</details>

<details>

<summary>Can I create plain text emails in eMarketeer?</summary>

No. eMarketeer doesn't support plain-text-only emails. Every email you create in eMarketeer is sent as a multipart email, with both an HTML version and a plain text version.

If you want an email that looks simple, like a plain text email, choose the **Email - Plain** template when you create the email. It has a minimal design, but it's still an HTML email, not a true plain text email. See [Fill in settings, choose a template, create the email](https://support.emarketeer.com/getting-started/campaign-basics/basics-creating-email.md#fill-in-settings-choose-a-template-create-the-email).

</details>

<details>

<summary>Can I save or download an email, for example as a PDF?</summary>

No. eMarketeer can't save or download emails. Instead, open the email's [Read on web](https://support.emarketeer.com/references/references/email/read-on-web.md) page in your browser and save that page as a PDF:

1. Send a test of the email to yourself and click its read on web link. If the email doesn't have one, add it first. See [How to insert a read on web link](https://support.emarketeer.com/references/references/email/read-on-web.md#how-to-insert-a-read-on-web-link).
2. Press **Ctrl+P** (**Cmd+P** on a Mac) to print the page.
3. As the printer, choose **Save as PDF**, then click **Save**.

</details>

## API

<details>

<summary>Can I still use the Legacy API 1.0?</summary>

No. The Legacy API 1.0 has been deprecated and is no longer in use. Use the current eMarketeer REST API instead. See [API](https://support.emarketeer.com/references/apis-developer.md) for how it works and where to find your API key, and [API endpoints overview](https://support.emarketeer.com/references/apis-developer/api-endpoints-overview.md) for the available endpoints.

</details>


---

# 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/references/faq.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.
