Stop Overcounting Product Revenue: Adobe Analytics Adds a Product Level Segment Scope

Who said Adobe Analytics doesn’t get new features?! Yes at the end of July 2026, a new scope for segments has been added to the segment builder tool. Previously, users were limited to Visitor, Visit and Hit level segments. Now, we have a new Products scope – which Adobe are also referring to as “Sub Hit Analysis” (this is further reflected by Adobes “Segment Containers” documentation still omitting the Products scope, with it instead having its own documentation). So what does this mean – what are the use cases for this scope and why should we care? 

Before we get into the new feature, a quick recap of what segments are within the context of Adobe Analytics for those of you who aren’t in AA every day. Segments allow you to essentially apply filters to your AA data, isolating data that you are interested in analysing by identifying specific behaviour or attributes. These can be added within the headers of your panel in Analysis Workspace or placed on top of metrics within freeform tables you have created. These are the items within Workspace that have the blue label against them. 

Some typical segments you might put together are visitors who added to cart but did not purchase, hits on a certain landing page or users who access the site via a particular device type. Previously, within the segment builder you selected from three scopes:

• Hit: the most granular scope, basically an individual interaction on the website or app
• Visit: grouping all interactions within an individual session on the website or app
• Visitor: all interactions done by a single Experience Cloud ID (ECID)

Use of segments in your Workspace dashboards are a non negotiable – offering your end users a valuable method to drill down into the data and interactions on your site that matter the most. Segments also aren’t just isolated within Adobe Analytics Workspace – they can be used in calculated metrics, configuring alerts, or pushing to other platforms in Adobe Experience Cloud, such as Adobe Target. 

In addition to these three scopes – we now have a “Product” scope. 

What this does is it allows us to segment at the individual product level, rather than the entire hit that happens to include that item. 

Think of it this way – if we have an ecommerce site that sells clothing, and we have a product called “Men’s Socks” that we want to see how much revenue it has generated in the last 14 days. We create a hit level segment that contains that product name and combine it with our revenue metric in a table. This table will output the total amount of revenue where that product was included within an order –  brilliant. However, this revenue figure includes all revenue associated with that individual interaction (hit). This may give you an inflated revenue value for that individual product as there can be multiple items within the users cart when they convert. An order event on an ecom site is one hit, but potentially many products. With this new feature you can now ensure that your analysis into single products does not have revenue associated with other products bleeding into your data – measuring reliable true product ID or product category revenue and units within multi item interactions. 

This segment scope is entirely reliant on your “Product” variable in your Adobe Analytics tracking. So if you are storing product level information in  eVars, props or list variables, then it will not be eligible for use within this segment scope. Additionally, if you are not confident in how your ecommerce tracking has been set up in Adobe Analytics is configured in Adobe Launch, then its best not to draw any conclusions with product level segments – but definitely reach out to us if there is a lack of confidence in ecommerce tracking. 

This new scope should enable analysts to get more accurate product level analysis within the Adobe Analytics workspace – which previously would have only been possible using SQL within your data warehouse of choice. Please let us know if you have any questions on this or any other Adobe Analytics configuration questions you may have.