> For the complete documentation index, see [llms.txt](https://doc.batch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.batch.com/guides-and-best-practices/email-deliverability/reputation-and-performance-monitoring/inbox-placement/category-tabs-gmail-apple-mail-outlook...-vs.-the-spam-folder-two-different-things.md).
# Category Tabs (Gmail, Apple Mail, Outlook...) vs. the Spam Folder: Two Different Things
Understand the difference between delivery and deliverability, and why landing in a category tab isn't the same as landing in spam.
An email landing in a category tab, such as Gmail's Promotions tab or a similar sort in Apple Mail or Outlook, doesn't have a deliverability problem. This is a frequent point of confusion, and it sometimes leads to the wrong fix, like switching an email to transactional for the sole purpose of trying to "escape" that tab.
{% hint style="info" %}
**Delivery** and **deliverability** are two different things:
* **Delivery**: did the email reach the recipient's mail server at all? An email that lands in the spam folder is still delivered (100% delivery). An email that's rejected outright (a bounce) is not (0% delivery).
* **Deliverability**: where the email ends up once delivered. Landing in the spam folder is poor deliverability. Landing in the inbox, in any of its tabs (primary, promotions, social...), is good deliverability.
{% endhint %}
An email in the spam folder is technically delivered, just with poor deliverability. An email sorted into a category tab is both delivered and successfully placed in the inbox: it's simply organized differently once there.
{% hint style="danger" %}
Landing in a category tab is not a bounce, not a spam complaint, and not a reputation signal. Treating tab placement and spam foldering as the same problem leads to the wrong diagnosis, and sometimes to classification decisions (marketing vs. transactional) made for the wrong reasons.
{% endhint %}
### Two distinct mechanisms
Category tabs and the spam folder are driven by different signals and don't carry the same consequences:
| | Category tabs (Promotions, Social...) | Spam folder |
| ----------------------------- | ------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------- |
| What it is | A sort within the recipient's primary inbox, used by several providers (Gmail, Apple Mail, Outlook...) | The email is delivered, but categorized as spam and hidden from the default view |
| What drives it | Message content, structure, your recipient's engagement history with you | Sending reputation, authentication (SPF/DKIM/DMARC), complaint rate |
| Is it a deliverability issue? | No, the email is categorized as expected | Yes |
| Can the recipient see it? | Yes, in a dedicated tab | No, unless they check their spam folder |
### Why switching to transactional doesn't change this classification
"**Transactional**" vs. "**marketing**" is a classification made on Batch's side (consent requirements, unsubscribe rules, legal framing): it isn't a signal sent to the mailbox provider that determines tab placement. This sorting is based on your message's content and engagement behavior, not on how the send is labeled internally on your account.
{% hint style="danger" %}
Reclassifying an email with genuinely promotional content as "transactional" to try to escape a category tab creates a compliance risk, since the content no longer matches the declared purpose, with no guarantee it changes how the mailbox provider sorts it.
{% endhint %}
### What actually drives this sort
This sorting comes down to a few concrete signals:
* The content and structure of your message (tone, formatting, promotional calls to action)
* Your recipient's engagement history with you
* The recipient's own habits with that tab
### What you can do
* Don't try to influence tab placement through your Batch marketing/transactional classification: it's the wrong lever.
* Focus on real engagement: sending to genuinely engaged segments and keeping content relevant matters more than the tab itself.
* Remember that landing in a category tab isn't necessarily bad: it's where your recipients expect to find this type of content.
#### Checklist
* [ ] Confirm whether you're actually seeing a deliverability issue (spam complaints, low open rates across the board) or only a category tab placement.
* [ ] Check that your content matches its stated purpose (promotional content stays marketing).
* [ ] Review your reputation and authentication metrics separately before drawing conclusions.
{% hint style="info" %}
**Read more**
* [Understanding and Monitoring the Spam Complaints Rate](https://doc.batch.com/guides-and-best-practices/email-deliverability/reputation-and-performance-monitoring/understanding-and-monitoring-the-spam-complaints-rate)
* [Legal Requirements & Batch Email Senders Guidelines](https://doc.batch.com/guides-and-best-practices/email-deliverability/legal-requirements-and-batch-email-senders-guidelines)
{% endhint %}
---
# 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://doc.batch.com/guides-and-best-practices/email-deliverability/reputation-and-performance-monitoring/inbox-placement/category-tabs-gmail-apple-mail-outlook...-vs.-the-spam-folder-two-different-things.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.
