Ninja Forms conversions no longer count twice in dual mode, and Complianz banners now work out of the box: the visitor's consent choice reaches TagFlux even when Complianz has no Google service configured. Recommended update.<\/p>","1.2.5":"
Consent fixes: declining after having accepted now releases the click identifier everywhere, forms that appear after page load keep conversion deduplication, and custom consent banners that emit Google Consent Mode v2 are honoured automatically. Recommended update.<\/p>","1.2.4":"
Conversions are no longer lost when a visitor declines cookies: the click identifier is now also read from the submission request, which stores nothing on the visitor's device. On sites with a consent banner, the click identifier cookie now waits for advertising consent. Recommended update.<\/p>","1.2.3":"
Adds Divi 5 support and fixes conversion tracking on pages that embed a WPForms block \u2014 those pages were not loading the tracking script, so the browser-side conversion was lost. Recommended update.<\/p>","1.2.2":"
Google Ads accounts are now listed as a hierarchy, and "Link" is only offered for accounts that can actually record conversions \u2014 manager (MCC) and cancelled accounts explain why instead of failing after you click.<\/p>","1.2.1":"
Housekeeping release: uninstalling the plugin now clears all of its settings, so a reinstall really does start from scratch. No functional changes.<\/p>","1.2.0":"
Adds an optional "help me set it up" banner: leave your email and the TagFlux team helps you activate the plugin for free. Explicit opt-in, dismissible, no data sent unless you ask.<\/p>","1.1.0":"
Adds server-side conversion tracking (dual mode) with Consent Mode v2 and optional Enhanced Conversions \u2014 recovers conversions lost to blocked scripts, deduplicated via order ID. Also fixes the Spanish admin translations not loading. Recommended update.<\/p>","1.0.2":"
Clearer setup docs and an expanded FAQ for Google Ads conversion tracking. No functional changes.<\/p>","1.0.1":"
Improves error reporting when connecting to Google Ads. Recommended update.<\/p>"},"ratings":{"1":0,"2":0,"3":0,"4":0,"5":1},"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3567692,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3567692,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3567692,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3567692,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.0","1.0.1","1.0.2","1.1.0","1.2.0","1.2.1","1.2.2","1.2.3","1.2.4","1.2.5","1.2.6"],"block_files":[],"assets_screenshots":{"screenshot-1.jpg":{"filename":"screenshot-1.jpg","revision":3567702,"resolution":"1","location":"assets","locale":"","width":1219,"height":1264},"screenshot-2.jpg":{"filename":"screenshot-2.jpg","revision":3567702,"resolution":"2","location":"assets","locale":"","width":1100,"height":451},"screenshot-3.jpg":{"filename":"screenshot-3.jpg","revision":3567702,"resolution":"3","location":"assets","locale":"","width":1093,"height":1277}},"screenshots":{"1":"Dashboard with Google Ads metrics (clicks, CPC, conversions, cost) and breakdowns by form and campaign.","2":"Onboarding: the explicit \"Connect to TagFlux\" opt-in, disclosing exactly what data is sent before anything leaves your site.","3":"Settings: connect your Google Ads account, set the cookie consent mode, and disconnect the site whenever you want."}},"plugin_section":[],"plugin_tags":[1152,986,30680,985,219244],"plugin_category":[],"plugin_contributors":[266527],"plugin_business_model":[],"class_list":["post-323356","plugin","type-plugin","status-publish","hentry","plugin_tags-contact-form-7","plugin_tags-conversion-tracking","plugin_tags-form-tracking","plugin_tags-google-ads","plugin_tags-server-side-tracking","plugin_contributors-tagflux","plugin_committers-tagflux"],"banners":{"banner":"https:\/\/ps.w.org\/tagflux\/assets\/banner-772x250.png?rev=3567692","banner_2x":"https:\/\/ps.w.org\/tagflux\/assets\/banner-1544x500.png?rev=3567692","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/tagflux\/assets\/icon-128x128.png?rev=3567692","icon_2x":"https:\/\/ps.w.org\/tagflux\/assets\/icon-256x256.png?rev=3567692","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/tagflux\/assets\/screenshot-1.jpg?rev=3567702","caption":"Dashboard with Google Ads metrics (clicks, CPC, conversions, cost) and breakdowns by form and campaign."},{"src":"https:\/\/ps.w.org\/tagflux\/assets\/screenshot-2.jpg?rev=3567702","caption":"Onboarding: the explicit \"Connect to TagFlux\" opt-in, disclosing exactly what data is sent before anything leaves your site."},{"src":"https:\/\/ps.w.org\/tagflux\/assets\/screenshot-3.jpg?rev=3567702","caption":"Settings: connect your Google Ads account, set the cookie consent mode, and disconnect the site whenever you want."}],"raw_content":"\n
TagFlux is a server-side Google Ads conversion tracking plugin for WordPress forms. It auto-detects the forms already installed on your site, lets you choose which submissions count as conversions, and sends them to Google Ads through the TagFlux backend using the Google Click Identifier (gclid) \u2014 no code, no Google Tag Manager, no manual event setup.<\/p>\n\n
TagFlux uses server-side conversion tracking to send WordPress form submissions to Google Ads through the TagFlux backend.<\/p>\n\n
When a visitor arrives from a Google Ads click, TagFlux picks up the Google Click Identifier (gclid) from the ad URL and, where consent allows it, keeps it in a first-party cookie. If that visitor submits a tracked WordPress form, TagFlux sends the conversion event to Google Ads through the backend instead of relying only on browser-side tags \u2014 and if there is no cookie, it recovers the identifier from the submission request itself, so declining cookies costs you the visit-to-visit bridge but not the conversion.<\/p>\n\n
This is useful for lead generation websites that want more reliable Google Ads conversion tracking without maintaining a custom Google Tag Manager or gtag setup.<\/p>\n\n
Setting up Google Ads conversion tracking by hand usually means editing gtag snippets, configuring triggers in Google Tag Manager, and testing events one by one.<\/p>\n\n
TagFlux skips the manual tag setup. It detects your WordPress forms, captures the Google Click Identifier (gclid), and reports form submissions to Google Ads server-side through the TagFlux backend using the Google Ads API.<\/p>\n\n
That means no GTM container to maintain, no custom JavaScript, no manual event setup, and fewer moving parts between your WordPress forms and Google Ads conversion actions.<\/p>\n\n
TagFlux currently supports:<\/p>\n\n
If your Google Ads traffic lands on a WordPress page using one of these form plugins, TagFlux can help track those form submissions as Google Ads conversions.<\/p>\n\n
This plugin connects to two external services to provide conversion tracking. It does not work without them.<\/p>\n\n
1. TagFlux backend (api.tagflux.io)<\/strong><\/p>\n\n TagFlux relays conversion data to Google Ads through its own backend.<\/p>\n\n TagFlux terms: https:\/\/tagflux.io\/plugin-terms\/ \u2014 privacy policy: https:\/\/tagflux.io\/plugin-privacy-policy\/<\/p>\n\n 2. Google Ads \/ Google OAuth<\/strong><\/p>\n\n To connect your Google Ads account the plugin uses Google's OAuth flow, and the backend reads\/writes conversion data via the Google Ads API on your behalf.<\/p>\n\n Google terms: https:\/\/policies.google.com\/terms \u2014 privacy policy: https:\/\/policies.google.com\/privacy<\/p>\n\n\n Yes. TagFlux sends tracked WordPress form submissions to Google Ads through the TagFlux backend using the Google Ads API. It captures the Google Click Identifier (gclid) from Google Ads traffic and uses it to report the conversion server-side.<\/p><\/dd>\n No. TagFlux does not require you to set up a server-side Google Tag Manager container. It provides a simpler server-side tracking flow for WordPress form submissions and Google Ads conversions.<\/p><\/dd>\n No. TagFlux is designed to track Google Ads form conversions without Google Tag Manager, gtag snippets or custom JavaScript. It auto-detects supported WordPress forms and sends conversions to Google Ads through the backend.<\/p><\/dd>\n TagFlux currently supports Contact Form 7, WPForms, Elementor Pro Forms, Ninja Forms and Divi Forms.<\/p><\/dd>\n TagFlux tracks WordPress form submissions that come from Google Ads traffic. It captures the gclid from the ad click, keeps it in a first-party cookie where consent allows, and sends the conversion to Google Ads through the TagFlux backend when a tracked form is submitted. Without a cookie it falls back to the identifier carried by the submission request.<\/p><\/dd>\n Yes, you need an active Google Ads account to track conversions.<\/p><\/dd>\n With Google Tag Manager or gtag you build triggers and tags by hand and maintain them over time. TagFlux auto-detects your forms, maps each one to a conversion action, and sends submissions to Google Ads automatically \u2014 no container, no code.<\/p><\/dd>\n Yes. You can choose multiple forms to track, and every submission of each tracked form is reported to Google Ads.<\/p><\/dd>\n Not yet. TagFlux currently tracks form submissions (contact, lead and quote forms). WooCommerce checkout and purchase tracking is on the roadmap, not in this version.<\/p><\/dd>\n Any theme. Form detection currently covers Contact Form 7, WPForms, Elementor Pro, Ninja Forms and Divi forms \u2014 both the Divi 4 builder and Divi 5 \u2014 regardless of the theme you use.<\/p><\/dd>\n Yes. On a site where TagFlux detects a consent banner, the tracking cookie is not written until the visitor grants advertising consent, and declining removes it; the cookie is also tagged as In dual mode each tracked submission is reported twice: by the classic gtag script in the browser and by your server through the TagFlux backend. Google Ads deduplicates the two with a shared order ID, so conversions are never double-counted \u2014 but they are recovered when an ad blocker or strict browser blocks the gtag script. You can turn it off in Settings at any time.<\/p><\/dd>\n No. Activation only creates local options; no request is made to any external service. Your site is registered with api.tagflux.io only after you explicitly click \"Connect to TagFlux\" on the settings screen, where the data to be sent (your site URL and name) and the links to our Terms and Privacy Policy are shown beforehand.<\/p><\/dd>\n Click \"Disconnect site\" on the TagFlux settings screen to clear the local registration and the Google Ads connection stored in WordPress; you can connect again afterwards. Deleting the plugin removes all TagFlux options from your database (via \n
https:\/\/api.tagflux.io\/api\/auth\/register<\/code> to register the site and obtain an API key. No personal data is sent at this step.<\/li>\nhttps:\/\/api.tagflux.io\/api\/support\/help-requests<\/code> so the TagFlux team can contact you. Dismissing the banner sends nothing and it will not be shown again.<\/li>\ngclid<\/code>\/wbraid<\/code>\/gbraid<\/code>, taken from the submission request, from a hidden form field, or from a first-party cookie tagged as marketing<\/code> \u2014 which on a site with a consent banner is only written once advertising consent is granted), the visitor's Consent Mode v2 state, an order ID used for deduplication, the form\/campaign identifiers and the conversion event to https:\/\/api.tagflux.io<\/code>. The contents of the form fields (names, emails, messages) are not<\/strong> sent \u2014 with one exception: if you enable the optional Enhanced Conversions setting and<\/strong> the visitor has granted ad consent, the email and\/or phone number from the submitted form are sent as SHA-256 hashes (never in plain text).<\/li>\n<\/ul>\n\n\n
tagflux<\/code> folder to \/wp-content\/plugins\/<\/code>, or install it from the WordPress plugin repository.<\/li>\n\n
Does TagFlux support server-side tracking?<\/h3><\/dt>\n
Is this the same as Google Tag Manager server-side tracking?<\/h3><\/dt>\n
Do I still need Google Tag Manager?<\/h3><\/dt>\n
Which WordPress form plugins does TagFlux support?<\/h3><\/dt>\n
What does TagFlux track?<\/h3><\/dt>\n
Do I need a Google Ads account?<\/h3><\/dt>\n
How is it different from tracking Google Ads conversions with GTM or gtag?<\/h3><\/dt>\n
Can I track more than one conversion action?<\/h3><\/dt>\n
Does it work with WooCommerce?<\/h3><\/dt>\n
Which page builders and themes are supported?<\/h3><\/dt>\n
Is it GDPR compliant?<\/h3><\/dt>\n
marketing<\/code> so consent managers can control it themselves. Server-side conversions carry the visitor's real Consent Mode v2 state (read from your consent banner), and Enhanced Conversions data is only sent when the visitor has granted ad consent. See the \"External services\" section below for exactly what data is sent and where.<\/p><\/dd>\nWhat is server-side (dual) conversion tracking?<\/h3><\/dt>\n
Does the plugin send any data when I activate it?<\/h3><\/dt>\n
How do I disconnect or remove my data?<\/h3><\/dt>\n
uninstall.php<\/code>).<\/p><\/dd>\n\n<\/dl>\n\n\n1.2.6<\/h4>\n\n
\n
1.2.5<\/h4>\n\n
\n
ad_storage<\/code> governs the cookie, the visitor's choice survives navigation between pages, and region-scoped consent defaults are no longer misread as global.<\/li>\ntagflux_consent_managed<\/code> filter so custom banners can declare themselves in code, and a settings notice when the detected consent manager does not emit Consent Mode v2 \u2014 on those sites the attribution cookie waits for a signal that never arrives, which was working as designed but silently.<\/li>\n<\/ul>\n\n1.2.4<\/h4>\n\n
\n
mailto:<\/code>, tel:<\/code> and anchors are left alone, and nothing is added once the cookie is in place.<\/li>\nwww<\/code> no longer discards its own referrer and loses the conversion.<\/li>\n1.2.3<\/h4>\n\n
\n
1.2.2<\/h4>\n\n
\n
1.2.1<\/h4>\n\n
\n
1.2.0<\/h4>\n\n
\n
1.1.0<\/h4>\n\n
\n
gclid<\/code>\/wbraid<\/code>\/gbraid<\/code> in a cookie and a hidden form field (cookieless fallback).<\/li>\n1.0.2<\/h4>\n\n
\n
1.0.1<\/h4>\n\n
\n
1.0.0<\/h4>\n\n
\n