LogoLogo
WebsiteBlog
  • Introduction
  • CDP Overview
  • Identity Resolution
  • CDP Guidelines for Data Sanity and Campaign Governance
  • Login and User Management
    • Login to the platform
    • Change Password / Retrieve your Account
    • Role Based Access Control
      • User Management
      • Roles
    • Single Sign-On (SSO)
  • Events
    • Events Overview
    • App Events
    • Track
    • Identify
    • Page
    • Screen
    • Event Dictionary
  • Sources
    • Sources Overview
    • Android SDK
    • iOS SDK
    • JavaScript SDK
    • React Native SDK
    • Flutter SDK
    • REST API
    • Adobe Analytics Exports
    • SFTP
    • Kafka
    • Offline File Ingestion
  • Destinations
    • Destinations Overview
    • Quora Pixel
    • Hotjar
    • Clevertap
    • Google Analytics 4 (GA4)
    • Meta Pixel
    • Meta Conversion API
    • LinkedIn Insight Tag
    • Adobe Target
    • AppsFlyer
    • AWS S3
    • Criteo
    • Kafka
  • Integrations
    • Rudderstack
    • Azure Blob
    • Adobe Launch Private Extension
    • Adobe Launch Extension
    • Salesforce CRM
    • Microsoft Dynamics 365
  • Customer One View
    • Introduction
    • Basic details, Attributes and Devices
    • Segment and Engagement
    • Activity
  • Segments
    • Getting Started
    • Create a Segment
  • Channels
    • Getting Started
    • A/B Testing
    • SMS
      • Set up an SSP
        • Netcore
        • Twilio
        • Adobe Campaign Classic
        • Gupshup
        • Unifonic
        • Infobip
        • Tubelight
      • Add an SSP
      • Create SMS campaign
      • FAQs
    • Email
      • Set up an ESP
        • SendGrid
        • SendInBlue
        • SparkPost
        • Taximail
        • Netcore
        • Adobe Campaign Classic
        • Mailchimp
        • Oracle Email Delivery
        • Infobip
        • Vision6
      • 🆕Add an ESP
      • Create Email campaign
      • Common use cases with Email Editor
      • Why Email Notification may not get delivered?
      • FAQs
    • App Push Notification
      • Create App Push Notification - Android
      • Create App Push Notification - iOS
      • Why App Push Notification may not get delivered?
      • FAQs
    • WhatsApp
      • Configure a WSP
        • Yellow Messenger
        • Infobip
        • Gupshup
        • BIK.ai
        • Vonage
        • Sinch
        • Tubelight
      • Create WhatsApp campaign
      • FAQs
    • RCS
      • Add an RCS API
      • Example: Netcore RCS API
      • Create an RCS campaign
      • FAQs
    • Web Push Notification
      • Create a Web Push Notification
      • Create a Default Web Push Notification
      • FAQs
    • On-site Notification
      • Create On-site Notifications.
      • Common use cases with On-site Notification.
      • Notification Templates
    • Banner Personalization
      • Create a Personalized Banner
      • Create a Default Banner
    • External API
      • Create Engagement
      • Test your API configuration
      • Example Use Cases of External APIs
        • Use case 1: HubSpot - Create Contacts API
        • Use case 2: Exotel's Make a call API
        • Use case 3: Mailmodo's Send Campaign Email API
    • Notification Bot
  • Ramanujan AI
    • Lead scoring
    • Channel Orchestration
    • Content Generator
      • Generate Web Push Content
  • Journey Builder
    • Overview- Journey Builder
    • View all Journeys
    • Create a Journey
    • Journey Reports
    • FAQs
  • Audience Export
    • Facebook Export Channel
    • Google Ads Export Channel
  • Analytics
    • Dashboard
      • Guiding through the Dashboard
      • Unique Profile
      • Profile and Merge Trends
      • Campaign and Revenue Dashboard
    • Campaign Summary
    • Events Occurrence
    • Event Telemetry
    • App Installs and Uninstalls
    • Funnels
    • Paths
    • Traffic Analysis
    • Cohorts
    • Data sanity between Funnels, Paths and Events
    • FAQs
  • Developer APIs
    • User Profile API
    • WhatsApp Opt-in/Opt-out API
    • Subscription Management
  • Settings
    • Product Label
    • Frequency Caps
    • Contacts
