My client does some online trainings through Zoom. People sign up on client's website for access to the sessions. When the sessions are over, he wants to send a certificate to them.

These people are added to a list automatically in FluentCRM when they sign up.

I would love to create an automation that sends them a certificate by a certain date with their name on it.

The way I have handled this before is through a self-serve form with Gravity Forms and people could download certificate that was generated with their information.

Trying to avoid the self-serve route so if you have any experience with this, I would love to hear your suggested solution. Thanks.

Bricks Builder: Subscribe form with name, email. Custom fields: utmsource, utm__campaign, utmmedium, utm__content. Slugs match exactly to FluentCRM custom fields.

Webhook set up fine. When someone subscribes, it fills the name and email, but none of the custom fields. I'm having this same issue with YouForm to FluentCRM also. Is there a secret trick to this I'm missing?

I wanted to see how the Vue 3 rewrite in 3.0 handles high-concurrency database tasks on a hardened infrastructure. Most reviews look at the features; I looked at the SQL table namespaces and response times. Here’s the breakdown.

Hi team!

I think I found a tracking issue in FluentCRM related to campaign template type.

I compared two recent campaigns sent to almost the same audience:

• Campaign 1

  • design_template: raw_classic
  • sent: 596
  • opens: 223
  • clicks: 7

• Campaign 2

  • design_template: raw_html
  • sent: 594
  • opens: 7
  • clicks: 7
  • CTOR: 100%

This looks suspicious because the second campaign clearly generated clicks, but opens were only counted for the same users who clicked.

Important context:

• SPF / DKIM / DMARC look correct
• delivery does not appear to be the problem
• click tracking works
• the anomaly appears only in the campaign using raw_html
• previous campaigns using raw_classic tracked opens normally

Hypothesis:
The open tracking pixel is missing, not rendered correctly, or not being registered properly in raw_html campaigns.

Could you please confirm:

1. whether this is a known issue with raw_html
2. whether raw_html handles open tracking differently from raw_classic
3. whether there is any recommended workaround

Happy to share more campaign details if needed!

Is there any chance we can get a warmup domain feature? For example, if my domain is sending only 50 emails a day coming from automations, when sending a campaign I would want to start i.e. by sending double that amount. So I would start the campaign by sending out 100 emails and then slowly increase the amount of emails being sent each day.

