Royal Plugins

RoyalComply – Cookie Consent, GDPR & CCPA Compliance Banner

GDPR and CCPA cookie consent banner with Google Consent Mode v2. Blocks analytics and marketing scripts until the visitor gives consent.

UserElements

Paste your Measurement ID. Get trustworthy WooCommerce GA4 ecommerce data.
GIA GA4 is a measurement-quality layer between WooCommerce and Google Analytics 4 (optionally Google Ads). It fires the full recommended ecommerce funnel, enriches every line item, backs up purchases server-side, and respects consent — without Google Tag Manager, without a data team, and without turning WordPress into a profit or attribution platform.
<h4>What GIA GA4 is</h4>
<ul>
<li>Complete GA4 ecommerce schema — not just purchase, but the real shopping and checkout funnel</li>
<li>Reliable revenue — browser + Measurement Protocol, with <code>session_id</code>, <code>event_id</code>, and consent-aware server sends</li>
<li>Better item data — categories, brand, GTIN, discounts, list attribution, classic templates and WooCommerce Blocks</li>
<li>GDPR-ready by default — Consent Mode V2, CMP bridges, geo rules, and a built-in banner</li>
<li>Store-owner UX — onboarding wizard, verification tools, and a lightweight dashboard for setup and shop pulse</li>
</ul>
GA4 stays the system of record. GIA GA4 feeds it well; it does not replace it.
<h4>What GIA GA4 is not</h4>
GIA GA4 deliberately avoids feature creep. It is not:
<ul>
<li>A profit, COGS, or margin-by-channel tool</li>
<li>A journey analytics or multi-touch attribution platform</li>
<li>A Meta CAPI, TikTok, or ad-spend ingestion hub</li>
<li>A heavy BI dashboard that duplicates GA4</li>
</ul>
The built-in dashboard gives operational context — weekly order insights, view-to-purchase, top customers — not a second analytics product inside wp-admin.
<h4>Who this is for</h4>
<ul>
<li>WooCommerce merchants who want complete GA4 ecommerce without hiring someone for GTM</li>
<li>Stores with a GA4 ≠ orders gap who need Measurement Protocol backup and deduplication</li>
<li>EU/UK shops that need Consent Mode V2 without wrestling CMP + gtag</li>
<li>Growth-minded stores that optionally want Google Ads purchase conversions on the same stack</li>
</ul>
Not primarily for: agencies running custom GTM containers, or merchants who want P&L-by-channel inside WordPress.
<h4>Why GIA GA4 vs other WooCommerce GA4 plugins</h4>
Most alternatives stop at purchase (and maybe add-to-cart). GIA GA4 goes deep on measurement quality:
<ul>
<li>Full funnel completeness (<code>view_item_list</code> through <code>purchase</code> and <code>refund</code>)</li>
<li>Rich <code>items[]</code> parameters on cart and checkout events</li>
<li>First-class WooCommerce Blocks cart and checkout support</li>
<li>Server-side purchase and refund backup with deduplication</li>
<li>Consent Mode V2 and CMP compatibility out of the box</li>
</ul>
<h4>GA4 ecommerce events</h4>
Discovery & product
<ul>
<li><code>view_item_list</code> — Shop, category, and tag archives (<code>item_list_id</code> / <code>item_list_name</code>)</li>
<li><code>view_item</code> — Product pages and variable-product variant changes</li>
<li><code>select_item</code> — Product clicks from classic shop grids (list context persists through the funnel)</li>
<li><code>view_search_results</code> — On-site product search terms (Extra GA4 events)</li>
<li><code>view_promotion</code> — On-sale products and WooCommerce store notices</li>
</ul>
Cart
<ul>
<li><code>add_to_cart</code> — AJAX, form submit, and WooCommerce Blocks cart (full item payloads)</li>
<li><code>remove_from_cart</code> — Cart page, mini-cart, and Blocks cart</li>
<li><code>view_cart</code> — Cart page and Blocks cart</li>
</ul>
Checkout
<ul>
<li><code>begin_checkout</code> — Classic and Blocks checkout</li>
<li><code>add_shipping_info</code> — Shipping method selected</li>
<li><code>add_payment_info</code> — Payment method selected</li>
<li><code>purchase</code> — Thank-you page with <code>transaction_id</code>, revenue, tax, shipping, coupons, payment method, new vs returning customer, and <code>event_id</code> for deduplication</li>
<li><code>payment_failure</code> — Checkout validation and payment errors (always tracked; classic + Blocks)</li>
<li><code>coupon_applied</code> / <code>coupon_removed</code> — Coupon usage</li>
<li><code>select_promotion</code> — Coupon codes applied at checkout</li>
</ul>
Post-purchase & account
<ul>
<li><code>refund</code> — When a refund is processed in WooCommerce (browser + server)</li>
<li><code>login</code> / <code>sign_up</code> — Optional (enable Extra GA4 events)</li>
<li><code>exception</code> — 404 pages (optional)</li>
</ul>
WooCommerce Subscriptions (when the extension is active)
<ul>
<li><code>subscription_started</code>, <code>subscription_cancelled</code>, <code>subscription_expired</code></li>
<li>Renewal orders sent as <code>purchase</code> via Measurement Protocol</li>
</ul>
Optional extras (off by default — Extra GA4 events setting)
<ul>
<li><code>cart_time_spent</code> — Seconds on cart/checkout before leaving</li>
</ul>
Core funnel events can be toggled individually in Settings → Events to reduce volume. Checkout errors, coupons, shipping, and payment events are always tracked.
<h4>Rich GA4 item data</h4>
Every funnel event can include detailed product line items:
<ul>
<li>Hierarchical categories (up to 5 levels)</li>
<li>Brand (auto-detects common brand taxonomies)</li>
<li>GTIN / EAN / UPC when stored in product meta</li>
<li>Variant, image URL, stock status</li>
<li>Sale <code>discount</code> amount on discounted products</li>
<li><code>item_list_id</code> and <code>item_list_name</code> carried from list views through add-to-cart and purchase</li>
<li>Product ID or SKU as <code>item_id</code> (setting)</li>
<li>Product Bundles use minimum bundle price in item data</li>
</ul>
Works on classic templates and WooCommerce Blocks cart/checkout via the Store API.
<h4>Server-side purchase & refund tracking</h4>
Browser tags are blocked by ad blockers and strict privacy settings. GIA GA4 mirrors <code>purchase</code> and <code>refund</code> from your server using the GA4 Measurement Protocol.
<ul>
<li>Saves GA4 <code>client_id</code> and <code>session_id</code> on the order at checkout</li>
<li>Sends <code>event_id</code> on server hits to deduplicate with browser <code>purchase</code> events</li>
<li>Retries failed sends via Action Scheduler</li>
<li>Respects stored analytics consent before server sends</li>
<li>Optional multi-currency normalization for foreign-currency orders (WOOCS / WooPayments rates)</li>
<li>Configurable trigger: order Completed or Processing</li>
</ul>
Add your GA4 API Secret in settings and use the built-in Verify tracking setup tool.
<h4>Consent Mode V2</h4>
<ul>
<li>gtag loads with consent defaulting to denied (configurable)</li>
<li>Built-in consent banner (auto-hides when a CMP is detected)</li>
<li>Geo-aware defaults: EU/EEA/UK → denied, US → granted (optional)</li>
<li>Bridges: CookieYes, Complianz, Cookiebot, and the <a href="https://wordpress.org/plugins/wp-consent-api/" rel="ugc">WP Consent API</a></li>
<li>Order-level consent stored for server-side tracking decisions</li>
</ul>
<h4>Google Ads (optional)</h4>
<ul>
<li>Fire <code>conversion</code> on purchase with your AW- account ID and conversion label</li>
<li>Enhanced Conversions: hashed billing data sent with purchase (same consent rules as GA4)</li>
</ul>
<h4>Other optional features</h4>
<ul>
<li>Google Tag Manager container ID (disable base gtag when GA4/GTM is loaded elsewhere)</li>
<li>Server-side gtag proxy (extends cookie lifetime, reduces blocker impact)</li>
<li>Cross-domain linker settings (domains + incoming parameters)</li>
<li>Transactional email link UTM tagging</li>
<li>First-touch UTM / <code>gclid</code> / <code>fbclid</code> saved to order meta + Traffic Source admin column</li>
<li>Exclude store administrators from tracking</li>
<li>GA4 DebugView mode</li>
<li>Gross vs net revenue on purchase events</li>
<li>Accepts <code>G-</code> and <code>GT-</code> Measurement IDs</li>
<li>HPOS (High-Performance Order Storage) compatible</li>
<li>Onboarding wizard on first activation</li>
<li>Admin warnings when Google Analytics for WooCommerce or Site Kit may duplicate tracking</li>
</ul>
<h4>Built-in dashboard (operational, not BI)</h4>
Admin menu: GIA GA4 → Analytics
<ul>
<li>Overview — Setup wizard, tracking verification, and weekly WooCommerce insights (revenue, refunds, customer mix, geo, checkout risk, tracking gap vs GA4 when Site Kit is connected)</li>
<li>Traffic — GA4 sessions, channels, and landing pages via <a href="https://wordpress.org/plugins/google-site-kit/" rel="ugc">Site Kit</a> when installed (optional)</li>
<li>Products — Local view-to-purchase report (no Google API required for view counts)</li>
<li>Customers — Top customers by lifetime spend</li>
<li>Settings — Full configuration (also at WooCommerce → Settings → Integrations, redirected to GIA GA4 settings)</li>
</ul>
<h4>Known gaps</h4>
Transparent limits aligned with the measurement-quality focus:
<ul>
<li><code>select_item</code> list attribution on Block Product Collection grids is not yet supported (classic shop grids are supported)</li>
<li>No <code>add_to_wishlist</code> or deep promotion CMS integration unless store-specific</li>
</ul>
These are extensions of the same GA4 data-quality goal, not a product pivot.
<h4>Privacy</h4>
<ul>
<li>Registers WordPress personal data export and erasure handlers</li>
<li>Checkout error logs and product view counters auto-expire (configurable retention: 30–365 days)</li>
<li>Enhanced conversion data is hashed before transmission; not stored by this plugin</li>
</ul>
<h3>External Services</h3>
This plugin connects to external services to provide analytics functionality. By using this plugin, you agree to the terms and privacy policies of these services.
1. Google Analytics 4 (required for tracking)
<ul>
<li>Purpose: Records ecommerce events, sessions, and conversions</li>
<li>Data sent: Page views, ecommerce events, hashed customer data (if Enhanced Conversions enabled), client/session identifiers</li>
<li>Domains: <code>www.googletagmanager.com</code>, <code>www.google-analytics.com</code>, <code>region1.google-analytics.com</code></li>
<li>Terms: <a href="https://marketingplatform.google.com/about/analytics/terms/us/" rel="nofollow ugc">Google Analytics Terms</a></li>
<li>Privacy: <a href="https://policies.google.com/privacy" rel="nofollow ugc">Google Privacy Policy</a></li>
</ul>
2. GA4 Measurement Protocol (recommended)
<ul>
<li>Purpose: Server-side <code>purchase</code> and <code>refund</code> event delivery when browser tracking is blocked</li>
<li>Data sent: Order value, line items, transaction ID, client ID, session ID, event ID</li>
<li>Endpoint: <code>https://www.google-analytics.com/mp/collect</code></li>
<li>Terms/Privacy: Same as Google Analytics above</li>
</ul>
3. Google Ads (optional)
<ul>
<li>Purpose: Purchase conversion signals for Smart Bidding</li>
<li>Data sent: Conversion value, transaction ID, hashed customer data (if enabled)</li>
<li>Domains: <code>www.googletagmanager.com</code></li>
<li>Terms: <a href="https://ads.google.com/home/terms/" rel="nofollow ugc">Google Ads Terms</a></li>
<li>Privacy: <a href="https://policies.google.com/privacy" rel="nofollow ugc">Google Privacy Policy</a></li>
</ul>
4. Google Tag Manager (optional)
<ul>
<li>Purpose: Tag deployment when you manage GA4 through GTM</li>
<li>Domain: <code>www.googletagmanager.com</code></li>
<li>Only loaded when a GTM container ID is configured</li>
</ul>
5. Google Site Kit (optional — dashboard only)
<ul>
<li>Purpose: Display GA4 traffic reports inside the GIA GA4 dashboard</li>
<li>Only used when Site Kit is installed and Analytics is connected</li>
<li>Plugin: <a href="https://wordpress.org/plugins/google-site-kit/" rel="ugc">Google Site Kit</a></li>
</ul>

GIA — GA4 Ecommerce Tracking for WooCommerce

Complete GA4 ecommerce tracking for WooCommerce — every funnel event, server-side purchase backup, Consent Mode V2. No Tag Manager. No bloat.

RoyalComply – Cookie Consent, GDPR & CCPA Compliance Banner vs GIA — GA4 Ecommerce Tracking for WooCommerce