New Sub-Hit Segment Container

[#1]

We sell multiple product categories on our site.  For example: Toys, Baby, Grocery.  A user may place an order that has a product from each category.  For example:

Order Revenue = 500

Toys = 100

Baby = 300

Grocery = 100

If want to see Revenue by Category, I would run a product report against our revenue metric.  Lets say I wanted to create a calculated metric for 'Grocery Revenue'.  My most granular option is this:

Segment Container: Hit

Segment Variable: Products  = Grocery

Metric = Revenue

The problem with this is that the 'hit' container would include all revenue in this order.  So the value would be 500 instead of 100 (unless I broke it down by products).  It would be great to add an additional container that would allow us to 'filter' on the variable in the container depending on the report I am viewing.  This would give us (Visitor, Visit, Hit, Filter) containers and would increase flexibility when creating reports/dashboards etc.

Let me know your thoughts.

Thanks!

[#2]

I'd recommend looking into merchandising eVars!

Merchandising Variables

[#3]

hello sir!  thanks for suggestion.  We absolutely leverage merch evars and i might be unaware of the use case you are implying.

Are you saying that merch eVar 'hit' level segments would only return the products assigned with a given merch evar value?  For example:

In Hit 1, I have:

s.products = ;cats;;;;eVar1=big

s.products = ;dogs;;;;eVar1=small

If I create a hit level segment defined as "hits where eVar1=small", would that segment return only "dogs" or would it return both "cats" and dogs" because it was on the same hit?  If its the former, then that is a "sort of" solves my issue.  It is less elegant as it would require more implementation and another eVar.

Thanks again!

[#4]

Ah gotcha - a segment would include both dogs and cats, a breakdown of "small" by product would only give you "dogs" though. Sub-hit segmentation is a common feature request - I'll pass this along to the team.

[#5]

Duplicated by Segmentation - New Segment Container  and Add a Product Container to the Segment Builder  adding 17 votes here.

[#6]

I haven't checked but I think list vars suffer in a similar way.  If they do they should be considered along aside this.

[#7]

Needed

[#8]

This is an absolute must-have for any ecommerce client, and Adobe boasts itself with E-Commerce.

Why?

1. It totally confuses people that dragging the Product Category "Sports" onto a table is not the same as having it on top for the whole panel in the Segment bar.

2. It makes a looot of flexible reporting very tedious. People have multiple products, categories, brands etc. in their basket. Example: This is an example of a category Level 1/ Level 2 / Brand Dashboard where people can quickly switch to another category/brand to see that category's/brand's performance (or a combination of both).

That dashboard is almost useless without this feature, because filtering e.g. for Category Level 1 = "Sport & Freizeit" and Brand = "Fjällräven" will show revenue numbers etc., but people buy from multiple categories (on average 1.6 Distinct product categories per order in our case).

If I really want to see ONLY revenue generated by that category and brand, I have to go into each visualization and add a dimensional filter on top.

But noone is going to do that.

3. It would scale things so massively, I would be suuuuuper excited if Adobe finally offered Sub-Hits!!

4. It would be another strong differentiator to Google Analytics.

[#9]

Any update here? This is still an absolute Must-Have. 

[#10]

@trevorpaulsen Do you think this will be implemented any time soon? It is also a big issue in the new mobile app where we can only apply hit-based segments. My ecommerce clients would love to use the app, but they say it is no use when they cannot focus on sales in their assortment categories only. 

[#11]

Hi @luekl - unfortunately, this is not currently on our near term roadmap. That said, it is something we're researching for the future. Thanks for your feedback.