{"id":111460,"date":"2019-10-28T02:24:07","date_gmt":"2019-10-28T02:24:07","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/notification-button\/"},"modified":"2026-05-12T16:53:18","modified_gmt":"2026-05-12T16:53:18","slug":"notification-button","status":"publish","type":"plugin","link":"https:\/\/sah.wordpress.org\/plugins\/notification-button\/","author":17623488,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"1.0.9","stable_tag":"1.0.9","tested":"6.4.8","requires":"5.0","requires_php":"7.2","requires_plugins":null,"header_name":"iCortex\u2122 \u2013 High-Fidelity Revenue Engineering for WordPress & WooCommerce","header_author":"iCortex\u2122","header_description":"Send messages to your web visitors instantly without sending any e-mail. Notifications to desktop computers, laptops, cell phones or tablets","assets_banners_color":"","last_updated":"2026-05-12 16:53:18","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"https:\/\/icortex.ai","header_author_uri":"","rating":0,"author_block_rating":0,"active_installs":0,"downloads":1296,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"1.0.1":{"tag":"1.0.1","author":"scordeveloper","date":"2026-01-09 07:32:50"},"1.0.2":{"tag":"1.0.2","author":"scordeveloper","date":"2026-05-01 07:47:21"},"1.0.3":{"tag":"1.0.3","author":"scordeveloper","date":"2026-05-01 08:10:30"},"1.0.4":{"tag":"1.0.4","author":"scordeveloper","date":"2026-05-01 08:25:59"},"1.0.5":{"tag":"1.0.5","author":"scordeveloper","date":"2026-05-02 22:04:05"},"1.0.6":{"tag":"1.0.6","author":"scordeveloper","date":"2026-05-03 06:17:43"},"1.0.8":{"tag":"1.0.8","author":"scordeveloper","date":"2026-05-12 16:34:09"},"1.0.9":{"tag":"1.0.9","author":"scordeveloper","date":"2026-05-12 16:53:18"}},"upgrade_notice":[],"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3520171,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3520171,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.1","1.0.2","1.0.3","1.0.4","1.0.5","1.0.6","1.0.8","1.0.9"],"block_files":[],"assets_screenshots":{"screenshot-1.jpg":{"filename":"screenshot-1.jpg","revision":3520171,"resolution":"1","location":"assets","locale":"","width":1920,"height":1080},"screenshot-10.png":{"filename":"screenshot-10.png","revision":3520205,"resolution":"10","location":"assets","locale":"","width":1920,"height":1080},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3520205,"resolution":"2","location":"assets","locale":"","width":1920,"height":1080},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3520171,"resolution":"3","location":"assets","locale":"","width":1920,"height":1080},"screenshot-4.jpg":{"filename":"screenshot-4.jpg","revision":3520205,"resolution":"4","location":"assets","locale":"","width":1920,"height":1080},"screenshot-5.jpg":{"filename":"screenshot-5.jpg","revision":3520205,"resolution":"5","location":"assets","locale":"","width":1920,"height":1080},"screenshot-6.jpg":{"filename":"screenshot-6.jpg","revision":3520205,"resolution":"6","location":"assets","locale":"","width":1920,"height":1080},"screenshot-7.jpg":{"filename":"screenshot-7.jpg","revision":3520205,"resolution":"7","location":"assets","locale":"","width":1920,"height":1080},"screenshot-8.jpg":{"filename":"screenshot-8.jpg","revision":3520205,"resolution":"8","location":"assets","locale":"","width":1920,"height":1080},"screenshot-9.jpg":{"filename":"screenshot-9.jpg","revision":3520205,"resolution":"9","location":"assets","locale":"","width":1920,"height":1080}},"screenshots":{"1":"iCortex\u2122 positioning and hero overview for the E-commerce stack.","2":"Predictive Cortex\u2122 \u2013 intent intelligence and interaction signals.","3":"Campaign orchestration and node-level control in iCortex\u2122.","4":"Lifestyle Engine\u2122 \u2013 high-aesthetic visual synthesis (scene example).","5":"Lifestyle Engine\u2122 \u2013 product narrative and visual elevation (scene example).","6":"Product storytelling and Lifestyle Engine\u2122 output (footwear).","7":"Product storytelling and Lifestyle Engine\u2122 output (accessories).","8":"Brand Recall and Lifestyle Engine\u2122 strategic engagement cycle.","9":"iCortex\u2122 AI Stylizer \u2013 creative synthesis in the workflow.","10":"Predictive timing, incentives, and orchestration surfaces in iCortex\u2122."}},"plugin_section":[],"plugin_tags":[2353,888,20199,1155,3609],"plugin_category":[55],"plugin_contributors":[177867],"plugin_business_model":[],"class_list":["post-111460","plugin","type-plugin","status-publish","hentry","plugin_tags-ai","plugin_tags-e-commerce","plugin_tags-email-campaigns","plugin_tags-push-notifications","plugin_tags-revenue","plugin_category-seo-and-marketing","plugin_contributors-scordeveloper","plugin_committers-scordeveloper"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/notification-button\/assets\/icon-128x128.png?rev=3520171","icon_2x":"https:\/\/ps.w.org\/notification-button\/assets\/icon-256x256.png?rev=3520171","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/notification-button\/assets\/screenshot-1.jpg?rev=3520171","caption":"iCortex\u2122 positioning and hero overview for the E-commerce stack."},{"src":"https:\/\/ps.w.org\/notification-button\/assets\/screenshot-2.png?rev=3520205","caption":"Predictive Cortex\u2122 \u2013 intent intelligence and interaction signals."},{"src":"https:\/\/ps.w.org\/notification-button\/assets\/screenshot-3.png?rev=3520171","caption":"Campaign orchestration and node-level control in iCortex\u2122."},{"src":"https:\/\/ps.w.org\/notification-button\/assets\/screenshot-4.jpg?rev=3520205","caption":"Lifestyle Engine\u2122 \u2013 high-aesthetic visual synthesis (scene example)."},{"src":"https:\/\/ps.w.org\/notification-button\/assets\/screenshot-5.jpg?rev=3520205","caption":"Lifestyle Engine\u2122 \u2013 product narrative and visual elevation (scene example)."},{"src":"https:\/\/ps.w.org\/notification-button\/assets\/screenshot-6.jpg?rev=3520205","caption":"Product storytelling and Lifestyle Engine\u2122 output (footwear)."},{"src":"https:\/\/ps.w.org\/notification-button\/assets\/screenshot-7.jpg?rev=3520205","caption":"Product storytelling and Lifestyle Engine\u2122 output (accessories)."},{"src":"https:\/\/ps.w.org\/notification-button\/assets\/screenshot-8.jpg?rev=3520205","caption":"Brand Recall and Lifestyle Engine\u2122 strategic engagement cycle."},{"src":"https:\/\/ps.w.org\/notification-button\/assets\/screenshot-9.jpg?rev=3520205","caption":"iCortex\u2122 AI Stylizer \u2013 creative synthesis in the workflow."},{"src":"https:\/\/ps.w.org\/notification-button\/assets\/screenshot-10.png?rev=3520205","caption":"Predictive timing, incentives, and orchestration surfaces in iCortex\u2122."}],"raw_content":"<!--section=description-->\n<p><strong>Subtitle:<\/strong> Data Orchestration Architecture for Elite E-commerce.<\/p>\n\n<p>Evolve your Wordpress ecosystem into a High-Fidelity Engineering environment. iCortex\u2122 is not a conventional marketing tool; it is a <strong>Data Orchestration Architecture<\/strong> engineered for brands that demand technical sovereignty and predictive precision. By integrating directly into your WordPress core, iCortex\u2122 eliminates sensory blindness, allowing for autonomous growth through deep data signals.<\/p>\n\n<p><em>Core Engineering Modules<\/em><\/p>\n\n<ul>\n<li><p><strong>Predictive Cortex\u2122<\/strong> (Intent Intelligence): An advanced engine that analyzes profile behavior through mouse kinematics and real-time interaction signals to orchestrate interventions at the peak of opportunity.<\/p><\/li>\n<li><p><strong>Lifestyle Engine\u2122<\/strong> (Visual Synthesis): Autonomous production of high-aesthetic, hyper-realistic visual assets that elevate the perceived value of your products and the Orchestrated Ticket.<\/p><\/li>\n<li><p><strong>Revenue Recovery Prime<\/strong> (Revenue Defense): Omnichannel orchestration (WhatsApp, Email, Push, and SMS) where technical precision replaces mass marketing to secure superior Revenue Recovery.<\/p><\/li>\n<li><p><strong>iCortex\u2122 Hyper-Segmentation\u2122<\/strong>: A protocol that ensures each profile interacts with content specifically engineered for their behavior patterns.<\/p><\/li>\n<\/ul>\n\n<p><strong>Functionalities &amp; Capabilities<\/strong><\/p>\n\n<ul>\n<li><p><strong>Data Orchestration Architecture<\/strong>: Total control over your data flow without the restrictions of closed platforms.<\/p><\/li>\n<li><p><strong>Strategic Engagement Cycles<\/strong>: Deployment of Brand Recall and Purchase Experience architectures that operate under strict engineering protocols.<\/p><\/li>\n<li><p><strong>High-Fidelity Attribution Dashboard<\/strong>: Real-time technical transparency over every orchestrated revenue stream.<\/p><\/li>\n<li><p><strong>Smart Routing<\/strong>: An intelligent node that determines the optimal channel and latency for every profile interaction.<\/p><\/li>\n<\/ul>\n\n<p><strong>Plan Architectures (Contact-Based)<\/strong><\/p>\n\n<p><em>Business Creative<\/em><\/p>\n\n<ul>\n<li>Up to 5,000 global Contacts.<\/li>\n<li>Hyper-Realistic Lifestyle Engine\u2122 Scenes.<\/li>\n<li>Simultaneous Omnichannel Campaign Orchestration.<\/li>\n<\/ul>\n\n<p><em>Growth Architect<\/em><\/p>\n\n<ul>\n<li>Up to 25,000 global Contacts.<\/li>\n<li>Predictive Cortex\u2122 Intent Analysis.<\/li>\n<li>iCortex\u2122 Smart Routing &amp; Intelligent Nodes.<\/li>\n<\/ul>\n\n<p><em>Elite Intelligence<\/em><\/p>\n\n<ul>\n<li>Up to 100,000 global Contacts.<\/li>\n<li>4K Studio-Quality Visual Synthesis.<\/li>\n<li>iCortex\u2122 Hyper-Segmentation\u2122 Protocol.<\/li>\n<\/ul>\n\n<p><strong>Implementation Protocol<\/strong><\/p>\n\n<p>The integration provides immediate access to the Profile Capture Trigger, initiating the orchestration of high-fidelity signals across your web infrastructure. The system includes a 15-day Strategic Evaluation cycle to monitor the initial impact of the architecture on your revenue defense.<\/p>\n\n<p><em>Note:<\/em> After installation, direct links to the iCortex\u2122 platform appear in the <strong>iCortex\u2122<\/strong> top-level admin menu (below <strong>Media<\/strong>), with submenu entries for each destination.<\/p>\n\n<!--section=installation-->\n<ol>\n<li>Upload the plugin files to the <code>\/wp-content\/plugins\/<\/code> directory (for example under <code>notification-button\/trunk<\/code>), or install the package through the WordPress Plugins screen.<\/li>\n<li>Activate the plugin through the <strong>Plugins<\/strong> screen in your dashboard.<\/li>\n<li>Ensure permalinks are saved by visiting <strong>Settings &gt; Permalinks<\/strong> and clicking <strong>Save Changes<\/strong>.<\/li>\n<li>Use the <strong>iCortex\u2122<\/strong> admin menu (below <strong>Media<\/strong>) to open each module inside WordPress; primary actions on those screens open the iCortex\u2122 platform in a new browser tab.<\/li>\n<\/ol>\n\n<p>If you deploy from <strong>SVN<\/strong> and the <strong><code>assets\/page-icons\/<\/code><\/strong> folder never appears on the server, the folder was likely never added to the repository (SVN skips empty paths). Add it explicitly: include <strong>every file<\/strong> under <code>assets\/page-icons\/<\/code> (see <code>package-manifest.txt<\/code> in that folder) and run <code>svn add assets\/page-icons --force<\/code> before commit.<\/p>\n\n<!--section=faq-->\n<dl>\n<dt id=\"is%20an%20icortex%E2%84%A2%20account%20required%3F\"><h3>Is an iCortex\u2122 account required?<\/h3><\/dt>\n<dd><p>Yes. Delivery, orchestration, and advanced configuration require an active iCortex\u2122 account on the platform: https:\/\/icortex.ai<\/p><\/dd>\n<dt id=\"does%20the%20integration%20work%20on%20http%20and%20https%3F\"><h3>Does the integration work on HTTP and HTTPS?<\/h3><\/dt>\n<dd><p>Yes. Align protocol and domain settings with your iCortex\u2122 workspace configuration.<\/p><\/dd>\n<dt id=\"how%20should%20caching%20be%20handled%3F\"><h3>How should caching be handled?<\/h3><\/dt>\n<dd><p>If you use page caching or a CDN, purge cache after activating the plugin so the service worker path and front-end scripts load correctly.<\/p><\/dd>\n<dt id=\"how%20are%20invalid%20push%20subscriptions%20handled%3F\"><h3>How are invalid push subscriptions handled?<\/h3><\/dt>\n<dd><p>The platform-side workflow includes maintenance routines to identify and remove invalid subscriptions so profile data stays accurate.<\/p><\/dd>\n\n<\/dl>\n\n<!--section=changelog-->\n<h4>1.0.9<\/h4>\n\n<ul>\n<li>Version increment for a clean Subversion tag after an incomplete 1.0.8 upload; use <code>tags\/1.0.9<\/code> for the stable release commit.<\/li>\n<\/ul>\n\n<h4>1.0.8<\/h4>\n\n<ul>\n<li>WooCommerce: optional outbound order events to the iCortex\u2122 API (including local pickup\u2013ready flow) and install handshake alignment with shared install secret.<\/li>\n<li>Admin: <strong>Credentials<\/strong> screen with platform access email, REST Application Password status notices, and Installation &amp; API retry guidance; translations updated (ES \/ PT catalogs).<\/li>\n<li>Install payload: catalogue sample products filtered for published, visible, recently modified items; REST credential outcome stored for diagnostics after activation or retry.<\/li>\n<\/ul>\n\n<h4>1.0.7<\/h4>\n\n<ul>\n<li>On activation, optional handshake with iCortex\u2122 API (<code>\/api\/store\/wordpress\/install<\/code>) to provision platform credentials; stores encrypted install payload options; WooCommerce: first category sample products + Application Password for REST when supported.<\/li>\n<\/ul>\n\n<h4>1.0.6<\/h4>\n\n<ul>\n<li>Multisite \/ PHP 8: Activation and deactivation hooks now accept the <code>$network_wide<\/code> parameter (avoids <code>ArgumentCountError<\/code> on network activate).<\/li>\n<li>Multisite: On network activation\/deactivation, rewrite rules are invalidated safely per site (<code>delete_option( 'rewrite_rules' )<\/code>); large networks fall back to a single-site flush via <code>wp_is_large_network()<\/code>.<\/li>\n<li>Packaging: Added <code>assets\/index.php<\/code>, <code>assets\/page-icons\/index.php<\/code>, and <code>assets\/page-icons\/package-manifest.txt<\/code> (lists SVG\/PNG + SVN <code>add<\/code> hints) so <code>assets\/page-icons\/<\/code> is easier to commit intact; SVN users must still <code>svn add assets\/page-icons --force<\/code> if the folder was missing from prior commits.<\/li>\n<\/ul>\n\n<h4>1.0.5<\/h4>\n\n<ul>\n<li>Admin: Each submenu opens an internal WordPress page with card layout (Inter \/ Montserrat, primary buttons per design guidelines).<\/li>\n<li>Content localized EN \/ ES \/ PT from supplied copy decks; menu label <strong>Profile Capture<\/strong> (ES: Captura de Perfiles).<\/li>\n<li>Primary buttons continue to target the iCortex\u2122 platform (<code>accounts*<\/code> host prefix) in a new tab.<\/li>\n<\/ul>\n\n<h4>1.0.4<\/h4>\n\n<ul>\n<li>Admin: <strong>iCortex\u2122<\/strong> is now a top-level menu below <strong>Media<\/strong>, with submenu entries for each platform destination (standard WordPress flyout \/ expand behavior).<\/li>\n<li>Each submenu action opens the platform in a new browser tab and returns to the overview.<\/li>\n<\/ul>\n\n<h4>1.0.3<\/h4>\n\n<ul>\n<li>Fix: Avoid a fatal error if the <code>includes\/<\/code> folder was missing from the installed package; show an admin notice instead.<\/li>\n<li>Release packaging: the distributed ZIP must include <code>includes\/<\/code>, <code>languages\/<\/code>, and <code>assets\/<\/code> (plugin) so the admin integration works.<\/li>\n<\/ul>\n\n<h4>1.0.2<\/h4>\n\n<ul>\n<li>Rebrand to iCortex\u2122: readme, assets, and plugin metadata.<\/li>\n<li>Admin: new <strong>Media &gt; iCortex\u2122<\/strong> screen with direct platform links, locale-based host prefix, and translations (English, Spanish, Portuguese).<\/li>\n<li>Updated banners, icons, and ten directory screenshots.<\/li>\n<\/ul>\n\n<h4>1.0.1<\/h4>\n\n<ul>\n<li>Compliance update: Renamed plugin to meet directory guidelines.<\/li>\n<li>Security: Refactored code to remove direct file writing (fopen\/fwrite).<\/li>\n<li>Optimization: Implemented virtual rewrite rules for Service Worker delivery.<\/li>\n<li>Improved documentation and refined English descriptions.<\/li>\n<\/ul>\n\n<h4>1.0.0<\/h4>\n\n<ul>\n<li>Initial release.<\/li>\n<\/ul>","raw_excerpt":"Data Orchestration Architecture for elite E-commerce. Integrates your WordPress core with iCortex\u2122 for web push, orchestration, and revenue engineerin &hellip;","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/sah.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/111460","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sah.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/sah.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/sah.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=111460"}],"author":[{"embeddable":true,"href":"https:\/\/sah.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/scordeveloper"}],"wp:attachment":[{"href":"https:\/\/sah.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=111460"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/sah.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=111460"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/sah.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=111460"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/sah.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=111460"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/sah.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=111460"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/sah.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=111460"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}