Description
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. The audit runs on tageasy.io against your public home page, and the result is public: tageasy.io shows the score and findings for your domain at tageasy.io/sites/your-domain (see External services).
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. It checks for other containers when you connect, whenever a plugin is activated or deactivated and twice a day, and checks Site Kit and GTM4WP on every page. Your container keeps loading if tageasy.io is briefly unreachable.
Get events worth tagging. The plugin pushes standard GA4-schema events to the dataLayer:
generate_leadon 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_clickandemail_clickon tel: and mailto: links
Respect consent. With your container, 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 a banner that registers a consent type with the WP Consent API, consent choices are forwarded to Google.
Know when it breaks. With a connected account, the Overview tab and a dashboard widget show your tracking score and plan usage. On TagEasy plans with event monitoring they also show which events have fired in the last 7 days and open alerts, with one click through to the full TagEasy dashboard.
Planned: WooCommerce orders server-side. The plugin includes code to send each paid order, refund and cancellation from your server to TagEasy, which would forward it to the destinations you connect there, so purchases are counted even when a browser blocks tags. TagEasy does not accept these orders yet, so the feature is not available on any plan. It is off by default, and the “Send WooCommerce orders server-side” setting appears on the Settings tab only once TagEasy turns the feature on for your account.
What is free?
The plugin is a bridge to the TagEasy service. The plugin itself never locks or disables anything; what a connected site sees depends on its TagEasy plan.
- Free, no account: the tracking audit and the dataLayer events.
- Free TagEasy account: the Google Tag Manager install with conflict detection, Consent Mode v2 defaults, and the Overview tab with your tracking score.
- Growth plan and up: event monitoring, which shows which of your events fired in the last 7 days.
- Business plan and up: alerts when event volume drops.
Server-side WooCommerce orders are planned and not yet available on any plan.
New TagEasy accounts get a 14-day trial with the paid monitoring features. Prices are at https://www.tageasy.io/pricing.
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. When a container ID is set, every front-end page view loads https://www.googletagmanager.com/gtm.js (and the ns.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. GTM loads once an account is connected and your TagEasy site has a container; you can turn it off in Settings. Nothing from Google loads before that.
Provided by Google LLC: Terms https://policies.google.com/terms, Privacy https://policies.google.com/privacy
TagEasy
Used for the free tracking audit, the account connection and tracking monitoring. The service runs at https://www.tageasy.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. tageasy.io fetches your public home page and publishes the result: the score and findings for your domain appear on a public page at https://www.tageasy.io/sites/your-domain, which search engines can index, and in the list of recent audits on tageasy.io. Anyone can run the same audit of any public site on tageasy.io.
- 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. Requests that carry the token never follow redirects. 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 (not available yet: TagEasy does not accept these orders on any plan, so the setting does not appear; once it does, your server sends them 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, first and last name, city, state, postcode and country (not the street 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/_fbccookies and ad click ids likegclid), 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_idscookie (only after advertising consent; otherwise for the browser tab only) and mirrors the visitor’s Consent Mode choices into a_tageasy_consentcookie. 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 event monitoring): every front-end page view that loads your container also loads a small script from tageasy.io, at a per-site URL with a token that your account provides. The first time on a page that one of your monitored events fires, the script reports the event name and the time, the names of the event’s parameters and the type of each value (such as text or number), and the page address as origin and path, without the query string or fragment. The path can still contain an ID, such as the order number in a WooCommerce order-received address (
/checkout/order-received/123/). When a value, or the query string or fragment, looks like an email address, phone number or card number, the report also flags which parameter (or the page address) and which kind, never the value. It never sends parameter values, so no form contents or amounts, and the report contains no cookie or visitor identifier. As with any request, the visitor’s browser sends tageasy.io its IP address and user agent (standard request headers) when it loads the script and when it sends a report; TagEasy does not store them with the report. The script is only loaded when the container loads, so it respects the same administrator exclusion and thetageasy_tracking_allowedfilter.
The Google Tag Manager conflict check fetches your own site’s home page from your server: when you connect, after a plugin is activated or deactivated, after the plugin is updated, twice a day, and when you click “Check for other containers” on the Setup tab. That request goes to your site only, not to a third party.
Provided by Hexcorp: Terms https://www.tageasy.io/terms, Privacy https://www.tageasy.io/privacy
Installation
- Install from the Plugins screen, or upload the
tageasyfolder to/wp-content/plugins/. - Activate the plugin.
- Open TagEasy in the admin menu.
- Click Run free audit to see how your tracking is doing, or Connect TagEasy account to install Google Tag Manager and turn on monitoring.
- Review the Settings tab: administrator exclusion, Consent Mode defaults, and which events to send.
FAQ
Do I need a TagEasy account?
No. The free audit and the dataLayer events work without one. A free account is needed for the Google Tag Manager install and Consent Mode defaults, because the plugin reads your container from tageasy.io. No payment card is required. Event monitoring needs the Growth plan or above, and alerts the Business plan; see “What is free?” above.
I already load Google Tag Manager from another plugin or my theme.
The plugin detects containers from Site Kit, GTM4WP, WPCode, the legacy Insert Headers and Footers option, and anything hard-coded in your theme, and warns you on the Setup tab instead of loading a second container. Site Kit and GTM4WP are checked on every page; the full check runs when you connect, when any plugin is activated or deactivated, after the plugin is updated, twice a day, and when you click “Check for other containers”. You can override this in Settings if the two containers are intentionally different.
Does the plugin send data about my visitors to TagEasy?
TagEasy does not build visitor profiles, and the plugin does not track visitors for TagEasy’s own purposes. One feature sends data to tageasy.io on your behalf today, and one planned feature would:
- On plans with event monitoring, visitors’ browsers load a verification script from tageasy.io, and it reports which of your monitored events fired: the event name and time, the names and value types of its parameters, the page origin and path (which can contain an ID, such as a WooCommerce order number on the order-received page), and a flag naming the parameter, or the page address, whose value looks like an email address, phone number or card number. No parameter values, query strings, cookies or visitor identifiers. Like any request, the script load and the report carry the visitor’s IP address and the browser’s user agent; TagEasy does not store them with the report.
- Server-side WooCommerce orders, which are planned and not yet available on any plan, would send each order from your server to tageasy.io once “Send WooCommerce orders server-side” is on: the buyer’s email, phone, first and last name, city, state, postcode and country (not the street address), checkout IP address and user agent, and advertising and analytics identifiers, for TagEasy to forward to the destinations you connected. TagEasy would process this data for you, as your processor.
Everything else the plugin does (your GTM container, the dataLayer events) stays between your site, your visitors and the services in your own container. The External services section lists every request.
I use Complianz, CookieYes or Cookiebot.
Those plugins set Consent Mode themselves, so TagEasy does not add its own defaults and says so on the Setup tab. With a banner that registers a consent type with the WP Consent API, the plugin forwards consent choices to Google as updates. The WP Consent API on its own, without a banner that registers a consent type, changes nothing: the defaults stand.
Which WooCommerce events are sent?
view_item, view_item_list, add_to_cart, remove_from_cart, begin_checkout, add_payment_info and purchase, in the GA4 ecommerce schema. Purchase fires once per order, guarded by order meta, and is skipped for failed or cancelled orders.
What does “Send WooCommerce orders server-side” do?
Nothing yet: TagEasy does not accept server-side orders on any plan, and the setting appears on the Settings tab only once TagEasy turns the feature on for your account. Once available, it sends each paid order from your server to TagEasy, which forwards it to the server-side destinations in your account (GA4 Measurement Protocol, Meta Conversions API, Google Ads and others). The browser purchase event carries the same woo-order-<id> event id, so destinations that deduplicate count the order once. Refunds and cancellations follow unless you turn “Send refunds and cancellations” off.
What happens if tageasy.io is unreachable?
Your Google Tag Manager container keeps loading: the plugin keeps the last container tageasy.io reported and replaces it only after a successful refresh. It stops loading only when you disconnect, or when tageasy.io answers that the site’s key was revoked or the site was deleted. The TagEasy screens show when the last refresh failed and how old the data is.
Order events are queued with Action Scheduler (part of WooCommerce) and retried after 1, 5 and 15 minutes, then 1, 3 and 6 hours. While tageasy.io reports that it cannot record orders yet, they stay queued for up to 7 days without using up those retries. The Overview tab shows the last send, failures in the last 7 days and the queue length. Nothing is sent during the shopper’s checkout request.
A personal-data erasure is only treated as done when tageasy.io confirms it. If the site’s key was revoked or tageasy.io keeps failing, the erasure (order ids and a hash of the email, never the address) is kept and sent again when the site reconnects.
Can I change or drop events?
Yes. Filter tageasy_datalayer_push to edit or drop any push, tageasy_woocommerce_item to adjust item fields, tageasy_gtm_container_id to override the container, and tageasy_tracking_allowed to skip output on specific requests.
I changed my WordPress security keys (salts).
The site key is stored encrypted with those keys, so it can no longer be read. The plugin shows a notice asking you to reconnect, and keeps loading your last known container in the meantime. Connect again from the Setup tab, or click “Forget this connection” there to stop using TagEasy on this site.
What happens when I delete the plugin?
The site token is revoked at tageasy.io and removed. Settings and cached results are kept unless you tick “Remove all plugin data when the plugin is deleted” in Settings first. Your TagEasy account keeps its site and history.
Screenshots






