Key events and e-commerce tracking

0:00 Key events and e-commerce

In twenty twenty-four, Google renamed conversions in G A four to key events. It sounds like a small wording change, but it confuses agencies and clients to this day, because Google Ads still uses the word conversions. In this lecture you'll learn what key events are, how to choose them, how G A four's e-commerce events and items array work, the three rules that prevent almost every revenue problem, and how to handle markets where cash on delivery means a purchase isn't really a purchase yet.

0:37 Why it matters

Why does this matter? Because key events power conversion-focused reporting, and revenue numbers drive budget decisions. If a key event fires on the wrong trigger, conversion rates look better than reality. If a purchase fires twice, revenue inflates. If currency is missing, revenue may not record correctly. And if refunds never flow back, G A four revenue drifts higher than your real sales every month. Each of these errors ends up in a board meeting as a confident, wrong number.

1:12 Key events versus Ads conversions

Here's the distinction. A key event in G A four is an important action for analysis in your property. A conversion in Google Ads is an action configured or imported into Ads to measure and optimize campaigns. Think of key events as the goals on your team's whiteboard, and Ads conversions as the specific signals you hand to the Ads bidding system. You might import a key event into Ads as a conversion, but they're separate settings in separate products.

1:47 Choosing key events

How do you choose key events? Keep the list short: your macro conversions, plus one or two critical micro conversions. For e-commerce, purchase, and perhaps begin checkout. For lead generation, generate lead or a book appointment event. For software, sign up and purchase, not login. For publishers, a newsletter sign up or subscription. If everything is a key event, nothing is. You can also assign a default value to a key event, or send a dynamic value and currency, so reports can show key event value alongside revenue.

2:25 The e-commerce event set

Next, the e-commerce event set. A typical retail funnel runs view item list, select item, view item, add to cart, view cart, begin checkout, add shipping info, add payment info, purchase, and refund. Each carries an items array. Each item should have at least an item id or name, and ideally price, quantity, category, brand and variant. The purchase event also needs a transaction id, value and currency, and optionally tax, shipping and coupon. E-commerce reports depend on these exact names and parameters.

3:01 Three revenue rules

Here are the three rules that prevent most revenue problems. One: always send a unique transaction id. G A four uses it to deduplicate purchases, for example when a buyer reloads the confirmation page. Two: always send currency as an I S O code, like U S D, G B P, A E D, S A R or P K R. Three: agree what value includes. Tax? Shipping? Document it. Finance numbers will differ anyway, because of refunds, cancellations and refused deliveries. So define the relationship instead of hoping the numbers match.

3:41 Cash on delivery

Now cash on delivery, common in Pakistan and parts of the Gulf. An online purchase is really an order, and some are refused at the door. You have two acceptable options. Track purchase at order time, then send refund events for refused orders, using the Measurement Protocol or a data import. Or track a custom place order event, and report realized revenue from your order system. Either works if it's documented and used consistently. What doesn't work is pretending every order was paid.

4:17 Example 1: finding the leak

First example, a simple one. An electronics store sees add to cart rising but purchases flat. The funnel, with illustrative numbers: twenty thousand view item, three thousand add to cart, eighteen hundred begin checkout, fifteen hundred add shipping info, seven hundred add payment info, and five hundred sixty purchases. The steepest avoidable drop is between shipping and payment, under fifty percent. Segmenting by device shows mobile users abandon far more at payment. That points to a payment form or wallet issue, not pricing.

4:53 Example 2: Riyadh retailer

Second example, a business case. A Riyadh electronics retailer offers cash on delivery. They track purchase at order placement, then send refund events through the Measurement Protocol when couriers report refused deliveries. Every week, the analyst compares G A four revenue net of refunds with delivered revenue from the order system. The gap is documented and stable, so it becomes a known quantity rather than a monthly argument. And the team can see which channels bring customers who actually accept deliveries.

5:28 Watch me do it, part 1

Watch me write a purchase push. First, I clear the previous e-commerce object by pushing e-commerce null, so values don't leak from an earlier event. Then I push event purchase with an e-commerce object: transaction id O R D one oh four five two two, value one forty-nine as a number, not a string, currency A E D, shipping fifteen, coupon E I D ten, and an items array with one abaya: its id, name, category, price and quantity. Google Tag Manager reads this and sends the G A four event.

6:08 Watch me do it, part 2

Then I check for duplicates in the BigQuery export, which the interface quietly hides. I select the transaction id and count purchase events for September, grouped by transaction id, keeping only those with more than one event. If any rows come back, orders are being counted twice, usually from confirmation page reloads or two tags firing. On a healthy setup, this query returns nothing. I schedule it weekly, so duplicates are caught before they reach a report.

6:41 Ads in 2026

And one more twenty twenty-six consideration: Google Ads. If you import a G A four key event into Ads as a conversion for bidding, make sure the same action isn't also tracked by a separate Ads conversion tag, or you'll double count in Ads. Decide which source Ads should optimize on, and write it down. And check consent mode, because Ads measurement depends on the consent signals: ad storage, ad user data and ad personalization.

7:14 Common mistakes

Common mistakes. Missing or duplicated transaction ids, inflating revenue. Sending value as a string with a currency symbol. Firing purchase on a confirmation page that also loads for failed payments. Marking add to cart and page view as key events, diluting conversion rates. And forgetting refunds, so G A four revenue drifts ever higher than actual sales.

7:39 Recap

Recap. G A four calls important outcomes key events, while Google Ads uses conversions. Keep key events few. E-commerce reports rely on recommended events with an items array. A unique transaction id, an I S O currency and a documented definition of value are non-negotiable. Handle cash on delivery with refunds or a separate order event. And check duplicates in the export.

8:06 Try this now

Try this now. Write the full purchase push, with items, for a real or imagined order. Then list three ways that number could differ from finance's figure, like refunds, tax or refused deliveries, and write one sentence for each explaining how you'd reconcile it. If you have BigQuery export, run the duplicate check query.