Google Ads Conversion Tracking for WordPress Forms – TagFlux
Changelog
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
Privacy: explicit opt-in (“Connect to TagFlux”) before any data leaves the site; activation makes no remote calls. “Disconnect site” button and uninstall cleanup