Powered by GitBook
On this page
  1. Channels
  2. Web Push Notification

Create a Web Push Notification

Steps to create a Web Push Notification for Android using Lemnisk Marketing Automation Platform.

PreviousWeb Push NotificationNextCreate a Default Web Push Notification

Last updated 25 days ago

Create a Web Push Notification Campaign

Step 1: Create a Web Push Notification Engagement

  1. Go to Campaigns > Segments

  2. Select the Segment Name

  3. Click on Web Push Notification on the left panel

  4. Click on Add Engagement

  1. Go to Campaigns > Channels

  2. Click on Web Push Notification on the left panel

  3. Click on Add Engagement

  4. Select Segment Name from the list

  5. Click on Confirm And Proceed To the Next Step

Step 2: Add General Details

  • Engagement Name (mandatory): Add a unique name to the Engagement. It must range between 6-25 characters.

  • Language (mandatory): Select a language in which you prefer to communicate.

Step 4: Add Content

  • Notification Title (mandatory): The notification title of the Engagement message. The recommended max length is 32 characters.

  • Notification Message (mandatory): Enter a brief message explaining the purpose of the Engagement. It should contain at least 6 characters. The recommended max length is 42 characters.

  • Icon (mandatory): Upload the icon to represent the logo of your website or profile that will be displayed in your web push notification. The icon image should support JPG or PNG file formats, with (192*192) pixel dimension and a maximum 1 MB size.

  • Notification Image: The image you want to upload indicates the purpose of the web push engagement. The notification image only supports JPG or PNG file formats, with an Aspect Ratio of 3:2 (recommended resolutions are 540x360, 720x480, etc).

Image Format:

In cases where the recommended size is stated, there is no length constraint for the message. However, it might get trimmed while it is delivered leading to data loss, or might not get delivered at all. Lemnisk suggests you should keep it to the recommended length.

Step 5: Buttons Icon

The icon you want to use on the button of your web push engagement. You can import using a URL or upload an image from the Lemnisk Image Media Repository. The icon image should be in JPG, PNG, or WEBP file formats, with (32*32) pixel dimension and a maximum 1 MB size.

  • Text: The text you want to mention beside the icon on the button.

  • On Click Action: The action is performed when the button is clicked.

  • Add/Remove Elements: You can add or remove buttons in the push notification to navigate customers.

Step 6: Redirect URL (mandatory)

Provide the URL to which the web push notification will get directed.

Step 7: Schedule Settings

Step 8: Save: Click "Save" to save the Engagement.

Fallback

For a detailed explanation of the steps discussed above, please refer to this video:

Once you have created an engagement, you cannot change the name of the engagement or the schedule settings.

Select Label (mandatory): Choose a product label from the list. Click to learn more about Product labels.

Step 3: Add a Goal Goal Type (mandatory): Choose a goal type from the list. To learn more about conversion goals, follow guide.

You can also generate content using Lemnisk's Ramanujan AI which supports generating content for any segment based on the previous engagement and prompts. To learn more about AI content generation for web push, Click

Fallback: You can use the fallback feature provided by Lemnisk. To learn more about Fallback, click .

Fallback: You can use the fallback feature provided by Lemnisk. To learn more about Fallback, click .

An engagement can be scheduled to be sent later or triggered immediately upon the achievement of the engagement goal. To learn more about Engagement Scheduling, click .

Fallback is a feature used in Web Push Notification engagements to communicate cases of engagement failure. A fallback message will be sent to the user who does not receive the engagement. This ensures that every segment member receives the engagement. To learn more about personalization failure, click .

here.
here
here
here
here
this
here
Demo: Creating Web Push Engagement
Demo: Add an engagement via Segment flow
Demo: Add an engagement via Engagement flow
(720*480) JPG or PNG