GA4 Ecommerce Validator

Why GA4 Ecommerce Event Validation Is Non-Negotiable

GA4 ecommerce tracking gives online stores unparalleled insight into customer behaviour — from which product lists drive the most add-to-cart actions, to how checkout funnel drop-off rates vary by device and traffic source. But GA4 ecommerce reporting is only as good as the underlying event data. A single missing required field — a transaction_id sent as a number instead of a string, or a currency value in the wrong format — causes purchase events to be recorded without revenue attribution, rendering your entire ecommerce reporting unreliable.

This GA4 ecommerce validator lets you paste your ecommerce event object and check it against Google's official schema before it ever touches your live website. Catch field-type mismatches, missing required parameters, and structural errors in seconds rather than discovering broken revenue data weeks after launch.

Required Fields for Each GA4 Ecommerce Event

GA4 has strict requirements for each ecommerce event type. Getting these wrong is the number one cause of zero-revenue reporting despite confirmed purchases:

• purchase — Required: transaction_id (string), currency (ISO 4217 code), value (number). Items array required with at least item_id or item_name per item.
• add_to_cart / remove_from_cart — Required: currency, value, items array. Each item needs item_id or item_name, price (number), quantity (integer).
• view_item / view_item_list — Required: items array. currency and value are recommended. item_list_id and item_list_name for list events.
• begin_checkout — Required: currency, value, items. Recommended: coupon for discount tracking.

Common GA4 Ecommerce Validation Errors

The errors we see most frequently in GA4 ecommerce implementations: value as a string ("99.99" instead of 99.99) — GA4 requires numeric values for revenue fields; currency as a symbol ("$" or "dollar" instead of "USD") — GA4 only accepts ISO 4217 three-letter codes; missing items array — the purchase event technically fires without items, but product-level reports in GA4 will be empty; transaction_id as an integer — should always be a string to prevent floating-point precision issues; and forgetting to push ecommerce: null before each new event, which causes previous event's product data to bleed into the next push.

GA4 Ecommerce and Google Ads Conversion Import

When GA4 ecommerce is set up correctly and linked to Google Ads, your purchase events automatically import into Google Ads as conversion actions — complete with accurate revenue values. This revenue data feeds directly into Target ROAS bidding strategies, making your campaigns significantly smarter over time. A single validation error in your ecommerce setup — like sending value: 0 or omitting the currency parameter — causes all your Google Ads conversion values to show as zero, breaking ROAS bidding and making campaign performance reporting meaningless. Validate before you implement, not after.