Skip to content

Document manual A/B test winner selection for Segment Emails - #967

Draft
promptless-for-oss wants to merge 3 commits into
mautic:7.2from
Promptless:promptless/pr-17303-manual-ab-winner-selection
Draft

promptless-for-oss wants to merge 3 commits into
mautic:7.2from
Promptless:promptless/pr-17303-manual-ab-winner-selection

Conversation

@promptless-for-oss

@promptless-for-oss promptless-for-oss commented Sep 8, 2026 •

Copy link
Copy Markdown
Contributor

Open in Promptless

Mautic 7 lets marketers manually pick an A/B test winner while a Segment Email test is running, instead of only accepting the automatic, statistics-based winner. This adds a short passage to the "Sending and determining the winner" section of the Emails documentation explaining that, from the A/B Test panel, you can select the Make winner trophy action on any Active variant to override Mautic's statistical recommendation and end the test on the variant you choose. It documents the eligibility rule (Active variants only, once the test has started sending), the filled-vs-outline trophy cue, and a note listing what confirming does: sets the chosen variant as the main Email, turns off the other variants, stops the test, and resets the A/B test stats.

Source: mautic/mautic PR #17303, which fixes issue #16318.

Trigger Events


Review feedback addressed (@adiati98, 2026-09-15): "please address the Vale warnings."

  • Applied: cleared the four Mautic.FeatureList Vale suggestions on the added passage by changing "published variant(s)" to "Active variant(s)" on lines 209 and 211, consistent with the rule's published → "Active or Available" mapping and the existing "Active variants" phrasing at line 120. vale docs/channels/emails.rst now reports 0 findings on the lines this PR introduced.
  • Not addressed (out of scope): the remaining Vale findings all sit on pre-existing lines this PR never touched (335, 469, 597, 670, 857, 858, 890, 901, 943, 969); this PR keeps its diff minimal and does not modify unrelated lines.

Comment thread docs/channels/emails.rst Outdated

After the wait time passes, Mautic evaluates each variant against your chosen winner criteria, marks the best performer with a **Winner** badge in the panel, and sends the winning version to the remaining Contacts.

While the test is running, you don't have to wait for the automatic pick. In the **A/B Test** panel, select the **Make winner** trophy action on a published variant's row to override Mautic's statistical recommendation and end the test on the variant you choose. The action appears on each published variant's row once the test has started sending.

@promptless-for-oss promptless-for-oss Sep 8, 2026 •

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Citation

Verifies the Make winner trophy action's eligibility gate: canMakeWinner = variants.parent.variantStartDate and isPublished, which appears on each published variant's row once the parent test has started sending. From PR mautic/mautic#17303 "Allow manual selection of A/B test winners" (fixes mautic/mautic#16318).

Source: row.html.twig:50–62 · fe5c978

Comment thread docs/channels/emails.rst

Before you promote a variant, review what confirming does. Mautic:

* sets the chosen variant as the main Email

@promptless-for-oss promptless-for-oss Sep 8, 2026 •

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Citation

Verifies confirm_make_winner translation string: "Warning: making %name% the winner will set it as the main item/parent, unpublish the other variants, stop the A/B test, and reset current A/B test stats." Backs the note's four bulleted consequences of confirming the Make winner action (lines 217-220).

Source: messages.ini · caa0ad1

Comment thread docs/channels/emails.rst Outdated

After the wait time passes, Mautic evaluates each variant against your chosen winner criteria, marks the best performer with a **Winner** badge in the panel, and sends the winning version to the remaining Contacts.

While the test is running, you don't have to wait for the automatic pick. In the **A/B Test** panel, select the **Make winner** trophy action on a published variant's row to override Mautic's statistical recommendation and end the test on the variant you choose. The action appears on each published variant's row once the test has started sending.

@promptless-for-oss promptless-for-oss Sep 8, 2026 •

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Citation

Verifies the Make winner trophy action renders inside the A/B Test panel: the h3 heading at L23 uses translation key mautic.core.variants.abtest ("A/B Test"), and the variant list (which contains the winner trophy action per Variant/row.html.twig) is included directly inside that panel at L37-L43. This is a separate panel/button from the A/B Test Stats modal (opened via a distinct button at L137-L148 / L151-L163, titled via mautic.core.ab_test.stats = "A/B Test Stats"). Confirms the corrected location claim.

Source: abdetails.html.twig:17–44 · fe5c978

Comment thread docs/channels/emails.rst Outdated

While the test is running, you don't have to wait for the automatic pick. In the **A/B Test** panel, select the **Make winner** trophy action on a published variant's row to override Mautic's statistical recommendation and end the test on the variant you choose. The action appears on each published variant's row once the test has started sending.

The variant the statistics currently favor shows a filled trophy, and the other published variants show an outline trophy. The trophy state is only a cue - you can promote any published variant, whichever trophy it shows.

@promptless-for-oss promptless-for-oss Sep 8, 2026 •

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Citation

Verifies the trophy fill/outline cue: isWinner (statistics-favored variant, L11) renders the filled icon ri-trophy-fill at L59, while other published variants render the outline icon ri-trophy-line. canMakeWinner (L13) governs which variants show the action at all and does not depend on isWinner, confirming the trophy state is only a visual cue and any published variant can be promoted regardless of which icon it shows.

Source: row.html.twig:9–13 · fe5c978

@adiati98 adiati98 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@promptless-for-oss please address the Vale warnings.

@promptless-for-oss

Copy link
Copy Markdown
Contributor Author

In reply to this discussion

On it — I'll run Vale on the changed files, fix the flagged warnings, and report back here once the PR is updated.

@promptless-for-oss

Copy link
Copy Markdown
Contributor Author

In reply to this discussion

Thanks! Vale reports 0 errors on the changed file. The findings on the lines this PR added are for the word "published" (the style guide prefers Active), which I'm fixing now — the rest are on pre-existing lines outside this PR's diff. I'll follow up when the update is pushed.

Replace 'published variant(s)' with 'Active variant(s)' on the manual
A/B winner-selection passage (lines 209, 211) to clear the four
Mautic.FeatureList Vale suggestions, matching the 'published' ->
'Active or Available' rule and the existing 'Active variants' phrasing
at line 120.
@promptless-for-oss

Copy link
Copy Markdown
Contributor Author

In reply to this discussion

Done — the A/B winner-selection passage now says "Active variant(s)" instead of "published variant(s)" (lines 209 and 211), which clears the four Mautic.FeatureList warnings the added text triggered — Mautic's Vale rules map "published" to "Active or Available", matching the existing "Active variants" wording elsewhere in this file. Vale now reports zero findings on the lines this PR adds. The remaining warnings in the file are all on pre-existing lines this PR doesn't touch, so I left them out to keep the change minimal — happy to open a separate cleanup if you'd like those addressed too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants