GA4 Ecommerce Tracking Setup (2026): Purchase Events and Key Events

What does GA4 ecommerce tracking actually involve?

In short: sending each shopping step to GA4 under a standard event name, together with an items array that describes the products. Once that structure is in place, revenue, transactions and item-level performance show up in reports without extra configuration.

A working setup has five layers, and each one depends on the previous:

1. Data layer Your store (Shopify, WooCommerce, BigCommerce or a custom build) writes product and order data to the dataLayer at every step.
2. Tagging Google Tag Manager (GTM) reads that data and sends it to GA4 as events.
3. Testing You check every event and parameter in DebugView.
4. Key event You confirm purchase is marked as a key event.
5. Import You link GA4 to Google Ads and create a Google Ads conversion from the key event.

Many older guides still tell you to click "Mark as conversion". The interface has changed; the menu names below match the English GA4 interface as of September 2026.

Which ecommerce events should I track in GA4?

Use Google's recommended event names exactly as documented. Google's ecommerce documentation is built around these exact names, and the built-in ecommerce reports read from them; custom event names leave those reports empty.

If developer time is tight, start with four events: view_item, add_to_cart, begin_checkout and purchase. That is enough to see where your funnel leaks. Our ad performance KPI guide covers which ratios to watch once the data is flowing.

What parameters does the GA4 purchase event need?

Four fields matter most: transaction_id, value, currency and items. Google's developer docs say that when you send value, you must set currency at the event level, and the items array can hold up to 200 elements.

• transaction_id: Your order number. It must be unique per order and should never contain personal data such as an email address.
• value: The sum of price × quantity for the items. Send shipping and tax in the separate shipping and tax fields so your revenue definition stays consistent.
• currency: An ISO 4217 code such as USD, GBP or EUR. On multi-currency stores, send the currency the order was actually paid in instead of hard-coding one.
• items: Each product needs at least item_id or item_name, ideally with price, quantity, item_brand, item_category and item_variant.

How do I set up GA4 ecommerce with GTM and the dataLayer?

Your site pushes an event name and an ecommerce object to the dataLayer at each step, and a GA4 Event tag in GTM forwards it to GA4. Google's official examples clear the previous ecommerce object before every push.

Example for the order confirmation page (values are illustrative):

dataLayer.push({ ecommerce: null }); // clear the previous ecommerce object
dataLayer.push({
  event: 'purchase',
  ecommerce: {
    transaction_id: 'ORD-100245',
    value: 118.00,
    tax: 9.44,
    shipping: 6.95,
    currency: 'USD',
    coupon: 'FALL10',
    items: [{
      item_id: 'SKU-3321',
      item_name: 'Cotton Oversized Tee',
      item_brand: 'Example Brand',
      item_category: 'Apparel',
      item_variant: 'Black / M',
      price: 59.00,
      quantity: 2
    }]
  }
});

In GTM:

1. Under Triggers, create a Custom Event trigger with the event name purchase.
2. Create a Google Analytics: GA4 Event tag, enter your measurement ID and set the event name to purchase.
3. In the tag's more settings, check Send Ecommerce data and choose Data Layer as the data source.
4. Repeat for view_item, add_to_cart and begin_checkout. With many events, you can use one tag with the {{Event}} variable as the event name and a trigger that matches all ecommerce event names.

How do duplicate transaction IDs inflate GA4 revenue?

GA4 deduplicates purchase events that arrive with the same transaction_id on a web stream, so a reloaded thank-you page won't count twice if the ID is correct. Problems start when the ID is empty, hard-coded or regenerated on every page load.

Three rules from Google's help center matter here:

• Send a unique, dynamic ID for every order, and never reuse the same ID across different users.
• Never send an empty string (transaction_id: ""). GA4 treats all purchases with an empty ID as duplicates of each other, so your orders undercount.
• Deduplication works only for web streams, not app streams.

A worked example: a store takes 1,000 orders a month at an $85 average order value, and 8% of customers reload the confirmation page. If the ID is regenerated on each load, that creates 80 phantom purchases and GA4 reports $91,800 instead of $85,000. If the ID is empty, the opposite happens: all 1,000 orders collapse into one. Either way, your ROAS is wrong.

