> For the complete documentation index, see [llms.txt](https://help.sdocs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sdocs.com/sdocs/template-architecture/inserting-merge-fields/additional-resources/special-salesforce-mailing-address-fields.md).

# Mailing Address Fields

## Salesforce mailing address fields

Salesforce “address” fields are **compound fields**. They bundle multiple values into one field.

### Use case

You need to show a customer’s mailing address in a template or document.

Examples:

* Emails (transactional and marketing)
* PDFs / generated letters
* Portals and customer-facing UIs

### Problem

Compound address fields (for example, `MailingAddress`, `BillingAddress`, `ShippingAddress`) are convenient to store, but they’re often **hard to format**.

* You can’t reliably control line breaks and punctuation.
* Styling can be inconsistent across channels.
* Parsing the combined value back into parts is fragile.

Salesforce details: <https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/compound\\_fields\\_address.htm>

### Solution

Use the **individual address components** in your template and format them yourself.

Typical components:

* Street
* City
* State/Province
* Postal Code
* Country

In Salesforce objects, these usually appear as field pairs like:

* `MailingStreet`, `MailingCity`, `MailingState`, `MailingPostalCode`, `MailingCountry`

Format and place these fields in the order your audience expects. This gives you consistent rendering and full control over layout.


---

# 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.sdocs.com/sdocs/template-architecture/inserting-merge-fields/additional-resources/special-salesforce-mailing-address-fields.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.