(Screenshot is from another email delivery software I'm using that has domain warmup)

Hi everyone,

Posting this because it's going to land on a lot of EU inboxes in the next few weeks and I'd rather we discuss it here before panic sets in.

On April 17, 2026 the Italian Data Protection Authority published a binding opinion on email tracking pixels. The short version: the open-tracking pixel that FluentCRM (and basically every other email platform — Mailchimp, Brevo, ActiveCampaign, HubSpot, Klaviyo, Substack, all of them) injects by default into campaigns is now classified under Art. 122 of the Italian Privacy Code, which is the local implementation of the EU ePrivacy Directive. In practice this means the pixel requires prior, specific, informed, freely given consent — the same standard that already applies to non-essential cookies.

A generic newsletter opt-in is no longer enough. The user must either explicitly consent to tracking, or be given a granular way to opt out of tracking while remaining subscribed.

Three things worth knowing:

1. This is not only an Italian problem. The legal foundation is the EU ePrivacy Directive, which applies everywhere in the Union. The Italian ruling is the first explicit interpretation on pixels specifically, but other national authorities (CNIL in France, the German DPAs, the Irish DPC, etc.) tend to align quickly on this kind of interpretation. If you send newsletters to EU recipients from anywhere in the world, this concerns you.

2. There's a grace period, then real sanctions. Italian businesses have six months from publication in the Official Gazette to comply. After that, fines fall under GDPR Art. 83 — up to €20M or 4% of global turnover. This is not a "€500 slap on the wrist" regime.

3. The fix is technical, not just legal. You need (a) an updated privacy policy that explicitly names tracking pixels and the data they collect, (b) a mechanism for subscribers to opt out of tracking without unsubscribing from the newsletter, (c) the ability to actually suppress the pixel for non-consenting contacts.

On point (c), FluentCRM right now doesn't expose a per-subscriber opt-out flow or a clean filter hook to conditionally suppress the pixel at render time — I've opened a feature request ticket with the Fluent team asking for both admin-level and subscriber-level tracking controls, plus developer hooks as a minimum viable step. If this matters to your business, adding a +1 or your use case to that ticket helps it move up the roadmap.

In the meantime, a few things I'd suggest to fellow EU users:

• Audit your current opt-in flow. Does your privacy policy mention tracking pixels explicitly? If not, it needs to.
• Don't panic-send a re-consent email tomorrow. You have time. Plan it: decide who needs what (fresh opt-in vs tracking-specific re-consent vs nothing because the existing policy already covers it).
• If you rely heavily on open rates as a KPI, start now on an alternative engagement model (replies, clicks on meaningful links, conversions) — a meaningful chunk of your audience will end up in a non-tracked segment either way.

Happy to discuss specific implementation ideas if anyone has them — I'm a developer running an agency managing EU/Swiss clients, so I'm looking at this from both the compliance and the "how do we actually build it" side.

Source https://www.garanteprivacy.it/home/docweb/-/docweb-display/docweb/10241943 https://www.garanteprivacy.it/web/guest/home/docweb/-/docweb-display/docweb/10241977

Another step closer to the stable 3.0 release.

Since RC-1, we've been working through the feedback and issues you reported. This one brings a couple of nice new additions along with a solid round of fixes and polish.

What's new in RC-2

• Frontend Portal: You can now give your contacts a clean frontend view to manage their own profile and preferences. This has been a long-requested feature, and we're excited to finally ship it. You can enable that from FluentCRM -> Addons
• New Bulk Selection UX/UI: Selecting contacts and emails, and running bulk actions on them, feels a lot better now.
• Floating action bar for bulk actions in Contacts and Emails, so your actions follow you as you scroll.
• Contact pagination up to 600 per page: If you manage large lists, this one makes a real difference.

Fixes

• Synced Pattern issue
• Pattern Edit issue
• Email Global Style issue
• RTL issues
• Automation Benchmark issues
• More UI fixes across the app

Improvements

• Better bounce handling
• Other small improvements and bug fixes throughout

How to install the latest RC

• Download & Install Fluent Toolkit addon
• Activate the plugin, then go to Fluent Toolkit and install/update FluentCRM Beta and FluentCRM Pro Beta
• That’s it.

How you can help

If you can, please install RC-2 and run it against your real workflows. The more edge cases we catch now, the cleaner the stable 3.0 release will be.

Drop bugs, feedback, or general thoughts right here in this space. We read everything.

I'm using FluentCommunity and have three different memberships: teenagers, adults and professionals. I have built a custom dashboard for all of the memberships. After login, I would like to redirect people to their membership dashboard. So if you have tag teenager, you are redirected to Teenager Membership Dashboard, if you have tag Adult, you are redirected to Adult Membership Dashboard etc.

This site is using FluentCRM, FluentAuth, FluentForms, FluentCommunity and FluentCart. Is this possible with this stack?

Are automation templates available for FluentCRM? In watching loads tutorial videos where automation flows are mentioned with quick screenshots. Looks great, but then I'm finding myself looking at blank page, with all the options, and not sure what to build. 'you don't know, what you dont know' type thing.

I've built a couple flows, but I'm sure I'm only just scratching the surface. Not least because I've got nearly the full Fluent suit.

A library of automations around use case scenarios would be great.

Basics, course owners, community builders, etc.

Even better, an AI integration to plug in what tools you use, what your trying to achieve.. and vola! A list of recommend automation templates.

I'm a one man band, so im very keen to do as much as I can using automation processes. 👍

Our customer uses FluentCRM and FluentSupport together to manage WooCommerce orders. They handle order customizations through FluentSupport — when a new order comes in, a support ticket is automatically created.

Problem:
There is currently no way to automatically update the WooCommerce order status when the associated FluentSupport ticket is closed. The workflow is one-directional: an order can trigger a ticket, but closing the ticket cannot update the order back.

Requested Feature:
Add an automation action (or trigger-based option) in FluentCRM that allows updating a WooCommerce order status when a FluentSupport ticket status changes — specifically when a ticket is closed or resolved.

Example Workflow:

1. New WooCommerce order → FluentSupport ticket is created automatically
2. Team works on the order customization via the ticket
3. Ticket is closed → WooCommerce order status automatically updates (e.g., to “Printing” or a custom status)

This would close the loop between FluentSupport and WooCommerce, making the integration significantly more useful for teams that manage order fulfillment through support tickets.

Shahjahan Jewel