# Personalized Mobile Push

{% columns %}
{% column width="58.333333333333336%" %}
Personalized mobile push lets you tailor the **title**, **message**, and **subtext** with user-specific data.

Use it when the push should feel relevant to the recipient, such as:

* greeting the user by name,
* reminding them about a saved item or abandoned cart,
* or inserting loyalty, promotion, or profile-based values.
  {% endcolumn %}

{% column width="41.666666666666664%" %}

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FH29iT0ADXx01SxFICldv%2Fimage.png?alt=media&#x26;token=6150b0a5-8702-472d-b89a-39331df9c8a3" alt="" width="331"><figcaption></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

### Quick workflow

{% stepper %}
{% step %}

#### 1) Prepare the user data

Make sure the profile attributes you want to use already exist in Netmera.
{% endstep %}

{% step %}

#### 2) Insert attributes in Step 2: What

Use the `{@attribute}` format, or select an attribute and click **Add**.
{% endstep %}

{% step %}

#### 3) Choose the fallback behavior

Decide what should happen when a user does not have that attribute.
{% endstep %}

{% step %}

#### 4) Preview before sending

Check the final wording so the message still reads naturally after substitution.
{% endstep %}
{% endstepper %}

### Before you start

Before you personalize a push, make sure the required user data already exists in Netmera.

Typical attributes include:

* `name`
* `surname`
* `age`
* `loyaltyTier`
* `favoriteCategory`

You can also insert promotion values when your campaign depends on a promotion assignment.

{% hint style="warning" %}

#### Personalization needs data first

If an attribute is missing for a user, the personalized text cannot be resolved for that user.

Set up the data first in:

* [Profile Attributes](https://user.netmera.com/netmera-user-guide/customer-data/profile-attributes)
* [Coupon Code Lists](https://user.netmera.com/netmera-user-guide/panel-settings/netmera-panel-settings/coupon-code-lists) — if you want to include promotion or coupon-related values
  {% endhint %}

### How personalization works

In **Step 2: What**, you can insert profile attributes directly into supported fields.

Use the `{@attribute}` format, or select an attribute from the dropdown and click **Add**.

Example:

* **Default message:** `Happy birthday!`
* **Personalized message:** `Happy {@age}th birthday, {@name}!`
* **Rendered result:** `Happy 26th birthday, Simon!`

{% hint style="info" %}
Keep the message readable even after substitution. Short, natural text performs better than heavily templated copy.
{% endhint %}

### Where you can personalize

You can personalize three common fields in mobile push:

* **Title** — best for the main hook
* **Message** — best for context and details
* **Subtext** — best for a short secondary value

### Personalized title

Use a personalized title when the first line needs stronger relevance.

Common use cases:

* `{@name}, your order is ready`
* `Hey {@name}, your offer expires today`
* `{@loyaltyTier} member reward unlocked`

This is useful for improving open rates when the user’s identity or status adds immediate context.

### Personalized message

Use **Personalized Message** for the main body of the push.

This is the best place to add dynamic details such as:

* product names,
* profile values,
* coupon or loyalty information,
* or next-step reminders.

Example:

* `Hi {@name}, the items in your cart are still waiting.`
* `Your coupon code is {@couponcode}.`

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2Fa08EV9REVOV9XuDHOiES%2FScreenshot%202024-02-13%20at%2016.01.50.png?alt=media&#x26;token=995d10fe-8b63-4a70-b6ef-daed2c15ba71" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2F3SnHqiep8eSasiYPhkTF%2FScreenshot%202024-02-13%20at%2016.10.34.png?alt=media&#x26;token=03515f26-23c7-4ea5-a05b-d6c79920ac56" alt="" width="375"><figcaption><p>Preview</p></figcaption></figure>

### Personalized Subtext

Use **Personalized Subtext** for short secondary context.

Good examples:

* `Tier: {@loyaltyTier}`
* `Nearest store: {@nearestStore}`
* `Code: {@couponcode}`

Subtext should stay compact. Use it to support the title and message, not repeat them.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FXETJKVyLhpbqngb2KJIf%2FScreenshot%202024-02-13%20at%2016.09.15.png?alt=media&#x26;token=17f8d037-92e0-415e-832a-bfa61e4cc4bc" alt=""><figcaption></figcaption></figure>

### If data is missing

When a selected attribute is null or missing, Netmera gives you two options:

* **Do not send message** — users with missing data do not receive that push.
* **Send notification message** — users with missing data receive the default **Notification Message** instead.

Use **Do not send message** when accuracy matters most.

Use **Send notification message** when reach matters most.

{% hint style="info" %}
The same fallback logic applies to personalized title, message, and subtext.
{% endhint %}

### Example patterns

{% tabs %}
{% tab title="E-commerce" %}

* **Title:** `{@name}, you left something behind`
* **Message:** `The items in your cart are still available.`
* **Subtext:** `Complete your order today`
  {% endtab %}

{% tab title="Loyalty" %}

* **Title:** `{@loyaltyTier} reward unlocked`
* **Message:** `Hi {@name}, your new member benefit is ready.`
* **Subtext:** `Check your rewards now`
  {% endtab %}

{% tab title="Coupon" %}

* **Title:** `Your offer is ready`
* **Message:** `Use code {@couponcode} before it expires.`
* **Subtext:** `Limited-time benefit`
  {% endtab %}
  {% endtabs %}

### Best practices

* Personalize only when the attribute is reliable.
* Keep fallback copy ready for missing data.
* Use one or two dynamic fields per push.
* Test the final output before launch.

{% hint style="success" %}
Use personalization to make the message clearer, not just more dynamic.
{% endhint %}

### Related pages

* [Notification Content: What](https://user.netmera.com/netmera-user-guide/omnichannel-engagement/mobile-push/create-mobile-push/what)
* [Audience: Who](https://user.netmera.com/netmera-user-guide/omnichannel-engagement/mobile-push/create-mobile-push/who)
* [Campaign Schedule: When](https://user.netmera.com/netmera-user-guide/omnichannel-engagement/mobile-push/create-mobile-push/when)
* [Push A/B Testing](https://user.netmera.com/netmera-user-guide/omnichannel-engagement/mobile-push/push-a-b-testing)