Website

Audit WooCommerce purchase tracking in GA4, Google Ads and GTM

Compares daily WooCommerce orders with GA4 purchases and Google Ads conversions over 14 days, maps every tag source, and pinpoints duplicate or missing purchase tracking before proposing previewed fixes.

When to use it

When WooCommerce orders, GA4 purchases and Google Ads conversions do not match and you suspect duplicate or missing purchase tracking.

What you get

A 14-day daily table of orders vs GA4 vs Google Ads with gap percentages and evidence-backed findings, then fixes proposed one by one and applied only after your approval.

Does it change anything in my account?

Only with your approval. The assistant first shows a preview of every change and waits for your go-ahead.

Works with

WordPress, GA4, Google Ads, Tag Manager

Fill in before sending

[WordPress site][Google Ads account]
Check whether [WordPress site] reports purchases correctly to GA4 and to [Google Ads account]. 1. Daily comparison, last 14 full days: - WooCommerce: page through wordpress_woo_orders until you pass orders older than 14 days. Count only completed and processing orders per day. Tell me if the orders run out before day 14, and treat any order that looks like a test (my own name, 0 total) separately. - GA4: run ga4_report with dimension "date" and dimension2 "event", and take only the purchase event count. Do not use the total conversions figure, it sums every key event. - Google Ads: run google_ads_query on the purchase conversion action, segmented by segments.date and segments.conversion_action_name, so other actions do not inflate the number. Note that Google Ads reports conversions by click date, so recent days may still fill in. - Note the time zones of the shop, the GA4 property and the Ads account if they differ, since that shifts orders between days. 2. Settings: - Confirm purchase is a key event with ga4_list_conversions. - With list_conversion_actions and get_conversion_settings, confirm the Ads purchase action is enabled, included in conversions (primary), has recorded data, and check its counting type. MANY_PER_CLICK on a purchase action is a common source of over-counting. 3. Tag inventory: - wordpress_tracking for every place a GA4 or GTM tag fires (plugins, WPCode snippets, header/footer code, theme options). Read any suspicious snippet with wordpress_snippet and any theme option it points to with wordpress_option. - wordpress_list_plugins for plugins that send purchase data on their own (for example GTM4WP, WooCommerce Google Analytics, Site Kit, PixelYourSite). - In GTM, list the tags and triggers in the live container's workspace and flag every tag that sends purchase to GA4 or a Google Ads conversion, with its conversion ID/label and trigger conditions. Use gtm_workspace_status to see whether any purchase change is sitting unpublished. - Consent mode cannot be read as a single setting. Report whatever the tag inventory shows (a consent plugin, consent settings in GTM tags, a consent snippet) and say plainly if you cannot tell. Deliver: - A daily table with these columns: date, orders, GA4 purchases, Google Ads conversions, GA4 gap % vs orders, Ads gap % vs orders. - A numbered list of findings, each tied to the evidence that supports it. Use these thresholds only as pointers, then confirm the cause from the inventory: - More than 10% above orders: look for two sources sending the same purchase (a plugin plus a GTM tag, two containers), a missing transaction_id, MANY_PER_CLICK counting, or a thank-you trigger that fires on reload. - More than 25% below orders: look for a missing or unpublished tag, a trigger condition that misses the thank-you URL, consent blocking, or a payment gateway that does not return to the thank-you page. If the order data does not show the payment method, ask me which gateways we use. Propose fixes naming the exact tag, trigger, snippet or plugin to change. Make no changes until I approve a preview of each one.

Related searches

These prompts work best when your AI assistant is connected to your accounts with Opus Growth.

Connect your accounts free

More prompts

WebsiteChanges after your approval

Rewrite meta titles and descriptions for pages with low organic CTR

Finds page-one pages that get impressions but few clicks, compares them to your site-wide CTR, and rewrites their meta title and description around the queries that actually bring them traffic.

When to use itWhen your pages rank on page one and get impressions but few clicks, so your titles and descriptions are probably not convincing.

Search Console, WordPress
WebsiteChanges after your approval

Rebuild the site menu around pages that actually convert

Matches GA4 landing-page performance against your WordPress menus, flags valuable pages missing from the navbar, dead weight and broken links, and proposes a leaner main menu.

When to use itWhen your site menu feels cluttered or outdated and you suspect it does not point visitors to the pages that actually bring conversions.

GA4, WordPress
WebsiteChanges after your approval

Plugin and tracking health check before it breaks your conversions

A plugin-by-plugin action list that flags outdated, duplicate and conflicting plugins and double-firing tags.

When to use itWhen your WordPress site has too many plugins, updates piling up, or you fear duplicate tags are inflating the conversions your ads optimize toward.

WordPress
WebsiteChanges after your approval

Replace an old phone number everywhere on the site, safely

A full map of where the old number appears, a dry-run diff of the bulk replace, and a list of places that need manual fixes.

When to use itWhen your phone number has changed and you need to be sure the old one no longer shows anywhere on your website.

WordPress, Business Profile