It is a good idea to track a few meaningful micro goals alongside your primary macro goal.
For an ecommerce store, the primary macro goal is usually a purchase. That is the final action you want users to complete. However, purchases are not the only actions worth measuring. Before buying, users may view a product, add it to the cart, begin checkout, use site search, sign up for a discount, or interact with other important parts of the shopping journey.
These smaller actions are often called micro goals. They do not carry the same value as a purchase, but they help you understand whether users are moving in the right direction.
For example, an add-to-cart event is not a transaction but is still a strong signal of buying intent. In many cases, increasing qualified add-to-cart actions may improve purchases if the rest of the checkout journey works properly.
This is why add-to-cart tracking can be useful for ecommerce businesses. It helps you answer questions such as:
-
Which campaigns are driving users who are interested enough to add products to their carts?
-
Are some campaigns generating traffic that browses but does not engage with products?
-
Are smaller campaigns producing better-quality traffic than larger campaigns?
-
Should we investigate a campaign that drives many sessions but very few add-to-cart events?
-
Should we increase spend on campaigns that consistently generate strong shopping intent?
If you know that one campaign drives a higher share of add-to-cart events than others, you may decide to prioritize it, review its targeting, increase budget, or use it as a model for other campaigns.
Before we look at the report, there is one important requirement: the add_to_cart event must actually be tracked in Google Analytics 4.
GA4 does not magically know that someone added a product to the cart unless your ecommerce platform, website, or tracking setup sends that event to GA4. Some platforms and ecommerce integrations send these events automatically, but others require manual configuration through Google Tag Manager, a data layer, a platform plugin, or custom code.
Before relying on this report, make sure the add_to_cart event fires correctly when a product is added to the cart. You can confirm this in DebugView, Realtime reports, or by testing the action with your browser’s developer tools and GTM Preview mode if GTM is used.
Once you know that add_to_cart is being collected correctly, you can use GA4 to see which campaigns are generating those events.
There are two main places where you can look for this data: standard reports and Explorations.
Explorations give you more flexibility, but for this article we will use the standard reports because they provide enough information to start drawing useful conclusions.
In standard reports, go to Traffic acquisition:
The Traffic acquisition report shows where sessions came from. This differs from the User acquisition report, which focuses on where users first came from. For campaign performance analysis, Traffic acquisition is usually the better place to start because it lets you analyze campaigns that drove sessions during the selected date range.
By default, the primary dimension is often Session default channel group:
This is useful to compare broad channels like Organic Search, Paid Search, Organic Social, Email, Direct, and so on.
If you want to compare individual campaigns, you need to change the primary dimension.
Click the primary dimension dropdown and select Session campaign:
Once you select Session campaign, the table will update to show campaign names instead of channel groups.
Next, we need to look at the right metric.
The metric we are interested in is Event count:
By default, Event count includes all events. That means it may include page_view, scroll, click, user_engagement, add_to_cart, purchase, and many other events collected by the property.
That is not what we want here. We only want to look at add-to-cart events.
To narrow the metric down, click the dropdown/triangle next to Event count and select the event name you are interested in. In this case, select add_to_cart:
Once selected, Google Analytics will update the table to show the number of add_to_cart events generated by each session campaign during the selected date range.
You can now start reviewing which campaigns generate the most add-to-cart activity.
However, be careful not to only look at the total number of add_to_cart events.
A campaign with the highest number of add-to-cart events is not automatically the best. It may simply have the most traffic. A large campaign can generate more total add-to-cart events because it has a much larger volume of sessions.
That is why another very important column in this table is Events per session:
Events per session helps you understand how many selected events are happening on average per session. In this case, after filtering Event count to add_to_cart, it can help you compare campaigns based on add-to-cart activity relative to traffic volume.
For example, one campaign may generate 611 add_to_cart events, while another generates only 120. At first glance, the campaign with 611 events looks better.
But if the first campaign had 10,000 sessions and the second campaign had only 500 sessions, the second campaign may actually be producing stronger add-to-cart engagement relative to its traffic volume.
That does not mean you should immediately pause the bigger campaign or move all budget to the smaller one. It simply means you should look deeper before making a decision.
A good way to review this table is to compare both:
-
Total add_to_cart events
-
Events per session
The total number of add_to_cart events helps you understand volume.
Events per session helps you understand efficiency or engagement relative to traffic.
Together, these metrics give you a better picture than either one alone.
For example:
-
A campaign with many sessions, many add_to_cart events, and strong events per session is likely performing well.
-
A campaign with many sessions but very few add_to_cart events may be driving low-intent traffic.
-
A campaign with fewer sessions but strong events per session may deserve more attention or additional budget.
-
A campaign with strong add_to_cart numbers but weak purchase performance may indicate a checkout, pricing, shipping, or trust issue rather than a campaign issue.
It is important to remember that add_to_cart is still a micro goal. It should not replace purchase data. A campaign that generates many add-to-cart events but very few purchases may not be as valuable as it first appears.
For that reason, it is best to use add-to-cart data alongside other ecommerce metrics, such as purchases, revenue, checkout starts, conversion rate, and average order value.
Still, add_to_cart can be a very useful signal, especially when you do not yet have enough purchase volume to make confident decisions. It can help you identify campaigns that are driving meaningful product interest earlier in the customer journey.
In short, this report can help you find campaigns that are not just bringing traffic, but bringing users who are actively engaging with your products.
This gives you a quick and practical way to evaluate which campaigns are contributing to shopping intent in Google Analytics 4.
