This section of the tool allows you to create a custom-made push notification.
Create Push Notification
- Original: The original push notification refers to the first push notification variant you create.
- Title: The title refers to the name or the heading of the push notification. This appear as Header message within the push notification.
- Message: This is the body of the push notification.
- CTA: Link/button that would be CTA.
- a. Deep-Link: Deep-links are used to divert users to a specific screen within mobile app. User lands on the screen after clicking on a CTA link. You can choose to send custom key value pair along with CTA.
- External URL: External URL refers to any weblink where user will land upon clicking on CTA.
- Custom key-Value: The custom key-value is a context passed to a CTA. Mostly, the Custom key-value is static. However, this value becomes more powerful when it is made dynamic.
- Option for expandable notification: The WebEngage tool gives its users an option to expand a push notification to occupy the whole screen. When this happens, the extra part of the screen can either be occupied by an image, message or another CTA such as social share links.
- A/B Campaign percentage: Also referred to as Split testing, A/B campaign is a way of knowing which of the two campaigns is more effective.
- Variant A: The Variant A is a version of the original push message in which a few parameters have been changed.
Target your users
- WHO – Target segment for sending the push notification campaign
- WHEN – Time of scheduling the push notification campaign
- OneTime – If you are looking to send a one time push campaign
- ASAP – Send the campaign immediately
- Later – Send the campaign at a pre-determined date and time. The time zone is selected based on the publisher’s/admin’s time zone.
- Triggers – If you are looking to send a recurring push campaign on the basis of event state change at user/system level.
Push Notification list
- ID: ID refers to the unique identifier for each push notification campaign within an account. These are also termed as experiment Ids.
- Name:This refers to the name given to a push notification campaign. This can be any generic name that the marketer chooses. This is NOT the ‘Push notification title’ that user views on receiving the campaign.
- Schedule: Shows the state of the campaign such as Draft, Sending, Completed and Failed.
- Sending: Sending refers to the process of sending push notifications to a chosen user. Sending consists of 4 stages: process started (process has begun but not yet delivered), completed ( sending process has successfully ended and has been delivered from server end), failed (shows that the push notification could not be delivered) and in-queue (these include the push notifications that are to be sent but for which the date and time has not been set).
- Views: The ‘Views’ tab gives the number on how many users have successfully received the push notification. This number appears on the system tray.
- Interacted: The interacted tab gives the number of users who clicked on the push notification and viewed it.
- CTR: CTR, also referred to as, Click Through Rate is the ratio of users who clicked on a push notification to the number of total users who actually viewed it. The CTR is an important element that allows push campaign creators to gauge the success as well as the effectiveness of their campaign.
- Full Page Modal: The full page modal allows you to accompany the image on your notification with Title in text format. There is also space for a call-to-action button. Title can be personalized using tags. A/B split testing is allowed on all in-app notifications.
Body of ‘Full Page Modal’ template includes an image with resolution and size limits.
CTA button can be customized for link to have either deep link or web URL.
- Page Blocker: The page blocker modal contains only images. However, the text can still be embed into the image. This modal also has a call-to-action button.
- Classic Modal: The classic modal does not include any image. It only has text and call-to-action buttons. In fact, this template has three call-to-action buttons, which is the maximum number of buttons the webengage tool allows in its templates.
- Header: In the header template, the push notification appears at the top the mobile screen. There can of course be no images in this case.
- Footer: In the footer template, the push notification appears at the bottom end of the phone screen.