| 开发者 | tagflux |
|---|---|
| 更新时间 | 2026年7月23日 04:59 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
tagflux folder to /wp-content/plugins/, or install it from the WordPress plugin repository.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.
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.
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.
TagFlux currently supports Contact Form 7, WPForms, Elementor Pro Forms, Ninja Forms and Divi Forms.
TagFlux tracks WordPress form submissions that come from Google Ads traffic. It captures the gclid from the ad click, stores it in a first-party cookie, and sends the conversion to Google Ads through the TagFlux backend when a tracked form is submitted.
Yes, you need an active Google Ads account to track conversions.
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 — no container, no code.
Yes. You can choose multiple forms to track, and every submission of each tracked form is reported to Google Ads.
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.
Any theme. Form detection currently covers Contact Form 7, WPForms, Elementor Pro, Ninja Forms and Divi 4 forms, regardless of the theme you use.
Yes. The tracking cookie is tagged as marketing so consent managers can control it. 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.
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 — 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.
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.
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 uninstall.php).
gclid/wbraid/gbraid in a cookie and a hidden form field (cookieless fallback).