About this plugin
Conversion tracking on WordPress usually means pasting snippets into a theme, hoping the form plugin fires something useful, and finding out weeks later that the purchase tag broke. TagEasy makes the setup a few clicks and keeps watching it afterwards.
Start with a free audit, no signup. From the plugin’s Overview tab, audit your site and get a score out of 100 with a pass/fail list: Google Tag Manager, GA4, Consent Mode v2, ad pixels, PII in URLs, script weight, HTTPS, duplicate GA4 properties and more, each with the fix.
Install Google Tag Manager without touching your theme. Connect a free TagEasy account and the plugin loads your container on every page, excludes logged-in administrators, and refuses to double-load when Site Kit, GTM4WP, WPCode or your theme already has a container.
Get events worth tagging. The plugin pushes standard GA4-schema events to the dataLayer:
- generate_lead on successful submits from Contact Form 7, WPForms, Gravity Forms, Elementor Pro Forms and Fluent Forms
- WooCommerce: view_item, view_item_list, add_to_cart, remove_from_cart, begin_checkout, add_payment_info, purchase (once per order), for both the classic and the Blocks cart and checkout
- phone_click and email_click on tel: and mailto: links
Respect consent. Google Consent Mode v2 defaults are set before any tag loads: denied for visitors in the EEA, UK and Switzerland until they consent, granted elsewhere. If Complianz, CookieYes or Cookiebot is active, TagEasy leaves consent to them; with any banner that supports the WP Consent API, consent choices are forwarded to Google.
Send WooCommerce orders server-side (optional). On TagEasy plans with server-side tracking, turn on “Send WooCommerce orders server-side” and each paid order, refund and cancellation is sent from your server to TagEasy, which forwards it to the destinations you connect there. Purchases are then counted even when a browser blocks tags or the shopper never reaches the thank-you page.
Works with the classic and the block checkout and with High-Performance Order Storage.
Know when it breaks. With a connected account, the Overview tab and a dashboard widget show your tracking score, which events have fired in the last 7 days, open alerts and plan usage, with one click through to the full TagEasy dashboard.
The plugin is a bridge to the TagEasy service. io add more sites, higher event volume, container audits, server-side tagging and alerting. Nothing in this plugin is locked behind a payment.
External services
This plugin connects to the following services.
Google Tag Manager
Used to load the Google Tag Manager container configured in your TagEasy account. html noscript iframe for visitors without JavaScript). Google receives the visitor’s IP address, user agent, page URL and referrer, plus any data the tags in your container collect.
Consent Mode v2 defaults are set before GTM loads, unless Complianz, CookieYes or Cookiebot manages consent on the site. Logged-in administrators are excluded by default. Nothing loads until an account is connected and GTM is enabled in Settings.
com/privacy
TagEasy
Used for the free tracking audit, the account connection and tracking monitoring. io. Every request your server makes to it carries a User-Agent header with the plugin version, your WordPress version and your home URL.
What is sent, and when:
- Running the free audit (admin, when you click “Run free audit” or “Re-run audit”): the host name of your home URL. No account is needed.
- Connecting an account (admin, when you click “Connect TagEasy account”): your home URL, the connecting administrator’s email address, and your WordPress and plugin versions. In return the plugin receives a token that identifies this one site. It is stored encrypted and can be revoked from the plugin or from your TagEasy account at any time.
- While connected (your server, twice a day and when you open the Overview tab or press “Refresh data”): the site token, to read your site’s Google Tag Manager container ID, tracking health, alerts and plan usage. Disconnecting, or deleting the plugin, sends one request to revoke the token. Your visitors’ browsers send nothing to tageasy.io through these requests.
- Server-side WooCommerce orders (your server, only when “Send WooCommerce orders server-side” is turned on in Settings): about three minutes after an order is paid, and when it is refunded or cancelled, your server sends the order to tageasy.io: order number and totals, line items, coupon, currency, the billing email, phone, name and address, the customer IP address and browser user agent recorded at checkout, the landing page, advertising and analytics identifiers read from first-party cookies on your site at checkout (such as the Google Analytics client id and session id, the Meta _fbp / _fbc cookies and ad click ids like gclid ), and the consent choices recorded at checkout. tageasy.io forwards these events to the analytics and advertising services connected in your TagEasy account, such as Google Analytics, Google Ads, Meta, TikTok, Pinterest or Snapchat, under your account’s settings. When this is on, the plugin’s front-end script also stores ad click ids from landing URLs in a first-party _te_ids cookie (only after advertising consent; otherwise for the browser tab only) and mirrors the visitor’s Consent Mode choices into a _tageasy_consent cookie. When WooCommerce erases an order’s personal data, the plugin asks tageasy.io to erase its copy, sending the order id and a SHA-256 hash of the billing email, never the address itself.
- Event verification (front end, connected accounts on plans that include health monitoring): every front-end page view loads a small script from tageasy.io, at a per-site URL with a short-lived token that your account provides. As with any script load, tageasy.io receives the visitor’s IP address, user agent and page URL. The script reports which of your configured event names fired, with the page URL. It does not send form contents, order details, or any identifier of the visitor. It is only loaded when the container loads, so it respects the same administrator exclusion and the tageasy_tracking_allowed filter.
The Google Tag Manager conflict check on the Setup tab fetches your own site’s home page from your server. That request goes to your site only, not to a third party.
io/privacy