TagFlux -- WordPress 插件

开发者	tagflux
更新时间	2026年10月18日 00:24
PHP版本:	7.4 及以上
WordPress版本:	7.1
版权:	GPLv2 or later
版权网址:	版权信息

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) — no code, no Google Tag Manager, no manual event setup. Features

Server-side Google Ads conversion tracking for WordPress forms
WooCommerce purchase tracking with the order value and currency — classic and block checkout
Purchases are uploaded from your server when the payment completes, so conversions are recorded even if the buyer never sees the thank-you page
Conversion submission through the TagFlux backend using the Google Ads API
Google Ads connection via OAuth
GCLID capture and first-party cookie storage
Auto-detection of supported WordPress forms
Support for Contact Form 7, WPForms, Elementor Pro Forms, Ninja Forms and Divi Forms
Choose which forms to track from the WordPress admin
Track form submissions from Google Ads traffic
Dashboard with clicks, CPC, conversions and total cost
Breakdowns by form, campaign and landing page
No Google Tag Manager setup required
No custom JavaScript required
Built for Google Ads lead generation campaigns
Consent Mode v2 aware: reads the visitor's real consent state from your consent banner and forwards it with each server-side conversion
Optional Enhanced Conversions: email/phone sent as SHA-256 hashes, only if you enable it and the visitor granted consent
Compatible with consent managers (GDPR-friendly)
Available in English and Spanish

Server-side Google Ads conversion tracking for WordPress TagFlux uses server-side conversion tracking to send WordPress form submissions to Google Ads through the TagFlux backend. 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 — 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. 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. Why TagFlux instead of Google Tag Manager? 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. 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. 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. Supported form plugins TagFlux currently supports:

Contact Form 7
WPForms
Elementor Pro Forms
Ninja Forms
Divi Forms

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. How it works

Install and activate the plugin — activation contacts no external service.
Click "Connect to TagFlux" and connect your Google Ads account via OAuth.
Select which forms to track. From then on, every submission is sent to Google Ads as a conversion automatically.

1.4.5

