Here are the versions of the AI Web Push plugin for WordPress, from newest to oldest, with what changed in each one. Your site gets the new version through the plugin updates in the WordPress dashboard. When the file of a version is published, the button next to the date downloads that version.
Version 1.9.3
What changes and what to do is in the post The Chrome notification prompt changed on Android.
New
- Ready for the new Chrome 155 notification prompt on Android, which shows up as a discreet card at the top and hides on its own when the reader does not tap it. The plugin now treats this case as "no answer".
- New permission_timeout event in the dataLayer (GTM and GA4), for the Chrome card that hid or was closed without an answer. permission_denied now only counts those who said no.
- Visitors who allow notifications later, through the site settings at the icon next to the address, are now registered right away, without reloading the page. If the site was closed when the person turned it on, the registration happens on the next visit to the site. Subscription events get the site_controls and permission_preexisting origins, and the new subscription_skipped event shows that the browser was already registered.
- A notice in the WordPress dashboard for sites that use the browser default prompt (Modal personalizado turned off), explaining the Chrome change on Android and leading to the Modal tab. It only shows to administrators, on the Dashboard, on Plugins and on the plugin screens, and each administrator can choose not to see it again.
Improvements
- The "Intervalo de reexibição" (reshow interval) field, in the Modal tab, now always shows, with Modal personalizado on or off. It applies to the modal cancel button and also when the Chrome card hides or is closed without an answer.
- Sites that do not change the setting keep the default of 1440 minutes (24 hours).
- Visitors the plugin has already recorded as subscribed in that browser are not registered again.
- New installations of the plugin now start with Modal personalizado turned on. On sites that already use the plugin, the modal setup does not change, including those that never touched the Modal tab.
Fixes
- Visitors who granted permission outside the plugin prompt were left unregistered and never received push. This is fixed.
- The Chrome 155 card that hid without an answer was counted as if the reader had said no and held a new request for 24 hours. Now the new request follows the Intervalo de reexibição.
- Visitors who remove the notification permission and later allow it again, with the site open, are registered again.
- A failure to generate the token on the first acceptance no longer prevents a new attempt on later visits.
Version 1.9.2
New
- The interval for the capture modal to show again after a cancellation can now be set in minutes, instead of being fixed at 24 hours.
- A value of 0 shows the modal again on the next page the visitor opens. While the visitor stays on the same page, the modal does not come back, and the delay and the scroll do not ask again after the cancellation.
- In the dashboard, the field shows the conversion to hours next to it while the value is typed (for example, 1440 minutes = 24 hours).
Improvements
- The interval field only shows when Modal personalizado is active, following the same pattern as the other modal options.
- Sites that do not change the setting keep the 24 hour behavior.
- If the visitor accepts in the modal and then closes the browser prompt, the prompt does not come back right away. The site waits 24 hours, so the browser does not block future requests.
Version 1.9.1
New
- New push_received_while_away event in the plugin JavaScript, fired when the visitor returns to the site after receiving a notification while the site was off screen. Sites can react with aiWebPushFront.on('push_received_while_away', ...).
Improvements
- Notifications sent without a destination link now open the site home page when the visitor clicks them.
Fixes
- Fixed the click on the notification when the site or the home screen app is already open, even in the background. The visitor is now taken to the notification page, instead of just going back to the page they were on.
- On iPhone, the app added to the home screen waits in the background, so the problem happened on most clicks. With the fix, the click opens the destination of the campaign or of the welcome message on iPhone too.
Version 1.9.0
New
- New Modal tab in the dashboard, bringing together in one place the settings of the permission capture modal.
- Modal position configurable per device (desktop and mobile), with nine ready positions (corners, edges and center) or a custom position as a percentage of the screen.
- Configurable modal background, with no overlay, dark or light, and an option to block clicks and page scrolling while the modal is open.
- Schematic preview in the dashboard, showing in real time where the modal appears on desktop and on mobile according to the chosen options.
Improvements
- The option is now called Modal personalizado, making it clear that it controls the plugin modal, and not the browser native prompt, which cannot be customized.
- Position and overlay only show when the custom modal is active, to avoid setting something that does not apply to the native prompt.
Fixes
- Fixed the case where the modal background could get stuck on screen when the prompt was triggered by the delay and by the scroll at the same time.
- When the overlay blocks the page, the visitor can no longer scroll the content under the modal either.
- On narrow screens, the side margins of the modal are symmetrical, without touching one of the sides.
Version 1.8.3
Improvements
- More accurate detection of the visitor location on sites that use a CDN or reverse proxy (such as Cloudflare), improving the quality of the country data of new subscribers.
Fixes
- Fixed the recording of the visitor IP behind a CDN or proxy, which in some cases pointed to the network server (for example, United States) instead of the subscriber real country.
Version 1.8.2
New
- When notifications are allowed, the plugin now records the page and the traffic source of the visitor (including campaign parameters in the URL).
- This data feeds the capture by campaign report in the dashboard, helping to identify which ads and links bring new subscribers.
Improvements
- Safer sending of the access URL information to the server, avoiding failures when the page has campaign parameters in the address.
Version 1.8.1
New
- In the experimental Meta WebView exit, you can now choose whether the visitor will see the guidance modal to open in the browser.
- New option to try to open the page in Chrome automatically when the visitor comes from Instagram, Facebook or Messenger on Android.
- You can use only the modal, only the automatic opening, or both together (automatic opening with a backup modal if the exit fails).
Improvements
- Clearer WebView exit settings in the dashboard, with warnings when no exit mode is active.
- More robust opening in the external browser on Android, with better handling when Chrome is not available.
- On iOS, the behavior is still guided by the modal, since the system does not allow forcing the page to open in another browser.
Version 1.7.13
New
- New 'Manutenção' (maintenance) tab added to the plugin settings dashboard to help with diagnosis and technical support.
Improvements
- Added a new 'Debug' option that shows the raw and detailed data returned by the backend while events are sent.
Fixes
- Fixed the handling of special characters, with HTML entities decoded and ampersand symbols ('&') removed automatically from titles, categories and page classifications to avoid data communication errors with the backend.
Version 1.7.12
Improvements
- Better real time delivery of notifications when the visitor is actively browsing the site, ensuring campaigns and welcome messages are received right away.
Fixes
- Fixed how links and campaigns open when the user already has the site open in the browser, ensuring that the click on the notification goes to the right destination page.
- Adjusted the processing of background notification click data for better compatibility with different Firebase Cloud Messaging payload formats.
Version 1.7.10
New
- New 'Migração' (migration) tab in the plugin admin dashboard, for moving Web Push subscriber bases from other platforms to AI Web Push.
- The new tab has an advanced option that lets your site serve its own Service Worker during the migration, with guidance from AI Web Push support.
Improvements
- A visual indicator in the new 'Migração' tab shows whether your own Service Worker file is correctly available on the site, making it easier to follow the migration.
- The confirmation message when saving settings now correctly reflects the active tab, giving clearer feedback for each settings area of the plugin.
Version 1.7.9
New
- You can now choose exactly on which pages, posts or categories the notice to open in the external browser is shown.
- New option to show or hide the close button (X) on the notice, giving more control over the experience.
Improvements
- The notice now shows every time the visitor arrives through the in app browser of social networks, without being muted between visits.
- Detection of in app browsers was expanded to cover more access scenarios coming from Meta networks.
- The attempt to open in the external browser became more robust, with a cascade of alternatives and a clear instruction if none of them works in the source app.
- The default notice text is now more direct and focused on continuing to read.
Fixes
- Fixed a case where the notice could wrongly appear on the site home page when a selected page was used as the home.
- Fixed the notice firing on listings, archives and screens that do not match the chosen page, post or category.
Version 1.7.8
New
- New experimental option to detect browsing through Instagram, Facebook and Messenger and guide the visitor to open the page in the external browser.
Improvements
- The modal for this experience now has customizable texts to match the voice of each site.
- Specific measurements were added to track views, external opening attempts and the results of the flow.
Fixes
- Capturing new subscribers now has a fallback path in WebView environments, reducing losses in contexts with limited support for push notifications.
Version 1.7.7
New
- Expanded compatibility with multilingual sites for the Web Push notification flow.
Improvements
- Delivery of the notifications file became more consistent on pages with a language prefix.
- More stable notification registration in environments with automatic translation turned on.
Fixes
- Fixed a problem that could change the notifications file on translated pages and cause failures.
- Adjusted the behavior to keep the same result between the main URL and the language URLs.
Version 1.7.6
New
- The Changelog tab in the dashboard now shows the version history, making it easier to look up earlier changes.
Improvements
- Internal improvements in loading the changelog to reduce temporary display failures in the dashboard.
- When the full history is not available, the system keeps showing it with an automatic fallback to the current version.
Fixes
- The changelog view in the admin became more stable when the history endpoint is partly unavailable.
Version 1.7.5
New
- New browser_not_supported event in GTM and the dataLayer, fired when the browser does not support push notifications.
- Sites can react with JavaScript (aiWebPushFront.on('browser_not_supported', ...)) to hide buttons or show other messages.
Improvements
- Automatic detection of support for the Notification API before any plugin operation.
- The total of GTM events went from 8 to 9, now covering the case of a browser without support.
Fixes
- Removed the 'Notification is not defined' error that happened in WebViews (Instagram, Facebook, TikTok), iOS Safari outside a PWA and contexts without HTTPS.
- The error no longer shows up in Microsoft Clarity or in the browser console.
Version 1.7.4
New
- Metric events exposed to GTM, telling apart the flow through the custom modal or the native prompt.
- Debug mode through localStorage to inspect events in the console (ai-web-push-debug=true).
Improvements
- Standard prefix for GTM events, ai_web_push_<event> and provider ai_web_push.
- Event origin fixed to correctly tell the custom modal from the native prompt.
Fixes
- Clicks on the custom modal now fire the proper events (modal_accepted and modal_dismissed).