Try-On Analytics: Which Events to Track in GA4

To track virtual try-on in GA4, send a small set of custom events that follow the shopper from seeing the try-on button to adding the product to cart. Five events cover most questions: button seen, try-on started, result viewed, size found and add to cart after try-on.

This guide assumes you already run a virtual fitting room on your clothing website and want to measure how shoppers use it. The event names below are suggestions. You choose them, and you wire them up yourself in your own tag setup.

Why do you need custom events for try-on?

GA4 collects some events automatically, but a try-on button is specific to your store. Google's guidance is to check first whether an automatically collected or recommended event already fits, and to create a custom event only when none does, as described in Google's custom events help page.

A try-on interaction usually doesn't match a standard event. So you define your own.

Which events should you track?

Start with these five. Keep names short, lowercase and consistent.

Event name	When it fires	Question it answers
tryon_button_view	The try-on button scrolls into view	How many shoppers could use it?
tryon_start	The shopper taps the button	How many choose to try it?
tryon_result_view	A result is shown	How many finish?
tryon_size_found	A size suggestion is shown	Does sizing help?
tryon_add_to_cart	Add to cart after a try-on in the same visit	Does try-on lead to carts?

These names are examples for planning. They are not events sent by ZeDaq.ai, and nothing on this list is built in. You create the triggers on your own site.

What parameters should each event carry?

Parameters add detail to an event. Google describes them as key-value pairs, where the name stays the same and the value changes with each interaction, in its custom events documentation.

Useful parameters for try-on:

• product_id or item_id, so you can compare products
• garment_type, such as tops, dresses or bottoms
• page_type, such as product page or collection page

Avoid putting personal data in parameters. Never send a shopper's photo, name or body measurements to analytics.

How do you send the events?

You can send custom events with gtag.js or Google Tag Manager. The gtag syntax is gtag('event', '<event_name>', { <event_parameters> }), and Google says to place events below the Google tag snippet, per its developer documentation on events.

A simple route for a store owner:

1. In Tag Manager, create a click trigger for your try-on button.
2. Create a GA4 event tag named tryon_start that uses that trigger.
3. Repeat for each event in the table.
4. Open the preview mode and click through a product page to confirm each event fires once.

For events that happen inside the try-on window, ask your developer to confirm which page events you can listen to on your setup. Don't assume an event exists until you see it fire.

How do you read the results?

Build a simple funnel: button seen, try-on started, result viewed, add to cart. Watch where shoppers drop off.

• Many views, few starts: the button is hard to notice or the label is unclear.
• Many starts, few results: shoppers hit friction, such as photo upload.
• Results but no carts: check price, stock and your size guide.

To see parameter values in reports, Google says you need to register a custom dimension for each parameter, per the custom events help page.

Link the results back to your product pages. The guide to which products to try on first helps you decide where to compare. Stores with used stock can also read about vintage and secondhand try-on.

Analytics only shows behavior. To tackle fit questions, pair it with better sizing content, starting with size guides that reduce returns.

What naming rules should you follow?

Google says an event name should describe what you intend to measure, is case sensitive, can't be a reserved name and must start with a letter, per its custom events help page. Pick a pattern, such as a tryon_ prefix, and use it for every event.

Write the plan in a shared sheet with the event name, trigger and parameters. When you change the setup later, you will know what each event means.

FAQs

Do I need Google Tag Manager?

No. You can send events with gtag.js directly. Tag Manager is often easier because you can add events without editing theme code.

Can I mark a try-on event as a key event?

Google says you can mark any custom event as a key event, per its custom events help page. Choose the event that best represents value, such as a try-on followed by add to cart.

Should I track shoppers' photos or measurements?

No. Keep analytics free of photos and body data. Track only that an action happened and which product it was on.

How do I test my events?

Use GA4 DebugView or the Realtime report to watch events arrive while you click through the page. Google's recommended events page mentions both.