Analytics & Tracking
Usage
Open Appearance β Customize β Scripts & Embeds β Analytics & Tracking and paste IDs only for services you use β Google Analytics, Google Tag Manager, Facebook Pixel, LinkedIn, StackAdapt, Hotjar, and the verification fields when a platform requires them. Leave unused rows blank.
Choose Tracking Load Strategy to control when scripts run: After Page Load (default) or First Interaction (first click or scroll). Turn on Track Admin Sessions only while debugging so your own visits are not excluded.
When WooCommerce is active, Enhanced Ecommerce Tracking sends a purchase event to GA4 or GTM on completed orders. Ecommerce Debug Mode logs those events to the browser console β use for testing only.
When to use it
- Launching a new site and connecting marketing tags in one central place.
- Improving initial page speed by deferring tags until interaction.
- Measuring shop revenue after WooCommerce checkout without editing theme templates.
Tips
- Pair with GDPR Banner so tracking waits for consent when the banner is enabled.
- You do not need both a GA4 ID and GTM unless your tag plan calls for it β follow your analytics team's setup.
- Disable Track Admin Sessions on production sites so reports reflect real visitors.
- After publishing, verify tags in a private window with your provider's debugger.
Settings
Analytics & Tracking

Enable analytics and tracking scripts for logged-in administrators. This is useful for debugging and development, but should be disabled in production so that you don't track your own activity.









Wait until the page finishes loading, or until a visitor first clicks or scrolls, before loading tracking scripts. Clicks and purchases are still recorded either way.

Enable tracking of WooCommerce purchase events (transactions, revenue, products). Requires WooCommerce and a configured Google Analytics or Google Tag Manager ID above. This will send a 'purchase' event to your analytics when an order is completed.

Log all GA4 ecommerce events to the browser console β including events that are blocked by gates (toggle disabled, no consent, admin, etc.). Use this for testing and development only.