Basic Settings

App Info

Go to [App Settings] - [App Info] page, you can view detailed application information such as the application package name and AppKey.

• The application package name and AppKey can be used for SDK integration, and the AppKey and Master Secret can be used for API calls.
• Click "Edit" to change the application name or delete the application, click "Show" to view the Master Secret.
• Click "Reset" to regenerate the Master Secret. After resetting, you need to change the authentication parameters of the Rest API in time. Otherwise, the call will fail. Please use the "Reset" function with caution.

Integration Settings

Enter Website Domain

Web push only supports HTTPS protocol. Do not enter any address other than the homepage. Bulk addition is supported, with a maximum of 100 domains.

Advanced Push Settings

1. Notification Click Behavior Control: Improve user experience by ensuring users get appropriate actions when clicking a notification, minimizing disruption.

• Navigate to a new tab: Clicking the notification will always open the content in a new tab.
• Focus on an existing tab: If a matching tab is already open, it will switch to that tab without refreshing. Otherwise, a new tab will open.
• Note: Notifications in Safari will always open in a new tab, regardless of the configured strategy.

2. Custom Service Workers: Enhance the stability of website notifications, avoiding subscriber loss or display issues caused by misconfiguration.

⚠️ Warning: It is recommended not to change this setting after the website goes live to avoid subscriber loss and notification display issues. By default, the Service Worker should be stored in the root directory of your site. Unless necessary, we strongly advise keeping the default configuration.

3. Safari Push Certificate Support: Provide flexibility for developers targeting users on Safari 15 or earlier versions, with shared certificates available to simplify the process.

• This certificate is only required if you plan to send notifications to users on Safari 15 or earlier versions. If you don't upload your own certificate, a shared certificate will be provided by default.

Notification Authorization Configuration

Users need to grant permission for web notifications before notifications can be displayed. Currently, we support three methods: direct request, guided request, and custom. When requesting web push permissions, if the user denies authorization, another request cannot be initiated. We strongly recommend using the "guided request" soft prompt to explain the value of notifications to users before requesting web push permissions!

EngageLab provides a "Guided Prompt Configuration" that is displayed before the native authorization prompt and guides users to select the types of messages they are interested in. This prompt does not replace the native prompt or subscribe users to web push notifications. It is beneficial because it increases the likelihood of users staying subscribed to your messages and is highly recommended by browsers. The authorization prompt serves three purposes:

• Introduce the value of subscribing to push notifications to users.
• Prevent users from being blocked from subscribing.
• Trigger the native prompt when the user indicates willingness to allow notifications.

Guided Prompt Configuration

Go to [WebPush] -> [Basic Settings] -> [Notification Authorization Configuration], and select the guided request configuration method. The parameter configuration is explained as follows:

Multi-language Text Support

Supports adding text in multiple languages: We will automatically detect the end user's browser language. If no other language is set, content will be sent to all target users in the [default] language setting.

Authorization Pop-up Display Interval Logic

After the user closes the soft prompt pop-up for the first time without completing the subscription, the system will display the pop-up again after the initial interval (default 3 days). If the user still does not complete the subscription when the pop-up is shown again, it will continue to display based on the subsequent interval setting (default 7 days) until the user status changes to subscribed.

• Initial Interval Pop-up: Default is 3 days; can be set between 0-7 days.
• Subsequent Interval Pop-up: Default is 7 days; can be set between 0-15 days.

Category Prompts

By automatically tagging users who choose to subscribe to push notifications, you can segment and personalize messages according to their interests. This means you can customize push messages based on user interests and preferences, enhancing user engagement and satisfaction. The tagging function helps you better understand users to send relevant content to different groups, thereby enhancing user experience and interaction.

Developers can offer each user up to 10 message categories to choose from to express interest in certain message topics.

These categories should be related to specific features, products, or topics. For example, users can choose to subscribe to newsletters, receive notifications about new sales and products, or specific topics such as breaking news, finance, politics, entertainment, etc.

• Label: The text displayed for the category in the pop-up.
• Corresponding tag key: What is the tag in EngageLab?

Updating User Category Choices

After users subscribe to push notifications, developers can show the category prompts multiple times as needed, for example, by calling after initialization:

          MTpushInterface.promptPushCategories();

        

When the authorization pop-up is displayed again, and the same user updates their selected message categories (e.g., "deselect news information," "select discount information"), the system will unbind the user's tag corresponding to news information and bind the tag corresponding to discount information.

• Update Explanation: If you choose to show category prompts again after users subscribe to push notifications, an update explanation will be displayed instead of an operational message. This allows you to notify users that they can update their categories.

Directly Apply

Direct application means directly calling the browser's informed authorization interface. If the user agrees, the notification will be displayed. If the user refuses to authorize, it will no longer be able to do so.

• Delay * seconds: It means that after the visitor opens your website, the subscription request will be displayed according to the delay time you configured.
  • For example, if 0 is configured, it means display subscription request immediately; If it is configured to be 5, it means the subscription will be delayed for 5 seconds.
• visits: Indicates that you can require users to subscribe the web push notifications when repeatedly visiting your website.
  • For example, if the configuration is 1, it means the subscription request will be displayed for the first visit; If it is configured to be 3, it means the subscription request will be displayed for the third visit.

Custom

If you select the custom mode, you need to customize the page pop-up style on your Web site, and tell the system that it belongs to your custom style by the following methods: