Planning GA4 E-commerce Events Before Implementation

E-commerce tracking usually goes wrong before anyone touches GTM. Someone sends a developer a list of GA4 event names, the developer builds them, and months later nobody can explain why revenue differs from the order system or why two versions of a product appear as separate items. The fixes are cheap at the planning stage and expensive after launch, because data already collected stays as it was.

Start with the decisions, not the event list

Google's e-commerce guide describes a long list of events, from product lists through to promotions. You do not need all of them on day one. Each event costs development and testing time, so ask what each one would change:

• Which products earn the most, and through which channels? This needs purchase with good item data.
• Where do people leave the checkout? This needs begin_checkout, add_shipping_info and add_payment_info.
• Do people who see a product add it to the cart? This needs view_item and add_to_cart.
• Do category lists and recommendations help? This needs view_item_list and select_item, which can be heavier to build.
• Do on-site banners lead to sales? This needs the promotion events, which matter only if somebody actually manages those banners.

A sensible first release for a small shop is often the second to fourth lines above, plus purchase. Add the rest once someone has a question that needs them.