Ecommerce Data Layer Generator

The Complete GA4 Ecommerce Data Layer: What You Need to Know

The GA4 ecommerce data layer is a standardised JavaScript object pushed to window.dataLayer before GTM fires any ecommerce tags. It tells GA4 (via GTM) what happened in the user's shopping journey — what products they viewed, added to cart, and purchased — along with all the financial and product metadata needed for accurate revenue attribution and Smart Bidding. This ecommerce data layer generator produces production-ready data layer code for any GA4 ecommerce event with all required and recommended fields pre-populated.

GA4 Ecommerce Events: What to Implement and When

GA4 defines eleven standard ecommerce events that map to the customer purchase journey. You don't need all eleven — implement the ones that match your funnel:

• view_item_list — fires on category pages and search results when product cards are displayed. Enables product list performance reporting.
• select_item — fires when a user clicks a product card. Links list position to eventual purchase for attribution.
• view_item — fires on the product detail page. Measures engagement and enables conversion funnel analysis from PDP to purchase.
• add_to_cart — fires when a product is added. Enables cart abandonment analysis and remarketing audience creation.
• begin_checkout — fires at checkout initiation. The critical funnel step for identifying checkout abandonment.
• purchase — the most important event. Must include transaction_id, value, currency, and the items array. This event drives all revenue reporting and Google Ads conversion attribution.

Critical Implementation Rules That Developers Frequently Miss

Even experienced developers make consistent mistakes when implementing GA4 ecommerce events. The most impactful ones to avoid:

• Always clear the ecommerce object first. Before every dataLayer.push() with an ecommerce event, push { ecommerce: null }. Without this reset, GTM may merge the previous ecommerce object with the new one, causing contaminated data — for example, items from a previous view_item event appearing in a purchase event.
• Send value as a number, not a string. The value field must be a JavaScript number (49.99), not a string ("49.99"). Strings cause GA4 to record the transaction with a value of 0 in revenue reports.
• Use ISO 4217 currency codes. currency must be a 3-letter ISO code (USD, EUR, GBP). Strings like "dollars", "$", or "us dollar" are rejected.
• Make transaction_id unique per order. Duplicate transaction_id values cause GA4 to deduplicate purchases — the second identical transaction is silently ignored. Always use your order management system's order ID, never a session ID or timestamp.