Carticy Conversion Tracking with GA4, Google Ads, and Meta Pixel for WooCommerce
| 开发者 |
carticy
alikhallad |
|---|---|
| 更新时间 | 2026年7月6日 17:20 |
| 捐献地址: | 去捐款 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
woocommerce_payment_complete plus paid-status fallbacks), so conversions are recorded even when a customer never returns from an off-site payment gateway. Classic, shortcode, and block (Store API) checkout are all supported.
The free plugin includes:
- Client-side GA4, Google Ads, and Meta Pixel tracking from merchant-supplied IDs (direct tag injection, or an optional GTM dataLayer mode with a generated import container).
- Purchase events deduplicated by order id across every layer (
transaction_idfor GA4,eventIDfor Meta), plus add-to-cart and begin-checkout events. - Consent-respecting behavior out of the box: multi-source consent intake (WP Consent API, Google Consent Mode v2, common CMP cookies, a first-party hook), a tri-state consent record stored per order, and default-deny before any tag loads.
- Duplicate-tag detection so an existing GA4/Pixel/GTM setup is never silently double-fired.
- WordPress privacy tooling: personal data exporter and eraser coverage, configurable IP anonymization, and a data retention window.
安装:
- Upload the plugin files to
/wp-content/plugins/carticy-conversions-for-woocommerce/. - Activate the plugin through the Plugins menu in WordPress.
- Make sure WooCommerce is active.
- Add your GA4 Measurement ID, Google Ads conversion ID/label, or Meta Pixel ID to enable tracking. No events are sent before you configure a destination.
屏幕截图:
常见问题:
Does this version send tracking events?
Yes - once you configure at least one destination (GA4, Google Ads, or Meta Pixel) with your own IDs. Nothing is sent before a destination is configured, and events respect the visitor's stored consent.
Does the WordPress.org package include Pro server-side providers?
No. Premium server-side provider implementation paths are excluded from the WordPress.org artifact.
Does the plugin make outbound HTTP requests on activation?
No. The plugin does not contact Google, Meta, or Carticy on activation. Google/Meta requests happen only after you configure the matching destination and the visitor's consent allows them. Freemius may be loaded for licensing and upgrade handling according to its WordPress.org-compliant opt-in flow when the SDK is present.
Does it work with the block (Store API) checkout?
Yes. Purchases are tracked from WooCommerce's server-side order-paid hooks, which fire identically for classic, shortcode, and block checkout.
更新日志:
- Order-paid purchase tracking engine with per-destination idempotency.
- Client-side GA4, Google Ads, and Meta Pixel tracking (direct and GTM dataLayer modes).
- Multi-source consent intake with per-order tri-state consent records.
- Identity and attribution capture (client id, click ids, UTM first/last touch).
- WordPress privacy exporter/eraser, IP anonymization, retention purge.
- WooCommerce HPOS and cart/checkout block compatibility.