Title: FlowMail Campaigns Author: flowpressuk Published: 15 agosto, 2026 Last modified: 4 outubro, 2026 --- Pesquisar plugins ![](https://ps.w.org/flowmail-campaigns/assets/banner-772x250.png?rev=3723723) ![](https://ps.w.org/flowmail-campaigns/assets/icon-256x256.png?rev=3723723) # FlowMail Campaigns Por [flowpressuk](https://profiles.wordpress.org/flowpressuk/) [Baixar](https://downloads.wordpress.org/plugin/flowmail-campaigns.1.5.14.zip) * [Detalhes](https://br.wordpress.org/plugins/flowmail-campaigns/#description) * [Avaliações](https://br.wordpress.org/plugins/flowmail-campaigns/#reviews) * [Instalação](https://br.wordpress.org/plugins/flowmail-campaigns/#installation) * [Desenvolvimento](https://br.wordpress.org/plugins/flowmail-campaigns/#developers) [Suporte](https://wordpress.org/support/plugin/flowmail-campaigns/) ## Descrição FlowMail Campaigns is an email marketing and automation workspace for WordPress and WooCommerce. It brings campaigns, customer journeys, subscribers, forms, product alerts, reporting, testing, and delivery diagnostics together inside WordPress so you can see not only what is configured, but what is actually happening and why. Instead of presenting automations as a disconnected list of triggers, FlowMail maps them across the customer journey: consent and signup, welcome, first purchase, post- purchase, loyalty, cart recovery, inactivity, win-back, and product interest. Guidance shows which automations are recommended, optional, alternatives, or protected from broader audiences. No external FlowPress service is required for plugin functionality. Operational data stays in WordPress, and email is sent through your site’s WordPress mail configuration or an SMTP server you choose. **Customer journey and automations** * Journey View organises automations across the real customer lifecycle. * Recommended, Alternative, Optional, System, and Protected guidance badges explain how each automation should be used. * Use single triggered emails or multi-step workflows without accidentally running duplicate paths. * Progressive High-value and VIP loyalty tiers can use different lifetime-spend thresholds and rewards. * Protected win-back paths separate standard inactive customers from High-value/ VIP recovery audiences. * New subscriber, welcome follow-up, lead magnet, anniversary, birthday, inactivity, and lifecycle automations are available where appropriate. * First-order, repeat-customer, post-purchase, review-request, loyalty, abandoned- cart, and purchase-inactivity automations can use WooCommerce completed-order data. **Campaigns and scheduling** * Create one-time email campaigns. * Schedule campaigns for a future date and time. * Run recurring campaigns on repeat schedules. * Use UK seasonal campaign starters for common retail dates. * Reuse templates, placeholders, and linked customer offers. * Keep campaigns separate from trigger-based automations so planned sends and lifecycle messaging remain easy to understand. **WooCommerce customer lifecycle** When WooCommerce is installed and active, FlowMail can use completed orders as the source of truth for customer lifecycle and value classification. * Recognise first-order and repeat customers. * Trigger post-purchase follow-up and review requests. * Reward High-value and VIP customers when configured spend thresholds are crossed. * Recover abandoned carts through a dedicated recovery workflow. * Re-engage inactive buyers with separate standard and High-value recovery paths. * Attribute the full value of a qualifying WooCommerce order back to FlowMail when a tracked email click or FlowMail-managed coupon provides strong evidence; open/ view-only matches are retained separately as assisted influence. * Capture an optional marketing opt-in alongside customer contact details at checkout. **Product interest alerts** Product alerts are request-driven rather than general lifecycle marketing. Customers can ask to receive: * Back-in-stock notifications. * Price-drop notifications. * Category new-arrival notifications. FlowMail keeps those requests separate from normal customer automations and can track real opens and clicks while excluding test sends from engagement figures. **Subscribers, audience, and preferences** * Subscriber profiles combine identity, acquisition source, preferences, interests, tags, lifecycle context, purchases, and engagement. * Customer Journey shows milestones such as welcome, purchases, loyalty, recovery, and email engagement. * Segments create reusable audience groups for campaigns and automations. * Subscriber preferences and unsubscribe handling let people control what they receive. * Double opt-in, hard/soft bounce, complaint, and suppression information help keep sending safer. * Acquisition tracking records how subscribers entered FlowMail, including forms, WooCommerce, imports, and retained source context. **Forms, Inbox, and reviews** * Subscriber signup forms. * Contact enquiry forms. * Selling enquiry forms. * WordPress block-editor and popup tools for FlowMail forms and subscriber-update content. * Internal Bot Shield to reduce automated form spam without relying on a third- party CAPTCHA service. * Inbox for managing incoming form enquiries. * Manual Google-style review badge and copy/paste review imports without a Google API connection. **Email operations and reporting** * Waiting to Send shows queued, future, due, held, or failed email. * Sent Emails keeps delivery history and source context. * Email Results compares Campaigns, Automations, and System email. * Track delivery, opens, clicks, outcomes, and conversions where supported. * Test sends remain separate so they do not distort real performance. * Campaign Activity provides drill-down into audience, queue, and result history. * Tracking Diagnostics helps verify open/click tracking and automation provenance. **Automation testing and diagnostics** FlowMail includes tools for checking automation behaviour before waiting for a live customer event. Depending on the workflow, the testing area includes: * Quick Test. * Trigger Simulator. * Customer Scan. * Audience Check. * Customer Simulation. * Time Travel. * Cart Inspector. * Waiting to Send. * Activity Feed. * Diagnostics. * Event Ledger. These tools help explain whether an automation should fire, who currently matches a rule, what is waiting to send, and what evidence exists behind an automation event. **Meaningful activity, not background noise** The Activity workspace combines audience, purchase, campaign, automation, review, content, and system events while keeping future work under Upcoming. Routine queue, cron, maintenance, and watchdog noise is hidden from the normal business timeline, but important failures remain visible. Full technical history is still available under System when deeper investigation is needed. **System email and branding** * Double opt-in confirmation, reminders, cleanup rules, delivery checks, and test sends are managed in one place. * Password-reset email content can be customised. * WordPress login branding can use a custom logo, background, button colour, and message. * Content publishing activity can be reviewed alongside email marketing and customer engagement. **Health, delivery, and send safety** * Health Check monitors the database, automation engine, queue, delivery, tracking, and watchdog. * Optional SMTP configuration can be used instead of the site’s default WordPress mail transport. * Sender-domain, SPF, DMARC, and DKIM checks help surface delivery configuration issues. * Watchdog and cron recovery help detect and restore required scheduled jobs. * Send-safety checks reduce the risk of duplicate, stale, or unsafe sends. * Mail transport failures are captured for diagnosis. **Built for WordPress control** FlowMail does not require a fixed external FlowPress API or hosted email-marketing account. Subscriber, campaign, automation, activity, and reporting data is managed inside WordPress. If you choose to use an SMTP provider, outgoing email is delivered through the SMTP server you configure. All features described here are included in FlowMail Campaigns; WooCommerce-specific features require WooCommerce to be installed and active. ### External services FlowMail Campaigns does not send operational data to FlowPress or to a fixed external API. By default, emails are sent through WordPress using `wp_mail()`, which uses the site’s own mail configuration. If the site administrator enables the optional custom SMTP setting, outgoing email is sent to the SMTP server entered by that administrator when an email is sent. Depending on the email being sent, this can include recipient email addresses, sender details, subject lines, message content, and technical email headers. The SMTP server is not supplied by FlowMail Campaigns and is not required for the plugin to work. Site administrators who enter their own SMTP server details should review the terms and privacy policy for that chosen mail provider. The plugin also includes an admin-only WP-Cron loopback diagnostic. When an administrator runs that diagnostic, the site sends a request to its own `wp-cron.php` URL to confirm that scheduled tasks can run. No FlowPress service is contacted for this check. The Reviews screen includes a manual Google-style review badge and a copy/paste importer for reviews that an administrator chooses to copy from their public Google review page. This feature does not contact Google, does not scrape Google, and does not use a Google API key. ## Capturas de tela [⌊FlowMail Overview brings together key activity, upcoming work, campaign and automation status, and clear routes to the areas that need attention.⌉⌊FlowMail Overview brings together key activity, upcoming work, campaign and automation status, and clear routes to the areas that need attention.⌉[ FlowMail Overview brings together key activity, upcoming work, campaign and automation status, and clear routes to the areas that need attention. [⌊Journey View maps automations across the customer lifecycle, showing recommended steps, optional extras, alternative workflows, progressive loyalty tiers, and protected win-back paths.⌉⌊Journey View maps automations across the customer lifecycle, showing recommended steps, optional extras, alternative workflows, progressive loyalty tiers, and protected win-back paths.⌉[ Journey View maps automations across the customer lifecycle, showing recommended steps, optional extras, alternative workflows, progressive loyalty tiers, and protected win-back paths. [⌊Campaigns keeps one-time, scheduled, recurring, and seasonal sends separate from trigger-based automations.⌉⌊Campaigns keeps one-time, scheduled, recurring, and seasonal sends separate from trigger-based automations.⌉[ Campaigns keeps one-time, scheduled, recurring, and seasonal sends separate from trigger-based automations. [⌊Audience management brings subscriber status, acquisition, preferences, interests, lifecycle context, and customer information together in one place.⌉⌊Audience management brings subscriber status, acquisition, preferences, interests, lifecycle context, and customer information together in one place.⌉[ Audience management brings subscriber status, acquisition, preferences, interests, lifecycle context, and customer information together in one place. [⌊Built-in forms cover subscriber signup, contact enquiries, and selling enquiries, with WordPress blocks, popups, and Bot Shield protection.⌉⌊Built-in forms cover subscriber signup, contact enquiries, and selling enquiries, with WordPress blocks, popups, and Bot Shield protection.⌉[ Built-in forms cover subscriber signup, contact enquiries, and selling enquiries, with WordPress blocks, popups, and Bot Shield protection. [⌊Segments create reusable audience groups so campaigns and automations can target the right subscribers without rebuilding filters each time.⌉⌊Segments create reusable audience groups so campaigns and automations can target the right subscribers without rebuilding filters each time.⌉[ Segments create reusable audience groups so campaigns and automations can target the right subscribers without rebuilding filters each time. [⌊Email Results compares delivery, opens, clicks, outcomes, and conversions across campaigns, automations, and system email.⌉⌊Email Results compares delivery, opens, clicks, outcomes, and conversions across campaigns, automations, and system email .⌉[ Email Results compares delivery, opens, clicks, outcomes, and conversions across campaigns, automations, and system email. [⌊Help & Status provides health checks and diagnostics for the database, queue, scheduling, email delivery, tracking, watchdog, and automation engine.⌉⌊Help & Status provides health checks and diagnostics for the database, queue, scheduling, email delivery, tracking, watchdog, and automation engine.⌉[ Help & Status provides health checks and diagnostics for the database, queue, scheduling, email delivery, tracking, watchdog, and automation engine. ## Blocos Este plugin disponibiliza 6 blocos. * FlowMail Subscribe Form * FlowMail Contact Form * FlowMail Selling Enquiry Form * FlowMail Email Preferences * FlowMail Subscriber Updates * FlowMail Product Category Subscribe ## Instalação 1. Upload the `flowmail-campaigns` folder to `/wp-content/plugins/`, or upload the ZIP through **Plugins Add New Upload Plugin**. 2. Activate **FlowMail Campaigns** from **Plugins Installed Plugins**. 3. Open **FlowMail Campaigns Settings** to configure sender details, SMTP options, forms, and safety settings. 4. Create your first campaign under **FlowMail Campaigns Campaigns**. ## Perguntas frequentes ### Does this use a third-party email service? No external email platform is required by default. Emails are sent through your WordPress mail configuration. If you configure SMTP, email delivery is handled by the SMTP provider you choose. ### What data is sent to external services? FlowMail Campaigns does not send operational data to FlowPress. If SMTP is enabled, email data is sent to the configured SMTP provider when an email is sent. This can include recipient email addresses, sender details, subject lines, message content, and email headers. ### Does FlowMail Campaigns connect to FlowPress? No external FlowPress connection is required for plugin functionality. Links to FlowPress are provided for documentation, support, and product information only. ## Avaliações Não há avaliações para este plugin. ## Colaboradores e desenvolvedores “FlowMail Campaigns” é um programa de código aberto. As seguintes pessoas contribuíram para este plugin. Colaboradores * [ flowpressuk ](https://profiles.wordpress.org/flowpressuk/) FlowMail Campaigns” foi traduzido para 1 localidade. Agradecemos aos [tradutores](https://translate.wordpress.org/projects/wp-plugins/flowmail-campaigns/contributors) por suas contribuições. [Traduzir o “FlowMail Campaigns” para seu idioma.](https://translate.wordpress.org/projects/wp-plugins/flowmail-campaigns) ### Interessado no desenvolvimento? [Navegue pelo código](https://plugins.trac.wordpress.org/browser/flowmail-campaigns/), consulte o [repositório SVN](https://plugins.svn.wordpress.org/flowmail-campaigns/) ou assine o [registro de desenvolvimento](https://plugins.trac.wordpress.org/log/flowmail-campaigns/) por [RSS](https://plugins.trac.wordpress.org/log/flowmail-campaigns/?limit=100&mode=stop_on_copy&format=rss). ## Registro de alterações #### 1.5.14 * Fixed the shared Settings save path so POSTed changes persist correctly across the FlowMail settings workspace, including Protection & Security controls. * Made repeat-offender learning sender-first: normal business/private domains are no longer globally blocked because one claimed sender repeatedly triggers protection. Qualifying abuse can block the exact address, while whole-domain escalation is reserved for stronger domain-level evidence such as disposable or DNS-invalid domains. * Expanded protected/shared-provider safeguards and remove protected providers from Additional blocked domains when settings are saved, reducing false-positive whole-domain blocks. * Added a non-destructive Repeat-offender learning preview to Test spam protection so administrators can see projected sender/domain learning, thresholds, protected- provider handling and domain-review behaviour without changing counters or blocklists. * Removed the completed legacy blocklist-review warning and clarified that Suspicious TLD entries are hard signup blocks for the entire listed top-level domain. #### 1.5.8 * WordPress.org release consolidating the FlowMail 1.4.x and 1.5.x workspace, reporting, diagnostics, settings, audience, automation and interface improvements since the previous directory release. * Added a shared FlowMail Control Centre and application header with clearer navigation, page guides, notifications, contextual actions and consistent workspace branding. * Expanded customer-journey, campaign, automation, email-results, WooCommerce attribution/ revenue, activity and health/status reporting. * Improved subscriber acquisition/source context, lifecycle and segment management, automation/watchdog diagnostics, spam-protection reporting and settings organisation. * Added a compact installed-version badge to the Control Centre branding card so the active FlowMail build is visible from every workspace screen. * Health Check continues to show the fuller installed-version information for troubleshooting and support. #### 1.5.7 * Alignment polish: vertically centered Dashicons inside shared-header buttons, including Notifications and Back to WordPress. * The left Control Centre now stays in normal document flow with the application header so their top edges remain aligned instead of drifting when the sidebar becomes sticky. #### 1.5.6 * Fixed the Notification Center/header collision structurally: the full application header now stays in normal document flow, while the sidebar remains sticky, and the notification summary gets an explicit non-collapsing gap below the header on server-rendered and fallback pages. #### 1.5.5 * Standardised page-specific application-header descriptions, improved header/notification spacing, removed duplicate Campaigns page actions, and surfaced the installed version clearly in Help & Status. #### 1.5.4 * Application-shell polish: shared header and left workspace navigation now use the same alignment/sticky offset so the top-left gap does not appear on mixed legacy/server-rendered pages. * Fallback/legacy workspace pages now place the branded FlowMail header and notification summary inside the same main column as server-rendered pages. * WordPress admin-menu branding now uses the same FlowMail controls-repeat icon shown inside the FlowMail workspace. * Header actions now follow one hierarchy: contextual actions first, a single primary action, Notifications, then Back to WordPress. * Removed the duplicate Back to WordPress control from the left workspace sidebar; the sticky application header is now the single global exit control. * Notification reporting is less repetitive: the all-clear state stays compact and active notifications are shown directly rather than behind a second Show notifications button. * Added consistent keyboard focus styling, improved responsive header wrapping, and surfaced the installed FlowMail version in Help & Status. #### 1.5.3 * Introduced one shared FlowMail application header with constant FlowMail Campaigns branding, consistent layout and global controls across the admin workspace. * Contextual header actions now change with the current page while Notifications and Back to WordPress remain predictable global controls. * Activity, WooCommerce, legacy Analytics, Email views and Revision History now use the same branded header pattern instead of bespoke headings. * Settings save action now lives in the shared header, and Subscribers/Email page titles align with their sidebar destinations. #### 1.5.2 * Removed the legacy duplicate Email & Sending section-navigation row so the shared secondary settings tabs are the single navigation system. * Scanned the other settings areas and confirmed Forms & Popup, Lifecycle & Segments, Protection & Security, and Technical & Data already use only the shared secondary tab system. #### 1.5.1 * Polished settings navigation: Page Guide copy now follows the selected settings task, Technical & Data replaces ambiguous Advanced naming, contextual settings links land on the correct task, and Save Settings uses one consistent sticky control. #### 1.5.0 * Settings information architecture: logical top-level order, focused secondary tabs, contextual settings retained beside their related workspace areas, cleaner Protection & Security grouping, and corrected Forms & Popup ownership of the Manage Preferences URL. #### 1.4.9 * Reporting consistency: separates stored Inbox/Spam messages from aggregate spam/ Bot Shield protection events. * Adds matching Today / 7 days / 30 days / Since reset protection ranges to Spam Protection settings and Inbox. * Clarifies protection reasons that may never create a stored Inbox message. #### 1.4.8 * Sidebar navigation cleanup: top-level items now use the same block layout as grouped items, preventing the active Overview background from rendering as a separate-looking blank row. * Added defensive guards so blank or incomplete sidebar items/children are never rendered by either the server or fallback navigation builder. #### 1.4.7 * Standardize FlowMail admin datetime display through the WordPress site timezone so BST/GMT is applied exactly once. * Store new Activity, system-log and automation-debug timestamps as real Unix epochs and migrate existing offset-adjusted entries once. * Correct UTC handling for Sent Emails, queue schedules, Campaign Activity delivery times, trigger history, dashboard recent activity and upcoming campaign times. * Keep site-local database timestamps local while converting UTC queue/delivery timestamps explicitly, avoiding fixed one-hour adjustments when daylight-saving time changes. #### 1.4.6 * Offer settings now deep-links reliably to the Customer offer section and briefly highlights the destination. * Sent Emails now uses the same Selected email actions pattern as FlowMail’s other managed tables; the inline Actions column is hidden and row actions are surfaced outside the table. * Managed tables now keep row actions outside the table in both Essential and Full views to avoid duplicated or clipped controls. * Scanned campaign, automation, results, queue and inbox table action patterns and kept their existing capability-specific actions while standardising where actions are shown. #### 1.4.5 * Fix abandoned-cart duplicate protection so Step 1/2/3 de-duplicate per recovery episode instead of across a subscriber’s lifetime history. * Allow the same customer to enter a new abandoned-cart recovery sequence after a later genuine abandonment. * Advance a recovery step safely when the same episode already has its queue row instead of retrying forever. * Make Activity report the actual queue suppression/failure reason and keep routine recovery-check noise out of the main timeline. #### 1.4.4 * Bootstrap timing hotfix: recurring maintenance schedules are now created at ` init` rather than during plugin bootstrap, preventing pre-init cron schedule enumeration from triggering translation loading too early. * Cron schedule labels avoid translation calls before `init`, while remaining translatable during normal WordPress runtime. * No sending, automation, attribution, or reporting logic changed. #### 1.4.3 * Compatibility hotfix: Campaign Activity and subscriber engagement no longer request the optional legacy `event_data` column from `pmcpc_email_events`. * Restricted-hosting hotfix: removed remaining FlowMail `dbDelta()` table-creation calls that could trigger disabled `set_time_limit()` warnings. * No sending, attribution, automation, queue or campaign behaviour changed. #### 1.4.2 * Restores real live KPI/reporting summaries where the 1.4.1 visual cleanup made operational pages feel too bare, while keeping the redundant Current view / Best for / Key tools cards removed. * Waiting to Send now shows live Waiting/unsent, Pending, Held/paused, Failed, and Sent (7 days) KPI cards sourced from the queue itself; the separate queue status bar is simplified so it does not repeat those counts. * Sent Emails now shows live Sent emails, Failed emails, Delivery rate, and Matching current filter KPI cards. Static Status filter and Current page cards remain removed. * Email Results retains its existing performance, engagement, attribution, and revenue KPI cards without adding duplicate summary cards. * Keeps the 1.4.1 cleanup on genuinely redundant cards such as Current section and fixed Key segments labels; live configuration and audience metrics remain. * No sending, automation, attribution, queue-processing, campaign, or subscriber runtime behaviour changed. #### 1.4.1 * Removes the static Current view / Best for / Key tools summary strip from Waiting to Send, Sent Emails, and Email Results; the Page guide now carries page-purpose guidance while the tabs provide navigation. * Removes Sent Emails summary cards that only repeated the selected status and page number; the useful matching-email count is retained as compact filter text. * Removes other low-value summary cards found in the same audit when they only restated UI context, including Current section / Double opt-in location cards in email branding settings and the fixed Key segments count. * Keeps live KPI, health, audience, configuration-state, campaign, automation, diagnostic, and reporting cards unchanged. * No sending, automation, attribution, queue, campaign, or subscriber runtime behaviour changed. #### 1.4.0 * Replaces the old Help & Shortcuts pattern with one consistent Page guide across FlowMail admin screens. * Every guide now separates what the page is for from how to use it, with clearer What to look for guidance where a page has health, validation, delivery, attribution, or legacy-data caveats. * Removes redundant self-navigation from guide actions, limits related-page links to a small contextual set, and keeps primary navigation/actions in the menu, page header, and row-action areas where they belong. * Waiting to Send, Sent Emails, and Email Results now have page-specific instructions instead of one generic tab explanation; Waiting to Send no longer links back to itself. * Page guides open automatically the first time a user sees a page in that browser, then stay collapsed on later visits to reduce visual clutter. * Renames legacy How this page works, Test and check, and Shortcuts headings to How to use this page, What to look for, and Related pages without changing sending, automation, attribution, or queue behaviour. #### 1.3.99 * Adds one shared action-help tooltip system across campaign, automation, reporting, Activity, queue, and sent-email action controls. * Every managed action gets a short plain-English description on hover and keyboard focus; specialised controls such as Trigger insight & matches, Event ledger, Delivery diagnostics, Offer settings, and workflow testing explain what they open or do. * Uses the same description source for cloned Selected row actions and original row-action menus so help text remains consistent wherever an action appears. * Tooltips are keyboard-accessible with role=tooltip and aria-describedby, stay within the browser viewport, and do not change any campaign, automation, sending, attribution, or queue behaviour. #### 1.3.98 * Rationalises campaign and automation actions across Campaigns, Automations, Email Results, Campaign Activity, Activity, Waiting to Send, and Sent Emails without removing capability-specific controls. * Makes each section own its job: Campaigns/Automations manage configuration and lifecycle actions, Email Results focuses on analysis, Activity focuses on chronology, Waiting to Send on queue operations, and Sent Emails on delivered-message history. * Standardises repeated action labels and order around Activity & results, Waiting to send, Preview email, Send admin test, Test & diagnostics, Event ledger, Revision history, Pause/Activate, and Manage campaign/automation. * Multi-step workflows now expose Activity & results, Waiting to send, Test workflow, and Event ledger alongside Edit steps; workflow step actions consistently use Edit step, Preview email, and Send admin test. * Email Results now links back with Manage campaign/automation instead of duplicating edit, duplicate, pause/activate, and test lifecycle actions that belong to the owning Campaigns or Automations section. * Activity events now keep the event title as the event-specific destination while adding explicit Activity & results and Manage campaign/automation context links. * Manage automation links from reporting, Activity, Waiting to Send, and Sent Emails now return to the focused Automations owner row; Manage campaign links return to the campaign editor. Queue and stored-email actions remain intact. * Not-created automations/workflows retain their Create automation/Create workflow action instead of being mislabeled as Activate. #### 1.3.97 * Cart recovery reporting now shows an unavailable dash instead of £0.00 when historical recoveries exist but no completed-order value was recorded. * Recovered-cart reporting now validates tracked recoveries against completed WooCommerce orders while preserving legacy recovery counts that pre-date order-ID tracking. * Clarifies recovered-cart and recovered-revenue descriptions so checkout activity is not presented as a completed recovery. #### 1.3.96 * Expands Health Check with a dedicated Attribution & revenue tracking check covering WooCommerce order hooks, order metadata read/write capability, FlowMail coupon attribution, tracked email-click attribution, abandoned-cart recovery tracking, and the configured attribution window. * Adds a workflow-level Cart recovery performance block to abandoned-cart Campaign Activity with abandoned carts detected, recovery emails sent, recovered carts, recovered revenue, recovery rate, and average recovered order value. * Stores the completed WooCommerce order ID and full order total on recovered abandoned- cart records so recovery revenue uses the completed order value rather than the original abandoned basket value, with order IDs deduplicated in reporting. * Refines purpose-aware Health wording so strong opens/clicks cannot be described as successful cart recovery without a recovered order, and product/sales health does not imply an unconfirmed conversion goal was reached. #### 1.3.95 * Unifies Campaign Activity goal, health, and funnel messaging around one purpose- aware goal rule so a campaign no longer says its goal was reached while the Health card says the same goal needs work. * Updates Campaign Activity revenue reporting to distinguish generated orders/revenue( FlowMail coupon or tracked click) from assisted orders/revenue (open/view-only evidence), using whole completed WooCommerce order value. * Labels influenced-order drill-down rows with the attribution evidence used and clarifies the difference between the selected outcome window and the configured revenue attribution window. #### 1.3.94 * Fixes the Overview so Store Revenue, Attribution Health, and Recent FlowMail- influenced Orders always render on the main control centre, including a useful zero state before the first attributed sale. * Adds abandoned-cart-specific recovery metrics: recovered carts, recovered cart value, and an observed recovery rate based on abandoned-cart records rather than all FlowMail-attributed orders. * Clarifies that recovered cart value is the original abandoned-cart value, while generated revenue continues to use the completed whole-order value when FlowMail coupon/click evidence exists. #### 1.3.93 * Formalises whole-order FlowMail revenue attribution: when a FlowMail-managed coupon or tracked email click leads to a purchase, the full WooCommerce order value is credited, including items that were not shown or linked in the original email. * Separates strong generated-sale evidence (FlowMail coupon or tracked click) from weaker assisted evidence (open/view only) while retaining one FlowMail-influenced total. * Prevents double counting when an order has multiple FlowMail signals; coupon use remains the strongest signal, followed by tracked click, then open/view assistance. * Renames revenue reporting to distinguish FlowMail-generated, FlowMail-assisted, and FlowMail-influenced orders/revenue more clearly. * Makes Attribution Health business-readable with Coupon-driven orders, Email-click orders, Open/view assisted orders, and overall coverage. * Updates Recent FlowMail-influenced Orders so each order explains whether the evidence was a coupon, tracked email click, or open/view assistance. #### 1.3.92 * Refines Overview with a slimmer healthy-state summary and clearer separation between intervention status and operational delivery metrics. * Keeps Customer Journey stages directly clickable from Overview and retains meaningful- only Latest Activity with Upcoming separated from history. * Improves zero-state revenue attribution so attributed orders and revenue collapse into one explanatory card until evidence exists. * Adds deterministic revenue attribution when a WooCommerce order uses a FlowMail- managed campaign, seasonal, or recipient coupon. * Persists coupon attribution onto the WooCommerce order so later coupon cleanup does not remove historical FlowMail revenue credit. * Prevents double counting when the same order has both a FlowMail coupon and tracked email engagement; the coupon is treated as the strongest conversion signal. * Adds coupon-assisted attribution to Recent Attributed Orders and Attribution Health reporting. #### 1.3.91 * Refined Overview into a clearer business control centre with a customer-journey health strip near the top. * Added stage-level journey guidance for consent/signup, welcome, first purchase, post-purchase, loyalty, cart recovery, win-back, and request-driven product alerts. * Made the healthy state compact while reserving Needs Action for genuine intervention such as failures, moderation, broken scheduling, and setup gaps. * Grouped KPI cards by business purpose and clarified current/all-time/30-day context on headline metrics. * Split Latest Activity and Upcoming into separate side-by-side panels and tightened the Overview feed to the most recent meaningful events. #### 1.3.90 * Treats correctly ordered High-value and VIP spend tiers with distinct offers as an intentional progressive loyalty path rather than an overlap warning. * Shows a positive Progressive tiers status when VIP is above High-value and the two linked rewards are distinct. * Keeps genuine tier problems actionable: reversed/equal thresholds, missing threshold data or identical tier offers still show Review tiers with an explanation. * Keeps anniversary and birthday visible as optional loyalty extras without making a healthy progressive tier setup look like a warning. #### Earlier releases * Earlier releases contained incremental improvements to campaigns, automations, subscriber management, email delivery, reporting, WooCommerce integration, forms, reviews, diagnostics, security and admin usability. ## Meta * Versão **1.5.14** * Última atualização **2 dias atrás** * Instalações ativas **Menos de 10** * Versão do WordPress ** 6.3 ou superior ** * Testado até **7.1.2** * Versão do PHP ** 7.4 ou superior ** * Idiomas * [English (US)](https://wordpress.org/plugins/flowmail-campaigns/) e [Lao](https://lo.wordpress.org/plugins/flowmail-campaigns/). * [Traduzir para seu idioma](https://translate.wordpress.org/projects/wp-plugins/flowmail-campaigns) * Tags * [automation](https://br.wordpress.org/plugins/tags/automation/)[email](https://br.wordpress.org/plugins/tags/email/) [Email Marketing](https://br.wordpress.org/plugins/tags/email-marketing/)[newsletter](https://br.wordpress.org/plugins/tags/newsletter/) [woocommerce](https://br.wordpress.org/plugins/tags/woocommerce/) * [Visualização avançada](https://br.wordpress.org/plugins/flowmail-campaigns/advanced/) ## Classificações Ainda não foi enviada nenhuma avaliação. [Sua avaliação](https://wordpress.org/support/plugin/flowmail-campaigns/reviews/#new-post) [Ver todas avaliações](https://wordpress.org/support/plugin/flowmail-campaigns/reviews/) ## Colaboradores * [ flowpressuk ](https://profiles.wordpress.org/flowpressuk/) ## Suporte Tem algo a dizer? Precisa de ajuda? [Ver fórum de suporte](https://wordpress.org/support/plugin/flowmail-campaigns/)