MoEngage Docs

Configuring Opt-In Type

Opt-In refers to the way the push permission is asked from the users on your webpage. MoEngage provides 3 push opt-in mechanisms which can be configured here under Notification Opt-in Configuration:

  • 1-Click Opt-In
  • Two Step Opt-In
  • Self Handled Opt-in

1-Click Opt-In (HTTPS sites only)

The SDK directly triggers the browser to show the push notification permission request.

Chrome v62 Update

Following Chrome v62 update, 1-Click Opt-In will no longer be supported for HTTP websites. We recommend you switch to Two Step Opt-In approach for the best experience.

Two Step Opt-In

Users are shown a HTML "soft-ask" which gauges user preference and proceeds to show the main browser permission upon allowed.

Self Handled Opt-in

An Advanced setting where you can selectively show the Browser Opt-in on specific pages or after certain actions. You have to call our function Moengage.call_web_push() from your script to show the Push permission. Click here for more details about self-handled opt-ins

<head>
<script type="text/javascript">
  ...
  // Moengage Initialization script here
  // Docs: https://docs.moengage.com/docs/web-sdk-integration
  ...

  // call to show the Chrome's push notification opt-in box.
  Moengage.call_web_push();
</script>
</head>

Push Opt-in Re-appear Time

In case the users close the opt-in or banner/nudge, you can configure the time after which to show the opt-in again to the user. This is referred as Opt-in re-appear time as shown in the snapshot below.

Configuring Opt-In Type


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.