You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: help/analyze/analysis-workspace/visualizations/histogram.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -64,7 +64,7 @@ As part of the visualization, specific histogram settings are available.
64
64
|**[!UICONTROL Starting bucket]**| Determines which bucket the histogram starts with. "1" is the default. You can set starting numbers from 0 to infinity (no negative numbers). |
65
65
|**[!UICONTROL Metric buckets]**| Lets you increase/decrease the number of data ranges (buckets.) The maximum number of buckets is 50. |
66
66
|**[!UICONTROL Metric bucket size]**| Lets you set the size of each bucket. For example, you can change the bucket size from 1 page view to 2 page views. |
67
-
|**[!UICONTROL Counting method]**| Select from **[!UICONTROL Person]**, **[!UICONTROL Session]**, or **[!UICONTROL Event]**. For example, page views per session, or page views per person, or page views per event. |
67
+
|**[!UICONTROL Counting method]**| Select from **[!UICONTROL Person]**, **[!UICONTROL Session]**, **[!UICONTROL Event]**, or **[!UICONTROL Products]** (for [sub-hit analysis](/help/components/segmentation/sub-hit.md)). For example, page views per session, or page views per person, page views per event, or page view per product. |
68
68
69
69
<!--Russ or Meike - Check Hit Type link above. -->
Copy file name to clipboardExpand all lines: help/components/segmentation/segmentation-workflow/seg-build.md
+8-3Lines changed: 8 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -86,7 +86,7 @@ You use the Definition builder to construct your segment definition. In that con
86
86
You can configure the type and scope of your definition:
87
87
88
88
1. To specify the type of your definition, specify whether you want the build an include or exclude definition. Select **[!UICONTROL Options]** and from the drop-down menu **[!UICONTROL Include]** or **[!UICONTROL Exclude]**.
89
-
1. To specify the scope of your definition, select from the **[!UICONTROL Include]** or **[!UICONTROL Exclude]** drop-down menu whether you want the scope of the definition to be **[!UICONTROL Hits]**, **[!UICONTROL Visits]**, or **[!UICONTROL Visitors]**.
89
+
1. To specify the scope of your definition, select from the **[!UICONTROL Include]** or **[!UICONTROL Exclude]** drop-down menu whether you want the scope of the definition to be **[!UICONTROL Hits]**, **[!UICONTROL Visits]**, **[!UICONTROL Visitors]**or **[!UICONTROL Products]**. You use **[!UICONTROL Products]** for [sub-hit analysis](/help/components/segmentation/sub-hit.md) use cases.
90
90
91
91
You can always change these settings later.
92
92
@@ -98,7 +98,9 @@ A vital part of the construction of your segment definition is using dimensions,
98
98
99
99
To add a component:
100
100
101
-
1. Drag and drop a component from the components panel onto **[!UICONTROL Drag and drop Metric(s), Segment(s), and/or Dimensions here]**. You can use the  in the components bar to search for specific components.
101
+
1. Drag and drop a component from the components panel onto **[!UICONTROL Drag and drop Metric(s), Segment(s), and/or Dimensions here]**.
102
+
* You can use  in the components bar to search for specific components.
103
+
* You can use  in the components bar to filter on **[!UICONTROL Approved]**, **[!UICONTROL Favorites]**, **[!UICONTROL Dimensions]**, **[!UICONTROL Metrics]**, **[!UICONTROL Segments]**, **[!UICONTROL Date ranges]**, and **[!UICONTROL Products]** components. You can also filter on  tags.
102
104
1. Specify details for the component. For example, select a value from **[!UICONTROL Select value]**. Or enter a value. What and how you can specify one or more values depends on the component and the operator.
103
105
1. Optionally modify the default operator. For example, from **[!UICONTROL equals]** to **[!UICONTROL equals any of]**. See [Operators](../seg-reference/seg-operators.md) for a detailed overview of the available operators.
104
106
@@ -123,7 +125,7 @@ You can group multiple components in one or more containers and define logic wit
123
125
* To add another component to the container, drag and drop a component from the component panel into the container. Use the blue insertion line as a guide.
124
126
* To add another component outside of the container, drag and drop a component from the component panel outside of the container, but inside the main definition container. User the blue insertion line as a guide.
125
127
* To modify the logic between components in a container, between containers or between a container and a component, select the appropriate **[!UICONTROL And]**, **[!UICONTROL Or]**, **[!UICONTROL Then]**. When you select **[!UICONTROL Then]**, you turn the segment into a sequential segment. See [Create sequential segment](seg-sequential-build.md) for more information.
126
-
* To switch the container level, select **[!UICONTROL Hits]**, **[!UICONTROL Visits]** or **[!UICONTROL Visitors]**.
128
+
* To switch the container level, select **[!UICONTROL Hits]**, **[!UICONTROL Visits]**, **[!UICONTROL Visitors]**, or **[!UICONTROL Products]**.
127
129
128
130
You can use  in a container for the following actions:
129
131
@@ -135,6 +137,9 @@ You can use  in a container for the fo
135
137
|**[!UICONTROL Name container]**| Rename the container from its default description. Type a name in the text field. If you provide no input, the default description is used. |
136
138
|**[!UICONTROL Delete container]**| Delete the container from the definition. |
137
139
140
+
When you drag a product dimension or metric into the Segment builder, the system automatically selects the **[!UICONTROL Product]** container and does not use the default **[!UICONTROL Hit]** container. This behavior keeps the segment scoped to individual products rather than to the entire hit.
141
+
142
+
When you drag both product-level and hit-level components into a single segment rule, the system uses the **[!UICONTROL Hit]** container, which is the highest (least granular) shared container. If all components that are part of a segment rule are product-level, the **[!UICONTROL Products]** container is used.
Copy file name to clipboardExpand all lines: help/components/segmentation/segmentation-workflow/seg-quick.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -96,9 +96,9 @@ The header area determines the name, type and scope of the quick segment. It als
96
96
| Element | Description |
97
97
|---|---|
98
98
|**[!UICONTROL Name]**| The name is automatically derived from the quick segment definition. |
99
-
|**[!UICONTROL People]** <br/>| Preview visual of the data resulting from the quick segment. A bar and percentage provide insight in how much of the overall data is part of the result of the quick segment. A  signals that the quick segment does not return data. |
99
+
|**[!UICONTROL _Metric_]** <br/>| Preview visual of the metrics data resulting from the quick segment. A bar and percentage provide insight in how much of the overall data is part of the result of the quick segment. A  signals that the quick segment does not return data. |
100
100
|**[!UICONTROL Include]**<br/>**[!UICONTROL Exclude]**| Select from the drop-down  whether you want to include or exclude the results of the quick segment from the data in the panel. |
101
-
|**[!UICONTROL Event]**<br/>**[!UICONTROL Session]**<br/>**[!UICONTROL Person]**| Select from the drop-down menu  the scope of the quick segment. |
101
+
|**[!UICONTROL Event]**<br/>**[!UICONTROL Session]**<br/>**[!UICONTROL Person]**<br/>**[!UICONTROL Products]**| Select from the drop-down menu  the scope of the quick segment. Use **[!UICONTROL Products]** for [sub-hit analysis](/help/components/segmentation/sub-hit.md) use cases.<ul><li>When you drag a product dimension or product metric into the Quick segment panel, the system automatically selects the **[!UICONTROL Products]** container and does not use the default **[!UICONTROL Hit]** container. This behavior keeps the segment scoped to individual products rather than to the entire hit.</li><li>When you drag both product-level and hit-level components into a single segment rule, the system uses the **[!UICONTROL Hit]** container, which is the highest (least granular) shared container. If all components that are part of a segment rule are product-level, the **[!UICONTROL Products]** container is used.</li></ul>|
Copy file name to clipboardExpand all lines: help/components/segmentation/sub-hit.md
+5-32Lines changed: 5 additions & 32 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,6 @@
2
2
title: Sub-Hit Analysis
3
3
description: Learn how sub-hit analysis lets you filter individual products within a hit in Adobe Analytics, eliminating attribution bleed in product reports.
4
4
feature: Segmentation
5
-
hide: true
6
5
feature_v2:
7
6
- id: c153fd90-23e1-4614-81d3-3cc7571227f7
8
7
internal-label: Analysis Workspace
@@ -12,11 +11,15 @@ subfeature_v2:
12
11
---
13
12
# Sub-hit analysis
14
13
14
+
{{release-limited-testing}}
15
+
15
16
Sub-hit analysis lets you analyze product data at a level more granular than the hit level. Instead of filtering on entire hits, you can segment on individual products within hits. For example, segmenting on a specific product category without including all other products purchased in the same order.
16
17
18
+
In Adobe Analytics sub-hit analysis applies specifically to the **[!UICONTROL Products]** variable. The **[!UICONTROL Products]** variable is the only multi-value object in Adobe Analytics that supports sub-hit analysis.
19
+
17
20
In Adobe Analytics, the [Products variable](/help/components/dimensions/product.md) can capture multiple products on a single hit. Without sub-hit analysis, segmenting on a product attribute returns all hits where any product within a hit matches the product attribute. The result is incorrect attribution and inflated revenue metrics. Sub-hit analysis scopes the filter to individual product rows within a hit and solves these issues.
18
21
19
-
In sub-hit analysis exclude logic behaves differently from standard hit-level exclusion against the Products variable. When you exclude product attributes within the [!UICONTROL Product] container, the segment returns hits that **have products** but don't match your exclusion criteria. The segment does not return hits with no products at all.
22
+
In sub-hit analysis exclude logic behaves differently from standard hit-level exclusion against the Products variable. When you exclude product attributes within the [!UICONTROL Products] container, the segment returns hits that **have products** but don't match your exclusion criteria. The segment does not return hits with no products at all.
20
23
21
24
## Example
22
25
@@ -53,33 +56,3 @@ In the segmentation builder or as part of a **[!UICONTROL Quick segment]**, you
53
56
To exclude at the product level, hits that contain at least one product are included, then the exclusion on sub-hit level is applied within that scope. This exclusion differs from hit-level exclusion, which excludes the entire hit.
54
57
55
58
>[!ENDTABS]
56
-
57
-
In Adobe Analytics sub-hit analysis applies specifically to the **[!UICONTROL Products]** variable. The **[!UICONTROL Products]** variable is the only multi-value object in Adobe Analytics that supports sub-hit analysis.
58
-
59
-
60
-
>[!WARNING]
61
-
>
62
-
>The following sections are going to be moved to their relevant articles (on Segment builder, Quick segment, Histogram, and more) when this feature releases. And these articles will then refer to this article for reference on what sub-hit analysis is. This action is currently not done so as not to confuse customers while the feature is unavailable.
63
-
64
-
## Container auto-inference
65
-
66
-
When you drag a product dimension or metric into the Segment Builder or Quick segment panel, the system automatically selects the **[!UICONTROL Product]** container and does not use the default **[!UICONTROL Hit]** container. This behavior keeps the segment scoped to individual products rather than to the entire hit.
67
-
68
-
## Mixed container behavior
69
-
70
-
If you drag both product-level and hit-level components into a single segment rule, the system uses the **[!UICONTROL Hit]** container, which is the highest (least granular) shared container. If all components that are part of a segment rule are product-level, the **[!UICONTROL Product]** container is used.
71
-
72
-
## Product filters in the left rail
73
-
74
-
The Segment Builder includes a new filter option in the left rail to display only product dimensions and metrics. This makes it easier to find product-level components when building sub-hit segments.
75
-
76
-
>[!NOTE]
77
-
>
78
-
>This filter option is available in the Segment Builder only. It is not available in other left rails such as Analysis Workspace panels or visualizations.
79
-
80
-
## Histogram visualization
81
-
82
-
The Histogram visualization includes a new sub-hit container drop-down menu. This lets you bucket metric values at the product level. For example, counting product occurrences per order rather than per hit.
83
-
84
-
The Histogram is the only visualization that requires a sub-hit container selection. All other panels and visualizations work with sub-hit analysis data without additional configuration.
0 commit comments