Rather than leaning on deduplication alone, fire purchase only on the first view of the confirmation page, for example by storing the order number in a cookie or sessionStorage and skipping the tag on reload. If GA4 and your store admin still disagree on order counts, we break down the usual causes in why Shopify, Meta and GA4 numbers don't match.

What is a key event in GA4, and how do I mark purchase as one?

A key event is an event you treat as important for your business; it is what GA4 used to call a conversion. The word "conversion" now belongs to Google Ads, where imported key events become conversion actions.

GA4 marks purchase as a key event by default, so in most properties you only need to confirm it:

1. Go to Admin, and under Data display click Events.
2. On the Recent events tab, find purchase. It shows up once the first purchase has been received.
3. Check that the star next to it is filled. If someone unmarked it, click the star to mark it as a key event again.

Google notes it can take up to 24 hours for a newly marked key event to appear in standard reports. Resist marking every step as a key event: you already see add_to_cart and friends in the ecommerce reports, and a crowded key event list muddies both reporting and the Google Ads import. The same help page says that enabling ads personalization with a linked Google Ads account also marks some events, such as add_to_cart, begin_checkout and view_item, as key events, so review the list after linking. For where micro-steps fit in the bigger picture, see our article on customer journey mapping.

How do I test GA4 ecommerce events with DebugView?

Turn on debug mode, walk through a real purchase from product page to confirmation, and inspect each event and its parameters in Admin › Data display › DebugView. Sessions opened through GTM Preview or Tag Assistant count as debug sessions.

DebugView has three panes: the middle seconds stream shows the last 60 seconds of events, the left minutes stream covers the last 30 minutes, and the right column lists top events and current user properties. If several devices are in debug mode, pick yours from the device selector at the top.

• Do view_item, add_to_cart and begin_checkout arrive in order?
• Does purchase carry transaction_id, value and currency, and is value a plain number?
• Do the items show the right ID, price and quantity?
• Does reloading the thank-you page send a second purchase?
• Do coupon and shipping arrive in their own fields?
• Do tags behave as expected when a visitor declines cookies?

DebugView also won't show events blocked by consent settings. If your consent banner isn't wired up correctly, GA4 may receive little data or only modeled data; our Consent Mode v2 guide covers that side.

How do I link GA4 to Google Ads and import key events?

First link the accounts under Admin › Product links › Google Ads links, then go to Advertising › Conversion management in GA4, click New conversion and create a Google Ads conversion from your purchase key event.

The classic mistake is double counting. If a purchase conversion measured by the Google Ads tag is already primary and you also make the GA4 purchase primary, Smart Bidding sees the same order twice. Decide which one stays primary and keep the other secondary.

GA4 also asks, in its attribution settings, which channels can receive credit for key events exported to Google Ads: Google paid channels only, or paid and organic channels. That choice, plus the different attribution logic in each tool, explains most gaps between Google Ads and the "google / cpc" row in GA4. If you want to see those gaps side by side with Meta and your store data, Marpany's conversion analysis view lines the sources up in one table.

What are the most common GA4 ecommerce tracking mistakes?

Most bugs come from the values written to the data layer, not from the tags themselves. Use this table to go from symptom to cause quickly.

Don't forget refunds. Send a refund event with the original transaction_id and include the refunded products in the items array; Google recommends item data in refund events so item-level refund metrics show up. For a partial refund, list only the items that came back. Skipping this in high-return categories overstates the net revenue your ads bring in and pushes budget decisions the wrong way.

What should I check in the first week after setup?

Compare GA4 against your store admin and close the gap to an acceptable range; the setup isn't finished until that check passes.

1. Day 1 Place a test order in DebugView, then refund it to test the refund event.
2. Days 2–3 Confirm the Ecommerce purchases and Monetization overview reports are filling up.
3. Days 4–5 Compare GA4 transactions with your store's order count; if they diverge a lot, revisit transaction_id and consent settings.
4. Days 6–7 In Google Ads, check the imported conversion's status and its primary or secondary setting.

With these checks done, your measurement rests on solid ground and Google Ads' automated bidding finally learns from the right signal.