Changelog
0.2.1
- Fix: the Google Tag Manager container no longer disappears from the site when the 12-hour refresh fails, tageasy.io is unreachable or a persistent object cache evicts the cache. The last good container is kept until you disconnect, or tageasy.io reports the key revoked or the site deleted. The refresh is scheduled as soon as you connect or activate, and a site whose container had already dropped under 0.2.0 fetches it again right after this update.
- Fix: double-load protection no longer lapses after 12 hours or waits for a manual check. The result is kept, the check runs on connect, on activation, after this update, whenever a plugin is activated or deactivated and twice a day (also while the site key cannot be read), and Site Kit and GTM4WP containers are checked on every page.
- Fix: a changed set of WordPress security keys (salts) no longer silently stops tracking. A dismissible notice on the Dashboard and Plugins screens asks you to reconnect, GTM keeps loading, and the Setup tab can forget the old connection. A damaged stored key can no longer cause an HTTP 500.
- Security: requests that carry the site token never follow redirects, and a redirect counts as a failure.
- Fix: with the WP Consent API but no banner that registers a consent type, no “granted” consent update is pushed over the EEA defaults.
- CookieYes 3.x is detected as the consent manager.
- Fix:
add_payment_infonow fires on the classic (shortcode) checkout. - Fix: forms that reload the page (WPForms, Gravity Forms or Fluent Forms without AJAX) now push
generate_leadagain. The cookie that carries the lead to the next page was URL-encoded twice and could not be read. - Fix: one Fluent Forms submission gives one
generate_lead. The full-page lead cookie is not set for AJAX or REST submissions and is cleared with the path and domain it was set with, so subdirectory installs no longer repeat leads. - “Refresh data” reports the actual result (key revoked, site deleted, tageasy.io unreachable), and every TagEasy tab says when the last refresh failed and how old the data is.
- The Consent Mode card and the Overview say “Not active” when the container, and so the consent defaults, are not loading.
- The suggested privacy policy text lists the cookies the plugin sets, describes what the verification script reports, names Hexcorp as the operator of tageasy.io, and follows your consent settings.
- Readme: what is free and what needs a paid TagEasy plan, the public audit result, and server-side orders described as planned and not yet available.
0.2.0 – 2026-11-05
- First public release on WordPress.org: free tracking audit, account connection with a site-scoped, revocable token, Google Tag Manager install with detection of existing containers, Consent Mode v2 defaults and the WP Consent API bridge, dataLayer events for five form plugins, WooCommerce and contact links, the Overview tab and dashboard widget, privacy policy suggestion and opt-in data removal on uninstall.
- Server-side WooCommerce orders, refunds and cancellations (off by default), queued with Action Scheduler and retried with backoff, with erasure of TagEasy’s copy when WooCommerce erases an order’s personal data.
- Declares compatibility with High-Performance Order Storage and the cart and checkout blocks.
- Versions 0.1.0 to 0.1.2 were pre-release builds that were never published on WordPress.org.