Fix: on Divi sites with "defer jQuery" enabled (Divi's default since 4.10.5), Divi places a temporary jQuery placeholder in the page header and loads the real jQuery later. When nothing else in the header needed jQuery, the TagFlux tracking script ran before the real one arrived and stopped with an error. Divi contact forms then recorded no conversions at all, and Ninja Forms and Elementor Pro lost their browser-side conversion (the server-side upload kept working). TagFlux now waits for the real jQuery.

1.4.4

Change: server-side tracking is now on by default. Connecting Google Ads turns on Dual mode, so each conversion is also sent from your server as well as from the browser, and Google deduplicates the two by order id. Conversions are no longer lost when the visitor rejects cookies, uses an ad blocker, or the consent plugin never releases the Google tag. If you had set server-side tracking to Off yourself, reconnecting keeps it off.
When a visitor rejects cookies, only the Google Ads click identifier is sent, flagged as consent denied: no email, phone or other personal data. The settings page now says so.

1.4.3

New: if the connection between TagFlux and your Google Ads account is lost, a notice on every admin screen tells you and links straight to reconnecting. Until now the plugin only refreshed that status right after connecting, so it could keep showing "connected" while no metrics loaded and no server-side conversion could be uploaded. The check runs at most twice a day, and a network error or a TagFlux server outage never disconnects you.
New: a settings notice when your consent manager (Moove GDPR, Cookie Notice, Real Cookie Banner or EU Cookie Law) has no way to release the Google tag after the visitor accepts cookies, so browser-side conversions are never recorded. Server-side tracking still delivers them, and the notice points you there.

1.4.2

Fix: on sites with a cookie consent plugin, the Google tag and the TagFlux tracking script were blocked with a generic attribute that none of the supported consent managers knows how to release. They stayed blocked even after the visitor accepted cookies, so browser-side conversions were never sent — Google Ads ends up flagging the conversion action as "Misconfigured". Each consent manager now gets its own blocking convention: CookieYes (including legacy mode), Cookiebot, Complianz, iubenda and WPConsent release the scripts as soon as the visitor accepts advertising cookies, and keep them blocked otherwise.
Fix: a script tag carrying type="text/javascript" (themes without HTML5 script support) could run before consent, because browsers honour the first type attribute. TagFlux now removes it before blocking the script.
Fix: forms placed inside a Salient Global Section ([nectar_global_section]) are now detected, so the page loads the tracking script and the conversion is recorded.

1.4.1

New: conversion value in the dashboard. WooCommerce purchases have reported their order value to Google Ads since 1.3.0, but TagFlux never asked Google for it back, so the dashboard counted sales without saying what they were worth. There is now a "Conversion Value" metric for the period, plus a value column in the breakdowns by form and by campaign.
New: the server-side conversions card shows the value and currency of each upload. That data was already being sent by the site and returned by the API — it was simply not displayed. Unlike the Google Ads metrics, it appears as soon as the order is uploaded and uses each order's own currency.
The value is only shown where it means something: sites that only track form leads see the dashboard exactly as before, with no columns of zeros.

1.4.0

Fix (privacy): the EU Cookie Law / TP Cookies consent plugin was never detected, because TagFlux looked for the wrong main file. Sites using it were treated as having no consent manager, so the click id cookie was stored even when the visitor had rejected cookies. All nine supported managers are now verified against the packages published on WordPress.org by an automated check.
New: a public hook so any consent manager can be supported, including custom banners. Declare the visitor's choice with the tagflux_consent_signals filter in PHP, or call window.tagfluxSetConsent( 'granted' | 'denied' ) from your banner. A real Consent Mode v2 signal always takes precedence, and returned values are validated.
New: support for the WP Consent API, the WordPress consent standard — read both in the browser and in PHP, so server-side uploads no longer depend on the browser. Requires the wp-consent-api plugin, which most consent managers integrate with.
New: support for consent managers running in IAB TCF mode, through the standard __tcfapi. No extra plugin needed.
New: WPConsent (by the WPForms team) is now recognised as a consent manager.
Fix: forms embedded through a reusable block or a theme block pattern were still invisible to Divi's detectors, which resolved the reference only in one of the two scan paths.

1.3.1

Fix: forms embedded through a reusable block or a theme block pattern (wp:block / wp:pattern) were invisible to the tracking script. The page content only stores a reference — not the form itself — so TagFlux concluded the page had no tracked form and never loaded its conversion script: browser-side conversions on those pages were silently lost. Block references are now resolved before the page is scanned, nested patterns included, and in place — so Divi's position-based form matching keeps the document order. Pages with the form placed directly in the content are untouched.

1.3.0

New: WooCommerce purchase tracking. Completed orders are sent to Google Ads as PURCHASE conversions with the order value and currency, from your server — the upload fires when the payment completes (including gateway webhooks), not when the buyer lands on the thank-you page. Works with both the classic and the block checkout, and with High-Performance Order Storage (HPOS).
New: the Google click identifier and the visitor's consent state are captured into the order itself at checkout time, so a payment confirmed hours later by a webhook still carries the right attribution and the right consent.
New: a WooCommerce card in the settings screen to create the purchase conversion action in Google Ads with one click. In dual mode the thank-you page fires the browser-side tag with the same transaction ID, so Google deduplicates both paths.
New: tagflux_conversion_value filter to adjust the reported conversion value per order (both the server-side upload and the browser-side tag use the filtered value).
Fix: with consent declined, the click identifier now also survives form submissions — the URL-decoration that kept attribution alive across links did not cover form actions, so the add-to-cart step silently dropped the click identifier and cookieless purchases were never attributed.
Fix: billing phone numbers are validated before being hashed for Enhanced Conversions, matching the form path — junk values are no longer uploaded as identifiers.

1.2.6

Fix: Ninja Forms conversions were counted twice in dual mode. Ninja Forms submits its own field model instead of the page form, so the shared order ID never reached the server and Google saw two different transactions for the same lead. The order ID now travels through Ninja Forms' own extra-data channel and both paths deduplicate again.
New: Complianz support without extra setup. Complianz only emits Google Consent Mode v2 when a Google service is configured in its wizard; without one, the visitor's choice never reached TagFlux and conversions were uploaded without a real consent signal (no Enhanced Conversions data, ever). TagFlux now also listens to Complianz's public consent API, so accepting or declining the banner works out of the box. A real Consent Mode v2 signal, when present, always takes precedence.
New: a settings notice when a consent banner has been active for a week but no consent signal has ever reached the site — the case where a site believes it is measuring consent and is not. The existing "your consent manager does not emit Consent Mode v2" notice now also stands down when the site demonstrably does receive the signal.

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

Google Ads Conversion Tracking for WordPress Forms – TagFlux

标签

下载

详情介绍:

安装:

屏幕截图:

升级注意事项:

常见问题:

更新日志: