Define Notification Content: What
Last updated
Was this helpful?
Last updated
Was this helpful?
The What step is where you define the content of your push notification. In this step, you will configure the core components of your message—such as the title, body, visuals, and personalization settings—that will appear on users’ devices.
a. Small Icon
24×24 – 96×96, white PNG with transparent background.
b. Title
Max 50 characters.
c. Body (Notification Message)
Max 150 characters.
d. Image
1440×720 (2:1 ratio), PNG/JPG/GIF (not animated).
e. App Name
Shown as notification source. Cannot be customized.
f. Time Stamp
Shows when the message was received.
g. Thumbnail (Icon)
192×192+, PNG/JPG/GIF (not animated).
h. Action Buttons
Title of your notification
Necessary in all notification types
Your message to be delivered in your notification
Necessary in all notification types
Images that appear inside of your notification
Necessary if any media notification is chosen
Optional
Optional
Your personalized title aiming your user information
Optional
Additional text to be shown next to your application name
Optional
Personalized attribute using the {@} format
Optional
Optional
Images that appear next to text messages that can't be expanded
Optional
Notifications will be delivered via vibration if you switch on
Optional
Optional
Send message to all targeted users’ inbox regardless they are opt-in or not
Optional
Your message will not be shown as notification. Use only for inbox.
Optional
Optional
Message logs won’t be directed to application backend
Optional
Actions can be taken when the user clicks the notification
Optional
Optional
Conversion event can be determined according to your aim
Optional
Purpose: Organize your campaigns based on their function or content.
Use the Category field to classify your campaign under a label such as:
Promotions
Announcements
Account Alerts
Transactional Messages
Categorizing helps with future campaign filtering, reporting, and analytics.
Purpose: Communicates the primary message to users.
This is the main text content of your push notification. Keep it:
Informative
Concise
Action-oriented
You may use text and emojis for added emphasis and visual appeal.
Example: “Your payment was successful 🎉” or “🚨 Suspicious login detected. Tap to secure your account.”
Purpose: Increases engagement by tailoring content using user profile data.
Example:
Default: “Happy birthday!”
Personalized: “Wishing you a sweet {@age}th birthday, {@name}!” → Displays as: “Wishing you a sweet 26th birthday, Simon!”
Use cases include:
Greeting users by name
Recommending products based on past behavior
Sending localized or weather-based messages
Tip: Ensure your app transmits the necessary profile data to Netmera beforehand.
Purpose: Grabs attention and provides immediate context.
Create a compelling notification title that encourages the user to engage. You can use emojis and concise text to improve visibility.
If user profile data is available, personalize the title for stronger impact.
Example: “Hey {@name}, your exclusive offer is here!” → Becomes: “Hey Emily, your exclusive offer is here!”
Personalized titles can:
Increase open rates
Strengthen user-brand connection
Improve retention metrics
Purpose: Adds secondary context, shown next to your app’s name.
Subtext supports personalization and often appears in the notification header on supported devices. It can include:
Additional details
A brief summary
A call to action
Example: “Limited-time offer · Ends tonight!”
You can use the same {@} format or dropdown menu to insert dynamic user data into the subtext.
Example: “Your challenge score: {@score}” → “Your challenge score: 850”
Purpose: Displays a custom app logo or image beside the notification (platform-specific).
Requires SDK integration.
If not configured, the default icon from your app settings will be used.
Refer to:
Purpose: Displays a thumbnail image alongside the notification text.
Can be uploaded or referenced via direct URL.
Offers a static, non-expandable visual.
Ideal for logos, product previews, or branded content.
Purpose: Embeds rich media (images or videos) in the notification.
Media is shown more prominently than thumbnails.
Enhances visual appeal and message clarity.
Example Use Case: Include a product image in a push notification announcing a new collection.
Upload from your computer or insert a URL. Ensure the media is optimized for fast loading.
Adds a vibration alert when the notification is received.
Enhances visibility for users in noisy or muted environments.
Can be enabled or disabled per campaign.
Use this feature for:
Important announcements
Time-sensitive content
Summarized communications
Enables message delivery even to users who have opted out of push notifications. The message is silently delivered to the inbox without triggering a notification.
Useful for:
Critical updates
Transactional information
If selected, the message will only appear in the push inbox and will not trigger an actual notification on the device.
Use this to:
Avoid disturbing the user
Provide contextual messages inside the app
Use distinct sounds for priority messages
Ensure sound files meet platform requirements
When this option is enabled, any webhooks connected to the campaign are deactivated for this notification.
This is useful when:
Testing a message
Sending isolated notifications that should not trigger backend workflows
The Click Action defines what happens when a user taps the notification. Each action allows you to create specific user journeys based on your campaign goals.
Open App
Opens the app's main screen. Suitable for general awareness messages.
Show Web Page
Opens a specific URL in the device's browser. Useful for external content or promotions.
Go to Deeplink
Navigates to a specific screen in the app using a deeplink URL. Ideal for contextual or personalized experiences.
Show Custom Page
Displays an in-app landing page or message. Great for promos or targeted in-app content.
Open Widget
Opens a widget already defined in your app. Widgets must be created in advance.
Nothing
No action is taken. The notification is dismissed. Used for informational alerts.
Opens the main screen or homepage of your app. Ideal for general engagement campaigns where no specific destination is required.
Opens a web page in the device’s browser. A valid URL must be entered. Useful for:
Redirecting users to campaign-specific landing pages.
Linking to help center articles.
Promoting time-sensitive offers.
Navigates users to a specific page or section within your app using a deeplink. This is recommended for personalized or feature-specific campaigns.
You can choose from a list of predefined deeplinks or input a custom one.
Deeplinks must be registered in your app’s routing system.
Displays a custom in-app page. Often used for:
In-app promotional screens.
Full-screen messages.
Targeted announcements without navigating away from the app.
Triggers an in-app widget. Widgets must be created in advance and can be used to:
Collect feedback.
Display dynamic offers.
Show embedded content directly.
No action is triggered; the notification is dismissed. This is suitable for passive updates such as:
Informational alerts.
Background data sync confirmations.
Enhance push behavior with additional key-value data passed alongside the notification. These parameters can be read and interpreted by the app upon user click.
Key
Parameter name (e.g., campaignId, source).
Value
Corresponding value (e.g., spring2025, web).
Action
Click “Add” to include the parameter.
Example Use Cases:
Open App → add type: promotion, id: 12345
Show Web Page → add url: https://example.com/special
When enabled, the WebhookClick event is triggered upon notification interaction. This allows your backend systems to log or respond to click events in real time.
Web Hook
Select a webhook endpoint from your system.
pushParameter
Pass additional data (e.g., campaign type, user ID, offer ID).
Example Use Case: Click triggers a webhook that logs the event and updates CRM with user behavior context.
Updates user profile data upon click. This is useful for segmentation and campaign personalization.
Attribute
Name of the attribute (e.g., Status)
Value
New value to be assigned (e.g., Active)
Example Use Case:
Clicking a loyalty campaign updates LoyaltyStatus to Gold.
Suppose you want to update a user's credit limit when they click on a push notification:
Enter "CreditLimit" as the attribute name.
Input the desired credit limit value in the text box.
This configuration ensures that when the notification is clicked, the user's profile is updated with the new credit limit. It's like filling out a form to set someone's credit limit. When they press the button (click the notification), the limit gets updated automatically.
This option allows you to assign a tag to the user. Tags are used to group users based on specific characteristics or behaviors. For instance, you might use tags like "VIP", "Newsletter Subscriber", or "Frequent Buyer".
Fallback scenarios can be thought of as a backup plan in case your push notification fails to reach its intended audience. By creating a fallback scenario, you can ensure that users who do not receive your push notification can still receive the message through an alternative channel, such as SMS.
Example Use Case: If the push is undelivered within X minutes, an SMS is sent with similar content.
Campaign labels allow internal users to organize and filter campaigns more effectively. Unlike tags or attributes, labels are for internal tracking and do not affect segmentation or targeting.
Example Labels:
New Users
Promo_May2025
Onboarding_Step1
Use labels to streamline campaign reporting and searchability, especially for teams managing high campaign volumes.
Measure post-click behavior by setting conversion events. Helps quantify the impact of your notification campaign.
Purchase Event
Track how many users bought after clicking.
Registration Event
Measure new signups triggered by the notification.
View Content
See if users viewed a specific screen or item.
Multiple events can be tracked per campaign.
Data is available in real-time on the Netmera Dashboard.
The Control Group option enables data-backed performance evaluation. A selected percentage of your audience is excluded from the push to compare outcomes.
Example: Out of 100,000 users, setting a 1% control group sends the push to 99,000. The behavior of the 1,000 unnotified users is compared against the recipients.
Use control groups to attribute campaign impact with higher confidence.
Configurable in Settings > (up to 3).
Category of your messages based on your own predefined criteria or use case
Your personalized message aiming your user information
Send message with custom icons (needs integration, please refer to or )
Send message to application inbox (needs integration, please refer to )
Notification are delivered with sound (needs integration, please refer to )
Scenarios can be created for the users that did not receive your notification (needs integration, please refer to )
You can personalize messages using attributes such as name, age, or preferences stored in Netmera. Use {@attribute} syntax or the dropdown selector to insert available attributes. You must create before using them in your notifications.
This option needs integration, please refer to . After you have integrated this option with your developers, you may choose this option on this step. Once integrated, selecting this option allows the message to be stored in your app’s internal Push Inbox, enabling users to revisit it later.
This option needs integration, please refer to . After you have integrated this option with your developers, you may choose this option on this step. After setup, you can upload or select a custom sound to play when the notification arrives.
