Recommended Free Tools
Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
To track WordPress conversions reliably, choose one Google tag architecture, define the business outcome, send a dedicated event when that outcome succeeds, and verify it in Google Tag Assistant and GA4 Realtime or DebugView. A page-view tag alone cannot prove that a purchase or qualified lead occurred. WooCommerce stores also need ecommerce events, while form tracking must separate successful submissions from errors, spam and abandoned attempts.
1. Choose one tracking architecture
Your first decision is how the Google tag and conversion events will be managed. Use one coordinated implementation rather than installing overlapping plugins, a separate gtag.js snippet and Google Tag Manager (GTM) tags that measure the same action.
| Architecture | Coverage | Control | Duplication risk | Maintenance and debugging |
|---|---|---|---|---|
| WordPress or WooCommerce Google tag integration | Page views and supported sales or conversion events | Plugin defaults and available settings | Low when it is the only Analytics implementation | Simple updates; verify with Tag Assistant and GA4 |
Direct gtag.js implementation |
Page views plus custom events you code | High control over event names and parameters | High if another plugin also loads the tag | Requires code ownership and version testing |
| Google Tag Manager | Forms, ecommerce and other interactions through triggers and data layers | Highest flexibility without editing every page template | High if plugins also send identical events | Strong preview and debugging tools, but more configuration to maintain |
Google’s CMS guidance treats WordPress and WooCommerce as environments that can accept a Google tag ID. If your installation has no native field or supported integration, add the tag manually to the site HTML or manage it through GTM. Decide which system owns Analytics before creating any conversion event.
2. Define the conversion before installing anything
A conversion is a completed business outcome, not just an interaction with a page. Write the success condition first:
#1 Best Overall
- Purchase: an order reaches the store’s successful-payment or completed-order state.
- Qualified lead: a form is accepted and produces a lead your business can follow up.
- Registration: an account or event registration is successfully created.
- Other meaningful action: for example, a booking confirmation or a completed quote request.
GA4 events represent interactions. They can be sent with gtag() or through GTM, then inspected in Realtime and DebugView. Use an event that fires at the success point, such as a confirmation state or server-rendered thank-you page, rather than treating a button click as proof of completion.
3. Install the base tag once
- Choose the integration that will own the Google tag: a supported WordPress/WooCommerce integration, direct
gtag.js, or GTM. - Enter the correct Google Analytics 4 Measurement ID, which begins with
G-, or configure the relevant Google tag ID in the selected system. - Remove or disable any second Analytics implementation that loads the same property. WooCommerce Pro documentation specifically warns that another Analytics implementation should be removed when its implementation is used, because duplicate tags can inflate users, sessions and events.
- Publish only after the tag is present on the pages where the conversion journey occurs.
Do not add a second page-view tag merely because you still need conversion events. Events use the existing tag architecture; they do not require a second Analytics property or duplicate base snippet.
Rank #2
4. Configure WooCommerce ecommerce tracking
Enter the GA4 property
- In WordPress, open WooCommerce > Settings > Integration > Google Analytics.
- Enter the GA4 Measurement ID beginning with
G-. - Save the settings and confirm that the integration is the only component sending Analytics data.
Measure the whole shopping funnel
Useful WooCommerce reporting depends on ecommerce events, not only visits to product pages. Configure and verify events appropriate to your store, including:
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problems- Product detail views
- Add-to-cart actions
- Checkout progression
- Completed purchase
- Refunds
Google’s ecommerce guidance requires these events to be sent by the site implementation or the GTM container. A purchase event should include the order’s products and transaction values from the store’s ecommerce data; do not substitute a generic page view for an order.
5. Track WordPress forms at the success point
Contact Form 7 and similar forms
Form integrations such as GTM4WP can expose separate outcomes for Contact Form 7, including sent, failed, spam, invalid, aborted and terms-not-accepted states. Use those distinctions in your triggers. A successful submission should be the conversion; validation errors and spam should not be counted as leads.
Recommended GA4 event design
GA4’s recommended form events include form_start, form_submit and generate_lead. A practical arrangement is:
form_startwhen a visitor begins entering a form.form_submitwhen the form submission request is accepted.generate_leadonly when the submission meets your business definition of a qualified lead.
For a confirmation-page workflow, trigger the conversion on the unique success page or success message. For an AJAX form, use the integration’s successful-send event or a data-layer signal rather than a click trigger. If a visitor can submit repeatedly, decide whether each accepted submission is a conversion and keep that rule consistent.
6. Mark the event as a conversion in GA4
- Send the event from the form, WooCommerce integration,
gtag.jsor GTM. - Open GA4 and locate the event name after it has arrived.
- Mark the appropriate event as a conversion (GA4 may label this as a key event in current interfaces).
- Use a distinct event name for each business outcome so purchases, leads and registrations remain reportable separately.
Do not mark every diagnostic event as a conversion. Events such as form_start help analyze friction but do not represent a completed lead unless that is genuinely your business rule.
7. Test before trusting reports
Google Tag Assistant
- Open Google Tag Assistant and connect it to the page where the journey begins.
- Accept the site’s cookie banner when testing an opted-in visitor.
- Complete the form or a test purchase through the intended success path.
- Inspect warnings, errors, fired tags, event names and parameters.
GA4 Realtime and DebugView
Use GA4 Realtime to confirm that the property receives the activity. Use DebugView for event-level inspection while the test browser is in debug mode. Confirm the exact event name, relevant parameters, timing and whether the event arrives once rather than multiple times.
Test failure branches
- Submit a form with a missing required field and verify that no lead conversion fires.
- Use an invalid or spam-blocked submission and check that it is recorded only as the appropriate failure outcome, if you choose to measure it.
- Reload or revisit a confirmation page to see whether the purchase or lead event can be duplicated.
- For WooCommerce, test a successful order and the store’s refund workflow where applicable.
8. Implement consent correctly
WooCommerce states that Google Consent Mode was introduced in March 2024. Visitors in the European Economic Area, the United Kingdom and Switzerland must grant the required cookie consent before analytics data is captured. Your consent-management plugin should integrate with the WordPress Consent API.
Document both paths: what tags and events run after consent, and what happens when a visitor denies it. Regional settings can change the volume and detail of data in GA4, so a lower count after a consent change is not automatically a tagging failure.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Quick Recap
9. Troubleshoot common problems
No events appear
- Check that the Measurement ID or Google tag ID belongs to the intended property.
- Confirm that the consent banner has granted the permissions required for the test.
- Use Tag Assistant to see whether the base tag and event tag fired.
- Check Realtime and DebugView for the correct property and exact event name.
Conversions are doubled
- Search the site for multiple plugins or snippets loading the same Google tag.
- Check whether both a plugin and GTM send the same purchase or lead event.
- Remove the duplicate owner, then retest in Tag Assistant.
Purchases are missing or have wrong values
- Verify that the event fires only on the completed-order state, not when checkout begins.
- Inspect product, transaction and value parameters in the event payload.
- Check payment redirects, failed orders and refund handling separately.
Form submissions are overcounted
- Replace button-click triggers with the integration’s successful-send signal or confirmation state.
- Exclude invalid, spam and aborted outcomes from the lead conversion.
- Prevent a confirmation-page refresh from sending the same event repeatedly.
10. A maintenance checklist
- Keep one documented owner for the Google tag and each conversion event.
- Retest after WordPress, WooCommerce, form-plugin, consent-plugin or GTM changes.
- Review Tag Assistant warnings and GA4 DebugView after template or checkout changes.
- Record which regions require consent and which events are suppressed without it.
- Periodically compare order and lead records with Analytics totals, allowing for consent-denied visits and platform processing differences.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
