Building a service booking site for a notary business in New York (WordPress + Elementor Pro + Fluent Forms Pro + Stripe). The forms have conditional pricing logic — deposit vs. full payment options with add-on fields that conditionally show/hide based on selections.
Client now wants to add tax collection to full-payment transactions only. The problem: Fluent Forms passes a fixed calculated amount directly to Stripe Elements.
What's the best way to calculate and display a tax amount to the user before they hit the Stripe payment step in Fluent Forms?
rich text on bricks builder not show up
Hey team! Quick question/feature request
I noticed FluentCart has native UTM tracking built in, which is great. But I'm surprised this isn't available natively in Fluent Forms yet. ( as core, not as custom FCRM integrations with custom fields by get paragram).
Right now, to track where a lead originally came from (Google, YouTube, newsletter, etc.), we need to set up hidden fields with GET parameters or use third-party plugins. It works, but it's manual and fragile.
Having native UTM tracking in Fluent Forms (utm_source, utm_medium, utm_campaign) captured automatically and passed through to FluentCRM would be a game changer for reporting. Especially for those of us running content funnels where knowing which video or email generated a lead is critical.
Since the logic already exists in FluentCart, would it be possible to bring it over to Forms? Feels like a natural fit for the ecosystem.
Anyone else missing this?
-
cc: Nishat Shahriyar
WP Ninja Team: Can you all just hide the credit card field when a 100% coupon is entered for a product? Gravity Forms does this well, so I know FluentForms could do this. This is the main issue I have with FluentForms right now. You all gave me a workaround to take the user to stripe for payment, but the hiding of the credit card field should be inline on the form and I don't want the user to go to stripe to complete their transaction. It was told to me that it would be sent as an "improvement request", but this is a logical usability issue to me. Please... in the next update...please.
Hey Nishat Shahriyar and team.
Quick feature request: it seems there's no way to add a Custom HTML field below the submit button in Conversational Form mode:
it's only available in regular forms.
This is relevant for GDPR compliance: in the EU, we need to display a collapsible "basic data protection information" notice (using a \ toggle) right below the form submission area. We've implemented this in all our regular forms using Custom HTML, but conversational forms don't support it.
Would it be possible to allow Custom HTML fields (or at least a designated "legal notice" slot) in Conversational Forms? Thanks!
It has come to my attention that over the past few months, each time a new version is rolled out, the download function is affected. This results in a critical error that prevents me from downloading the forms as PDF files. While this issue may seem minor on your end, it creates significant legal implications for me when I am unable to download completed forms and submit them to my clients by the required deadlines.
I respectfully request that this issue be resolved as soon as possible and that measures be taken to prevent it from recurring in future updates.
P.S. I have opened a ticket already!
Is it possible to define a slug for a fluentforms landing page?
Not sure where to get help with this issue, I have a form with 9 sections with Page Breaks between each one. I'm not sure how to troubleshoot the issue to fix this.
Is there a limit to how many sections you can have in a form?
Here's the form: https://sailsandgrace.com/?ff_landing=5
Hello super team,
Is there any chances that soon Fluent cart will become on of the official payment gateway for Fluent Form. It would be such a great feature, like in fluent booking.
WIth FluentForms, we already can create a custom double opt-in (DOI) email per form. But we cannot change the sender. It always uses the sender that is configured in FluentSMTP. It would be great to add a field for configuring the sender, too.