Personalized Web Push

Personalized web push lets you tailor the title, message, and subtext with user-specific data.

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

• greeting the user by name,

• reminding them about an offer, cart, or deadline,

• 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 web push, make sure the required user data already exists in Netmera.

Typical attributes include:

• name

• surname

• age

• goal

• loyaltyTier

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

• Coupon Code Lists — if you want to include promotion or coupon-related values

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.

Examples:

• Wishing you a sweet {@age}th birthday, {@name}!

• Hey {@name}, your {@goal} reminder is ready.

• Your coupon code is {@couponcode}.

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

Where you can personalize

You can personalize three common fields in web push:

• Title — best for the first hook

• Message — best for the main context

• Subtext — best for short secondary detail

Personalized title

Use a personalized title when the first line should feel immediately relevant.

Common use cases:

• {@name}, your order is ready

• Hey {@name}, your offer expires today

• {@loyaltyTier} member reward unlocked

This is useful when identity, status, or urgency adds clear context.

Personalized message

Use Personalized Message for the main body of the notification.

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

• product names,

• profile values,

• coupon or loyalty details,

• or next-step reminders.

Example:

• Default message: Happy birthday!

• Personalized message: Wishing you a sweet {@age}th birthday, {@name}!

• Rendered result: Wishing you a sweet 26th birthday, Simon!

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 web push.

• Send default notification message — users with missing data receive the default Notification Message instead.

Use Do not send message when accuracy matters most.

Use Send default notification message when reach matters most.

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

Example patterns

E-commerce

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

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

• Subtext: Complete your order today

Loyalty

Coupon

Best practices

• Personalize only when the attribute is reliable.

• Keep fallback copy ready for missing data.

• Use one or two dynamic fields per notification.

• Test the final output before launch.

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