Qaiyo UTM Tracker for Fluent Forms

Descripción

You run Meta and Google Ads, the enquiries arrive through Fluent Forms, and the question is always the same: which source and which campaign brought this lead? Qaiyo UTM Tracker for Fluent Forms answers it on every entry, with no reporting tool in between.

Click one button to add the tracking fields to a form. From then on the plugin remembers where the visitor arrived from — the campaign parameters of the ad, or the search engine, social network or website that sent them — writes it into those fields when the form is sent, and Fluent Forms stores it with the entry: visible on the Entries screen, in exports and in Fluent Forms’ own reports.

What makes it different

• The values live in the Fluent Forms entry itself. No extra database table and no second dashboard: source, campaign and click ID are ordinary entry fields, so Fluent Forms’ own search, exports, reports and (with Fluent Forms Pro) Advanced Filter work on them, and they are kept, exported and erased with the entry.
• One click per form. The settings screen lists your forms and the tracking fields each one still needs. «Add missing fields» appends them to the form as Hidden Fields through Fluent Forms’ own save, the same way the editor does; nothing else in the form changes.
• Every lead gets a source, not only ad clicks. Without campaign parameters the source comes from the site that sent the visitor: search engines as «organic» (google, bing, duckduckgo…), social networks as «social» (facebook, instagram, linkedin…), any other site by its domain as «referral», and a typed-in address as «(direct)» / «(none)». Ad data always wins: an organic or direct visit never replaces the parameters or click ID of an ad. Only the referring domain is used, never the full address.
• The landing page is recorded too, without its query string, so you see which page the lead first arrived on.
• Meta (Facebook and Instagram) Ads work out of the box. Meta appends the UTM parameters you set on the ad — source, medium, campaign, content, term — to the landing URL, and the plugin stores them with the entry as they are, for example facebook / cpc / your campaign name / the ad ID. Nothing else to configure.
• Survives the way people really convert. Visitors rarely send the form on the page they land on. UTM parameters are kept for the browser session; the Google Ads click ID is kept in a first-party cookie (90 days by default, adjustable), because it is only in the address of the very first page and people often come back days later.
• Google Ads without tracking templates. Google Ads auto-tagging adds only a click ID (gclid) to its links, no UTM parameters, so most trackers record these leads with an empty source. This plugin records them as source «google», medium «cpc» — on the server, just before Fluent Forms stores the entry, so it works even when the visitor’s browser blocks scripts. A source the ad link does set always wins.
• Fixes your older entries too. Entries saved before the plugin that carry a click ID but no source show «google» on the Entries screen straight away. A one-click, batched tool writes it into those entries for exports and reports as well, the way Fluent Forms itself stores an edited entry, and never overwrites an entry that already has a source or that someone edits in the meantime.
• Last touch wins, campaigns never mix. A new campaign visit replaces the values of the previous one, so a Google Ads click after a Facebook visit is not recorded as Facebook, and a new source never travels with an old utm_content.
• Consent-aware. With the WP Consent API plugin (used by Complianz, CookieYes, Cookiebot and others), nothing is stored until the visitor allows marketing cookies, and stored values are removed when consent is withdrawn. Suggested privacy-policy text is added to the WordPress Policy Guide.
• Works with the free Fluent Forms. Hidden fields and entries are part of Fluent Forms itself; Fluent Forms Pro is not required.

Tracked fields

utm_source, utm_medium, utm_campaign, utm_content, utm_term, gclid and landing_page. A field that is not on a form is simply not recorded, so you can leave out the ones you do not need.

Built to stay out of the way

The capture script is a few kilobytes, loads deferred in the footer, has no dependencies and does not watch the page: it fills the fields when the page loads, when Fluent Forms opens a form (popups, AJAX-loaded forms) and at the moment the form is sent. The plugin does not touch Fluent Forms’ Entries screen markup, so nothing shifts or breaks when Fluent Forms updates its interface.

Privacy

The plugin does not connect to any external service and sends nothing anywhere. The values stay in the visitor’s browser (sessionStorage and the qfut_gclid cookie) until a form is sent; after that they are part of the Fluent Forms entry and are kept, exported and erased with it. Of a referring page only its domain is used. Recording organic, social, referral and direct visits can be switched off in the settings.

Translations

The interface is translation-ready, and translations are delivered through translate.wordpress.org. The author prepares Hungarian, German, French, Spanish, Japanese, Portuguese (Portugal), Italian, Russian, Turkish and Polish.

Trademarks

Fluent Forms, Google Ads, Meta, Facebook and Instagram are trademarks of their respective owners. This plugin is an independent add-on and is not affiliated with, endorsed by or sponsored by them.