A/B test image styles for new subscribers
New FluentCRM contacts take turns between two welcome card designs: a Counter and a Branch alternate them, Image Builder renders the card for each variant and the contact is emailed a link to it.
FluentCRM
Counter
Branch
Image Builder
Email7 steps Setup ~12 min Used on 2.6k sites Marketing Free to import
What this workflow does
When you are choosing between two welcome images, the fair way to compare them is to send each to half of your new contacts. This workflow does the splitting for you, alternating every new FluentCRM contact between variant A and variant B, so you can look at the responses to each design.
The FluentCRM New Contact Created trigger starts a run for each new contact. FlowMattic's Counter then adds 1 to a stored number and resets it once it reaches 1, so its result goes 1, 0, 1, 0 across runs. A Branch checks whether that result exactly matches 1. Contacts on a 1 take the Yes path, variant A, and the rest take the No path, variant B. The paths don't rejoin, so each contact gets one card.
On each path, Image Builder renders a PNG from a saved template, saves it to the Media Library under a name with the variant letter and contact ID, and FlowMattic's Email step sends the contact a short welcome with the card's link. The two emails have different subjects and wording, so change them if you only want to test the image.
Set up both templates before you turn this on. The variant A step points at template ID 8, a placeholder, and the variant B step has no template at all. Neither maps contact data into its tokens. Rendering also needs your Cloudflare Browser Rendering details in FlowMattic's settings.
Illustrated card versus photo card
A travel newsletter sends half its new subscribers an illustrated welcome card and half a photo card, then compares the replies to each.
Testing a name on the image
A shop checks whether a card that shows the subscriber's first name draws more clicks than one with only the brand logo.
Picking a design for the main welcome series
A coach runs both card styles for a few weeks, then keeps the one subscribers mention most and puts it in the regular onboarding emails.
How this workflow runs
What happens at each step once the workflow is on, and what you need before you import it.
FluentCRM New Contact CreatedStarts a run whenever a new contact is created in FluentCRM. The contact's ID, email, first name and other details pass on to the Counter, Branch, image and email steps.
- Counter Incremental Counter
Adds 1 to a number FlowMattic stores for this workflow, starting from 0, and resets it to 0 once it has reached 1. The result, final_value, alternates between 1 and 0 from one run to the next.
- Branch Branch
Checks whether the Counter's final_value exactly matches 1. Yes sends the contact to variant A, No sends them to variant B. There is no Join, so each run follows one path to its end.
- Image Builder Generate Image from Template
Variant A: renders a PNG from Image Builder template ID 8 and saves it as welcome-a plus the contact ID. Replace the placeholder with your first design and map contact fields into its tokens.
Email Send EmailVariant A: emails the contact a welcome with a link to the variant A card. Edit the subject and text to match variant B if you want the image to be the only difference.
- Image Builder Generate Image from Template
Variant B: renders a PNG saved as welcome-b plus the contact ID. This step ships without a template, so pick your second design before turning the workflow on, and map contact fields into it.
- Email Send Email
Variant B: emails the contact a welcome that links to the variant B card, with its own subject and wording. Change both if you want identical text on the two paths.
What you need
- FlowMatticCore
- FluentCRM PluginPlugin
After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.
Make it yours
Changes worth making after you import it.
- Add FluentCRM's Add Tags to Contact action at the end of each path, tagging contacts Welcome A or Welcome B, so you can tell later which card each person received.
- Put a Filter between the New Contact Created trigger and the Counter that continues only for subscribed contacts. The Email steps don't check FluentCRM status, and filtered contacts won't affect the alternation.
- Give both Email steps the same subject and body before you start, so the card design is the only thing that differs between the two groups.
Questions about this workflow
How does this workflow split new FluentCRM contacts between the two cards?
By alternating. The Counter's result switches between 1 and 0 on each run, and the Branch sends a 1 to variant A and a 0 to variant B. Over many contacts that gives two groups of about the same size.
Does the workflow measure which welcome card performs better?
No. It only splits contacts and sends the cards. Tag each path's contacts in FluentCRM, or log them to a sheet, and compare replies or later activity yourself.
What do I need to set before the variant B card can render?
A second saved Image Builder template, selected in the variant B step, which ships with none. Also replace template ID 8 in the variant A step, and add your Cloudflare Browser Rendering details in FlowMattic's settings.
Is the welcome card personalised for each FluentCRM contact?
Not as imported. Only the file names use the contact ID. Map the contact's first name or other fields into each template's tokens if the card should show them.
More Marketing Automation workflows
Other ready-to-import templates from the same category.
Import this workflow into your WordPress site
Download the JSON, import it from the Workflows screen and connect your accounts. Every run stays on your server, with no per-task fees.
30-day money-back guarantee Unlimited workflows and runs Self-hosted