Betreff: 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]

@jen_lasser 

I'm in agreement with @luekl.  I was having a discussion with my manager just the other day, and I currently can't even run a simple eComm report to view of the units from a specific subset of products in my orders from December.

I can create a segment to see the orders using the products, but if I try to see the units, I get ALL of the units from the orders, no matter what, because you can't create a segment at the sub-hit level.

Until this is done, any and all analysis has to happen outside of AA and I'm dead in the water.

[#3]

No need to @ Eric and I on this idea. It is on the backlog and the PM that owns the project & prioritization is following this thread. They will share updates when they become available. Thanks!

[#4]

Superb!  Looking forward to hearing about it in the near future.  Thanks again!

[#5]

Thanks, but this is now 2 1/2 years old, and being "in the backlog" means basically nothing but that is is in some big list of potential features for the future... 

[#6]

Please!!!!

[#7]

@luekl You seem to have the same timing as I do.

Just today, I again had a product manager come to me and verify that we could not get the # of units for a specific product or the avg # of units for a specific product in an eComm order, and I had to tell them, "yes, that is correct."

Why?  Because Adobe Analytics doesn't provide the ability to segment Orders at the sub-hit level.

Yes, I know that's crazy.

Yes, I know that should be a fundamental capability to understand Order details.

When will it be available?  I have no idea.  It's been on their backlog since November 2020 to get it done.

Yes, I understand backlogs are where deprioritized tasks go to die.  Let's hope this isn't one of them.

[#8]

Please!!

At least for Products. 

Most retailers are product centric, not hit centric. Adobe is ONLY hit centric. This immediately makes communication with business stakeholders difficult. We are often unable to answer their leading questions that are product centric. Cross selling analysis is not good due to this.

[#9]

Given the focus on making AEP a sellable product, I don't expect Sub-Hit segments to come anytime soon as it has been requested for years now (this thread alone is from 2018), and Adobe has not given E-Commerce use cases much consideration in their recents features which all do not support sub-hits.

But what could be a good compromise would be to take functionality that is already there and make it a bit less tedious for end users: make drop-zone work like dimensional value filters if you drag a dimensional value into the drop zone. Because they look as if they WERE dimensional value filters (yellow), but they are actually hit segments which - again - keeps confusing my users every day. 

"Hi Lukas, I have been trying this now for at least an hour, reloaded etc., but I don't see the error. Why is this

not the same as this? I am just removing the duplicate filter after all!"

Thank you for your understanding.

[#10]

Sorry to insist, but this problem does not go away and people keep running into this all the time. 

This is also something that is important for AEP Workspaces, so please:

Can we at least get less misleading color codes in the dropzone?

- Segments should be blue always

- Dimensional Value Filters should be yellow always (but in the drop zone there are no dimensional value filters, everything is a Hit Segment or a Date Range, so please make it blue and not yellow or green when that color means sth different in a table)

- Metrics green

- Date Ranges purple

Why does the drop zone need to break this code?