Google Ads Conversion Tracking for WordPress Forms – TagFlux

Changelog

1.2.5

• Fix: declining consent after having accepted it now releases the click identifier everywhere — the value already painted in the hidden field, and carried by links clicked afterwards, stops travelling; not just the cookie. A click identifier arriving in the URL of the current request is kept, as it reads nothing from the visitor’s device.
• Fix: forms that appear after the page loads (popups, modals, AJAX tabs) now receive the click identifier and the shared order ID at submit time, so dual-mode conversions keep deduplicating instead of counting the same lead twice.
• New: TagFlux now obeys the Google Consent Mode v2 signal even when the consent banner is not one of the recognised plugins — a custom banner that emits Consent Mode is honoured automatically. ad_storage governs the cookie, the visitor’s choice survives navigation between pages, and region-scoped consent defaults are no longer misread as global.
• New: tagflux_consent_managed filter so custom banners can declare themselves in code, and a settings notice when the detected consent manager does not emit Consent Mode v2 — on those sites the attribution cookie waits for a signal that never arrives, which was working as designed but silently.

1.2.4

• New: conversions are no longer lost when a visitor declines cookies. The click identifier is now also read from the submission request itself — the query string or the referring URL — which reads nothing from, and stores nothing on, the visitor’s device. Measured against real submissions: WPForms posts to the page itself, Contact Form 7 and Ninja Forms only carry the referrer.
• New: internal links carry the click identifier while no cookie is available, so the attribution survives a visit that lands on one page and submits on another. Links to other domains, mailto:, tel: and anchors are left alone, and nothing is added once the cookie is in place.
• Privacy: on sites with a consent banner, the click identifier cookie now waits for advertising consent, and is written as soon as consent is granted — including later in the same visit. Declining removes it and stops it being read. Sites without a banner are unaffected. Visitors who never accept keep their attribution through the URL, the referrer and the decorated links; only the bridge between separate visits is lost.
• Fix: the click identifier is validated and length-limited whatever its source, so a crafted link or a tampered form field cannot inject arbitrary content into the conversion upload.
• Fix: a site served both with and without www no longer discards its own referrer and loses the conversion.
• Fix: links added to the page after it loads are now handled too, and relative links stay relative instead of being frozen to one scheme and host.

1.2.3

• New: Divi 5 support. Divi 5 builds its contact forms as blocks instead of shortcodes, so on a Divi 5 site no form was detected at all — nothing to select, nothing to track. Divi 4 and Divi 5 forms are now detected side by side, which is what a site migrated to Divi 5 actually looks like.
• Fix: pages embedding a WPForms block did not load the tracking script, so the browser-side conversion was never fired. With server-side tracking enabled the conversion still reached Google Ads; without it, the submission was lost entirely.
• Fix: the “used on these pages” list of a form no longer misses block embeds, and no longer confuses one form with another whose ID starts with the same digits (form 2 was matched by form 23).
• Fix: Divi form identifiers are now resolved on the server in document order, so a page holding more than one Divi form reports the right one.
• Internal: every form-detection pattern now lives in a single place and is validated every night against the real form builders, including Divi 4 and Divi 5.

1.2.2

• New: the Google Ads account list is now shown as a hierarchy. Manager accounts (MCC) head their own group and the client accounts underneath are listed indented, so it is clear where conversions are actually recorded.
• Fix: the “Link” button is only offered for accounts that can record conversions. Manager accounts and cancelled or suspended accounts now explain why they cannot be linked, instead of offering a button that fails afterwards.
• Fix: auto-linking now only considers linkable accounts. A site whose only visible account was a manager could end up linked to it, which silently records nothing.
• i18n: new strings translated (es_ES).

1.2.1

• Fix: uninstalling the plugin now removes every setting it created. Four options survived deletion (server-side tracking mode, Enhanced Conversions, and the setup-help opt-in state and email), so reinstalling inherited the old configuration instead of starting clean.
• i18n: plugin headers are now translatable and the Spanish (es_ES) catalogue has been updated.

1.2.0

• New: optional setup-help banner for administrators while the plugin is not connected (Dashboard, Plugins and TagFlux screens). Leave your email and the TagFlux team contacts you to set everything up, free of charge.
• Privacy: the banner is strictly opt-in — nothing is sent unless you explicitly submit it; dismissing it is permanent and sends nothing. Disclosure added to the External services section.
• i18n: banner fully translated (es_ES).

1.1.0

• New: server-side conversion tracking (dual mode). Submissions are also reported through the TagFlux backend using the Google Click Identifier, recovering conversions lost when the gtag script is blocked. Google Ads deduplicates both paths via a shared order ID.
• New: first-party capture of gclid/wbraid/gbraid in a cookie and a hidden form field (cookieless fallback).
• New: Consent Mode v2 support — reads the visitor’s real consent state from the consent banner (dataLayer) and forwards it with each server-side conversion.
• New: optional Enhanced Conversions — email/phone are SHA-256-hashed before leaving the site, and only sent if you enable the setting and the visitor granted ad consent.
• New: “Server-side conversions” dashboard card with upload status (sent/failed/pending) and failure reasons, including a notice when the Enhanced Conversions terms are pending acceptance in Google Ads.
• New: non-blocking configuration warnings in Settings when server-side tracking is misconfigured (no Google account connected, no forms selected, or Enhanced Conversions without a consent manager).
• Fix: the admin now displays in Spanish on Spanish sites — the plugin never loaded its textdomain; all strings extracted and translated (es_ES).

1.0.2

• Docs: clearer setup guide and an expanded FAQ for Google Ads conversion tracking with Contact Form 7, WPForms, Elementor, Ninja Forms and Divi.
• No functional changes.

1.0.1

• Fix: Google connection errors (e.g. missing permissions) are now shown in the admin panel instead of failing silently.

1.0.0

• Initial release on WordPress.org
• Google Ads OAuth
• Form detection: WPForms, Divi 4, Contact Form 7, Elementor Pro, Ninja Forms
• Metrics dashboard (clicks, CPC, conversions, cost)
• Breakdowns by form, campaign and landing page
• Site ownership verification via REST API
• Privacy: explicit opt-in (“Connect to TagFlux”) before any data leaves the site; activation makes no remote calls. “Disconnect site” button and uninstall cleanup
• Privacy: external-services disclosure + suggested privacy policy content
• Upgrade routine (version-gated migrations via plugins_loaded)
• Available in English and Spanish