=== PushEngage Browser Push Notifications Plugin=== Contributors: prakrishna2004, itsmeravitejak Tags: push notifications, web notifications, chrome notifications, notifications, browser notifications, HTTPS support, chrome push notifications, push notifications, website push notifications Requires at least: 4.1.5 Tested up to: 4.7 Stable tag: 1.3.2 License: GPLv2 License URI: http://www.gnu.org/licenses/gpl-2.0.html PushEngage is a plugin to enable Browser Push Notifications for Desktop and Mobile users on Chrome, and Firefox. You can implement in 10 mins. == Description == PushEngage allows websites to send web push notifications to their site visitors and engage with them. Current version of plugin supports Chrome and Firefox notifications. Our Highlights of Chrome Notification offering 1. Engage With Users 2. Segmentation 3. HTTPS Support 4. Schedule Notifications == Installation == 1. Upload PushEngage plugin folder into the "/wp-content/plugins/" directory. 2. Install the plugin through the "Plugins" menu in WordPress. 3. Activate the plugin through the "Plugins" menu in WordPress. 4. HTTPS / SSL users should follw below instructions to install PushEngage Notifications Plug-in. i) HTTPS users should download installation files from their Dashboard under Settings -> Installation Settings. ii) Download the Package file containing manifest.json and service-worker.js iii) Place the manifest.json and service-worker.js file in root folder i.e. at https://www.example.com/manifest.json == Frequently Asked Questions == 1. How can I look into the product features and dashboard that you have? Please register with a new account here and you will receive an email with login to your dashboard. 2. Can PushEngage be implemented on http websites? Yes, PushEngage can be implemented on a HTTP website, and that is one of the advantage of using our product, that you don’t need to have a HTTPS version of your website. We will implement this using our Https certificate and the domain your push will be hosted will be https://yourdomain.pushengage.com 3. Can PushEngage be implemented on https websites, with a url structure https://push.mydomain.com ? Yes, we can implement if you have your own Https domain and want to have your notifications come from your domain name. 4. After I have 2500 subscribers in my free account, what will happen to my account? Once you reach a subscriber number of 2500, you will need to upgrade to paid plan to keep sending notifications. 5. How do I get access to my subscribers for Notifications, as I may need them if I want to migrate to a different software provider? In order for us to provide you your subscriber ID’s that have subscribed to your notifications, we would need that you provide us the GCM (Google Cloud Messaging) API Key for Chrome, and Certificate Details for Safari at the time of installation. Without this information it is not possible for us to provide you the subscriber ID’s. Also, note to export your subscriber ID’s you need to be subscribed to our paid plans. If you want to know how to register for a GCM Key, please refer to documentation here . 6. I have a large list of email subscribers for my site. Is there a way to tie this list to the subscribers through Push Notification on the website. The Chrome PushManager only gives us an opaque end-point for each of the subscriber i.e. a key like “APA91bHPffi8zclbIBDcToXN_LEpT6iA87pgR”. We do not have the ability to directly map this to a email of an user. However, if have the ability to determine the email or any other of your internal mapping of the user at the time of subscription, we provide you the ability to store that information along with the key. 7. If I have more questions who should I ask? Please send us your query through Contact Us page, or email to us at care@pushengage.com == Screenshots == 1. Dashboard page you can see notifications and subscribers information. 2. Send a new notification 3. List of sent notifications 4. Create a new segment 5. General settings for notifications 6. Subscription dailogbox settings 7. GCM Settings 8. Welcome notification settings == Changelog == = 1.0 = * Initial release. = 1.1 = * Fixed some minor issues = 1.2 = * Fixes for CSS issue, Major revamp to all dashboards = 1.2.1 = * Fixed CSS issue. Incorporated advanced options for new notification section(Segments, Scheduled, User Interarction and Expiry) = 1.2.2 = * Resolved HTTPS issue and fixed minor issues. = 1.2.3 = * Fixed notification issue in New Post section. = 1.2.4 = * Fixed notification issue while saving the post as draft. = 1.2.5 = * HTTPS installation issues fixed. = 1.2.6 = * Updated dashboard page user interface. = 1.2.7 = * Fixed issue in save draft checkbox display issue. = 1.2.8 = * Fixed display send notification checkbox issue in scheduled notification section. = 1.2.9 = * Updated require interaction functionality while creating notification. = 1.3.0 = * Require interaction of a notification option is now available in general settings. = 1.3.1 = * Fixed issue while posting printing an array. = 1.3.2 = * Support for wordpress version 4.7 == Upgrade Notice == = 1.3.1 = * Fixed issue while posting printing an array. = 1.3.2 = * Support for wordpress version 4.7 = 1.3.0 = * Require interaction of a notification option is now available in general settings. = 1.2.9 = * Updated require interaction functionality while creating notification. = 1.2.8 = * Fixed display send notification checkbox issue in scheduled notification section. = 1.2.7 = * Fixed issue in save draft checkbox display issue. = 1.2.6 = * Updated dashboard page user interface. = 1.2.5 = * HTTPS installation issues fixed. = 1.2.4 = Fixed notification issue while saving the post as draft. = 1.2.3 = Fixed notification issue in New Post section. = 1.2.2 = Resolved HTTPS issue and fixed minor issues. = 1.2.1 = Fixed CSS issue. Incorporated advanced options for new notification section(Segments, Scheduled, User Interarction and Expiry) = 1.2 = This version upgrades the dashboard with several new features. Also, fixed a CSS Bug. Recommend to upgrade immediately. = 1.1 = This version fixes some minor issues in plugin. Upgrade immediately. = 1.0 = This version fixes a security related bug. Upgrade immediately.