> For the complete documentation index, see [llms.txt](https://kasplo.gitbook.io/kasplo-doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kasplo.gitbook.io/kasplo-doc/product-docs/welcome-to-the-support-documentation/personalization-in-kasplo.md).

# Personalization in Kasplo

### Overview

Kasplo allows you to personalize your email campaigns using . These  dynamically replace placeholders with recipient-specific information, helping create a more personalized experience for every subscriber.

The **Merge Tags** option is available in both:

* **HTML Editor** (via the Personalization icon)
* **Drag & Drop Editor** (under **Merge Tags**)

<figure><img src="/files/nbJQoaBvgRnxuek5nB2x" alt=""><figcaption></figcaption></figure>

***

### Default Personalization Syntax

When you insert a personalization tag, Kasplo generates the following syntax by default:

```
{{first_name|default:'there'}}
```

<figure><img src="/files/xuO1AKxTmsSuypqg0lsR" alt=""><figcaption></figcaption></figure>

#### How it works

* **first\_name** – Fetches the recipient's `first_name` value from the contact list.
* **default:'there'** – Displays **"there"** if the `first_name` field is empty or unavailable.

For example:

| Contact First Name    | Output |
| --------------------- | ------ |
| John                  | John   |
| Sarah                 | Sarah  |
| Empty / Not Available | there  |

***

### Removing the Default Value

If you do not want a fallback value, simply leave the default value empty.

Example:

```
{{first_name|default:''}}
```

This ensures that if the recipient's first name is unavailable, nothing is displayed instead of a default word.

***

### Where Personalization Can Be Used

Merge Tags can be used in the following locations:

* Subject Line
* Preview Text
* Email Body
* Buttons
* Headers
* Footers
* Anywhere within the email template where text is supported

***

### Custom Fields

Kasplo also supports personalization using **Custom Fields**.

**Important:**

* If a custom field already contains a default value configured during its creation, **that default value takes precedence**.
* If no default value exists for the custom field, Kasplo will use the default value specified within the merge tag.

<figure><img src="/files/2d12deVXxFucQFqQfaOV" alt=""><figcaption></figcaption></figure>

#### Example

Merge Tag:

```
{{customer_city|default:'your city'}}
```

Scenario 1:

* Custom field default = **Bengaluru**
* Contact value is empty

**Output:** Bengaluru

Scenario 2:

* No custom field default configured
* Contact value is empty

**Output:** your city

Scenario 3:

* Contact value = Mumbai

**Output:** Mumbai

***

### Best Practices

* Always use fallback values for important personalization fields to avoid blank text in emails.
* Keep fallback values natural (for example, "there", "friend", or "Customer").
* Test personalization using sample contacts before sending campaigns.
* Verify that contact data is correctly uploaded and mapped to avoid missing values.

{% hint style="info" icon="paper-plane" %}
If any support is needed, contact: [HelpDesk | Kasplo](mailto:helpdesk@kasplo.com)
{% endhint %}