Ctrlk
Netmera Docs
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Personalized mobile push

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.

Quick workflow

1

1) Prepare the user data

Make sure the profile attributes you want to use already exist in Netmera.

2

2) Insert attributes in Step 2: What

Use the {@attribute} format, or select an attribute and click Add.

3

3) Choose the fallback behavior

Decide what should happen when a user does not have that attribute.

4

4) Preview before sending

Check the final wording so the message still reads naturally after substitution.

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.

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:

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!

Keep the message readable even after substitution. Short, natural text performs better than heavily templated copy.

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}.

Preview

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.

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.

The same fallback logic applies to personalized title, message, and subtext.

Example patterns

  • Title: {@name}, you left something behind

  • Message: The items in your cart are still available.

  • Subtext: Complete your order today

  • Title: {@loyaltyTier} reward unlocked

  • Message: Hi {@name}, your new member benefit is ready.

  • Subtext: Check your rewards now

  • Title: Your offer is ready

  • Message: Use code {@couponcode} before it expires.

  • Subtext: Limited-time benefit

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.

Use personalization to make the message clearer, not just more dynamic.

Related pages

PreviousGo
NextPush A/B testing

Last updated

Was this helpful?