MailPoet 5.37 Adds Tracking Consent History for WooCommerce
MailPoet 5.37.0, released September 1, 2026, adds a more complete record of how subscribers manage email open and click tracking. Store operators can review a subscriber’s consent state, change time, collection source, and consent wording. That information can also be preserved through supported import and export workflows.
The update extends the consent work introduced in MailPoet 5.36.0, which added tracking-consent collection at signup and segmentation options for reporting and email activity. Version 5.37.0 also fixes consent loss affecting WooCommerce guest checkout, WordPress registration and comment forms, and email-footer opt-out links.
For WooCommerce stores, this is more than an administrative improvement. Changes in tracking consent can affect how teams interpret opens, clicks, automations, abandoned-cart activity, and WooCommerce revenue attribution for affected subscribers.
Need help checking this on your WordPress, Google Ads, Analytics, local SEO, or website setup? Splinternet Marketing can review the issue and help you prioritize the next fix.
Why the update matters for revenue and reporting
Tracking consent and marketing subscription consent are separate records. A subscriber may remain subscribed to marketing email while opting out of open and click tracking. Conversely, a tracking-consent record does not prove that the person agreed to receive marketing email.
That distinction matters when reviewing performance after the update. If more subscribers are marked as opted out, never asked, or otherwise unavailable for tracking, engagement and revenue reports may become less comparable with earlier periods even when campaign or store performance has not changed by the same amount. Historical comparisons can also become less consistent if consent defaults or collection points change.
WooCommerce order, payment, account, and other transactional messages should be reviewed separately from MailPoet marketing and automation email. A tracking-consent checkbox should not be treated as proof of marketing consent or as an automatic instruction to suppress transactional notifications. Keep those message types separate during testing and internal documentation.
What to do next
- Update in staging first. Confirm the WordPress, WooCommerce, MailPoet, MailPoet Premium, theme, checkout-field, caching, and custom-code versions in the test environment. Take a recent backup before production changes.
- Test every checkout path. Run logged-in customer and guest checkout tests with the tracking checkbox selected and cleared. Include a returning subscriber, a new subscriber, and a failed or abandoned checkout where applicable. Do not rely only on a successful logged-in order.
- Audit custom integrations. If a custom checkout, registration flow, form builder, headless frontend, or theme integration sends subscriber data to MailPoet, confirm that the relevant checkbox value, consent wording, timestamp, source, and subscriber update are handled through MailPoet’s supported public PHP API.
- Reopen existing forms and emails. Confirm that the consent checkbox is present where intended and that tracking opt-out links remain available in email footers. Theme overrides, third-party email editors, and customized templates can interfere with updates.
- Validate import and export. Export a small test list, inspect the consent metadata, re-import it into staging, and confirm that the history remains available. A new history field cannot recreate consent that was never collected.
- Segment reporting after deployment. Compare consented, opted-out, and never-asked subscribers separately before evaluating changes in opens, clicks, automations, abandoned-cart activity, or WooCommerce revenue attribution.
MailPoet 5.37.0 gives store teams better visibility into consent changes, but the operational value depends on implementation quality. Document the versions tested, the checkout paths covered, and how consent state is handled in reporting before changing production email flows.
Sources
Need help checking this on your WordPress, Google Ads, Analytics, local SEO, or website setup? Splinternet Marketing can review the issue and help you prioritize the next fix.
This article is for informational purposes only and reflects general marketing, technology, website, and small-business guidance. Platform features, policies, search behavior, pricing, and security conditions can change. Verify current requirements with the relevant platform, provider, or professional advisor before acting. Nothing in this article should be treated as legal, tax, financial, cybersecurity, or other professional advice.
Editorial note: Splinternet Marketing articles are researched from cited platform, documentation, regulatory, and industry sources. AI may assist with drafting and review; final content is checked for source support, practical usefulness, and platform/date accuracy before publication.