Tracked URL and history limits are gone. Existing data and settings are untouched, and retention now keeps more than before rather than less.<\/p>","1.0.2":"
Hardening and documentation fixes only. No changes to stored data or settings.<\/p>","1.0.0":"
Initial release.<\/p>"},"ratings":{"1":0,"2":0,"3":0,"4":0,"5":1},"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3704058,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3704058,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3704058,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3704058,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.3"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3704058,"resolution":"1","location":"assets","locale":"","width":1280,"height":760},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3704058,"resolution":"2","location":"assets","locale":"","width":1280,"height":760},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3704058,"resolution":"3","location":"assets","locale":"","width":1280,"height":760},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3704058,"resolution":"4","location":"assets","locale":"","width":1280,"height":1080}},"screenshots":{"1":"Dashboard \u2014 vitals cards with budgets, status pills, sparklines, incidents and recent changes","2":"Change ledger \u2014 filterable timeline of every site change","3":"Incident detail \u2014 breach versus budget and baseline, with the changes from the 72 hours before (ranked cause attribution shown is a Pro feature)","4":"Settings \u2014 API key, tracked URLs, performance budgets and notifications"}},"plugin_section":[262246],"plugin_tags":[8531,181034,187460,5603,247],"plugin_category":[54],"plugin_contributors":[281675],"plugin_business_model":[],"class_list":["post-343106","plugin","type-plugin","status-publish","hentry","plugin_section-dashboard-widgets","plugin_tags-activity-log","plugin_tags-client-reports","plugin_tags-core-web-vitals","plugin_tags-monitoring","plugin_tags-performance","plugin_category-security-and-spam-protection","plugin_contributors-costibotez","plugin_committers-costibotez"],"banners":{"banner":"https:\/\/ps.w.org\/aftercare\/assets\/banner-772x250.png?rev=3704058","banner_2x":"https:\/\/ps.w.org\/aftercare\/assets\/banner-1544x500.png?rev=3704058","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/aftercare\/assets\/icon-128x128.png?rev=3704058","icon_2x":"https:\/\/ps.w.org\/aftercare\/assets\/icon-256x256.png?rev=3704058","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/aftercare\/assets\/screenshot-1.png?rev=3704058","caption":"Dashboard \u2014 vitals cards with budgets, status pills, sparklines, incidents and recent changes"},{"src":"https:\/\/ps.w.org\/aftercare\/assets\/screenshot-2.png?rev=3704058","caption":"Change ledger \u2014 filterable timeline of every site change"},{"src":"https:\/\/ps.w.org\/aftercare\/assets\/screenshot-3.png?rev=3704058","caption":"Incident detail \u2014 breach versus budget and baseline, with the changes from the 72 hours before (ranked cause attribution shown is a Pro feature)"},{"src":"https:\/\/ps.w.org\/aftercare\/assets\/screenshot-4.png?rev=3704058","caption":"Settings \u2014 API key, tracked URLs, performance budgets and notifications"}],"raw_content":"\n
Know what changed. Know what it cost. Prove what you did.<\/strong><\/p>\n\n Aftercare watches your WordPress site after launch. Every day it records your real-world Core Web Vitals; every second it records the changes made to the site. When performance regresses, it connects the two \u2014 an incident opens, an email goes out, and the incident page shows every change from the 72 hours before the regression, right next to the trend.<\/p>\n\n It is built for agencies and freelancers who maintain client sites on monthly care plans \u2014 and for any site owner who wants an answer to \"why did the site just get slower?\" that is based on data instead of guesswork.<\/p>\n\n This plugin is complete in itself. Nothing here is capped, timed or held back: every URL you add is monitored, vitals are kept for thirteen months and the change ledger is kept in full.<\/p>\n\n A separate add-on plugin, distributed outside this directory, adds ranked cause attribution and white-label monthly client reports with Slack and webhook delivery. It is not required, and this plugin does not check for a licence, prompt for one or change behaviour without it.<\/p>\n\n Aftercare is built and maintained by Nomad Developer<\/a>.<\/p>\n\n Aftercare does not phone home. CrUX data is fetched directly from Google's API using the key you provide. The optional RUM beacon posts anonymous metric values (no cookies, no personal data, no IPs stored) to your own site's REST API and can be disabled at any time.<\/p>\n\n Aftercare connects to the following external services. No connection is made until you configure it.<\/p>\n\n Chrome UX Report API (Google)<\/strong> \u2014 used to retrieve real-user Core Web Vitals field data for the URLs you choose to track. Once you enter your own Google API key, the plugin sends your tracked URLs (or your site's origin) together with that API key to From the Chrome UX Report (field data from real Chrome users), fetched daily with your own Google API key. Optionally, a small RUM beacon collects vitals from your own visitors as a second source.<\/p><\/dd>\n No. Tracked URLs are unlimited, vitals are kept for thirteen months and the ledger is kept in full. Both retention windows can be shortened with the By default all Aftercare tables and options are removed on uninstall. Tick \"Keep Aftercare data\" in Settings to preserve them.<\/p><\/dd>\n Yes. \ud83d\udcc8 Core Web Vitals monitor<\/h4>\n\n
\n
\ud83d\udcb0 Performance budgets and incidents<\/h4>\n\n
\n
\ud83d\udcd2 Change ledger<\/h4>\n\n
\n
\ud83e\uddf0 Fits into your workflow<\/h4>\n\n
\n
wp aftercare pull<\/code>, wp aftercare check<\/code>, wp aftercare status<\/code> and wp aftercare run<\/code> for scripted setups and real server crons<\/li>\n\ud83d\udd12 Private by design<\/h4>\n\n
\n
Privacy<\/h4>\n\n
External Services<\/h3>\n\n
https:\/\/chromeuxreport.googleapis.com<\/code> once per day per URL. No visitor data, personal data or site content is sent. This service is provided by Google: Terms of Service<\/a>, Privacy Policy<\/a>. If no API key is configured, no request is ever made.<\/p>\n\n\n\n
\n
Where does the vitals data come from?<\/h3><\/dt>\n
Does this plugin limit anything?<\/h3><\/dt>\n
aftercare_vitals_retention_days<\/code> and aftercare_ledger_retention_days<\/code> filters if you would rather keep the tables small.<\/p><\/dd>\nWhat happens to my data when I delete the plugin?<\/h3><\/dt>\n
Can I run the checks from a server cron instead of WP-Cron?<\/h3><\/dt>\n
wp aftercare run<\/code> executes the full daily pipeline (CrUX pull, RUM aggregation, breach detection, retention). Aftercare also uses Action Scheduler automatically when another plugin (such as WooCommerce) provides it.<\/p><\/dd>\n\n<\/dl>\n\n\n1.0.3<\/h4>\n\n
\n
1.0.2<\/h4>\n\n
\n
1.0.1<\/h4>\n\n
\n
crux_url<\/code> (the tracked URL) or crux_origin<\/code> (the whole site, used when the URL-level record is too thin)<\/li>\n1.0.0<\/h4>\n\n
\n