Here is what you can nest in each container: Container Name You can use nesting between containers as well as between rules within a container. The remaining data is then included in the resulting report. Repeat until all nested container rules have been calculated. The nested rule does NOT apply to any hits that the first rule throws out. Apply the nested rule to the remaining data.Any data that does not match this outer rule is discarded in the segmented report. Determine what data is included using the outermost container.The following logic is used with nested containers: When creating segment containers within other containers, you are in essence creating a segment within a segment. See Logic Group examples for additional information. This can be accomplished using the Logic Group container. This type of logic requires you to break the hierarchy (as you are already have a top-level Visitor container) to filter only for selected visitors. For example, you may want to provide a container nested within the segment that filters based on Visitor. The Logic Group container allows you to provide a separate container within the segment rules to filter entities not based on hierarchy. In the case of a tracking code that expires after a week, that value could be persisting across multiple visits. If you use this container on a value that persists, such as an evar, it will pull in every hit where that value is persisting. Merchandising eVars (in context of events) Hit containers include values based single page breakdowns: You may also want to pinpoint a specific value when an action occurs, such as the marketing channel when an order was placed. It is the most narrow of the containers available to let you identify specific clicks and page view where a condition is true, letting you view a single tracking code, or isolate behavior within a particular section of your site. The Hit container defines which page hits you would like to include or exclude from a segment. Visit containers include values based on occurrence per visit: It can help you answer the question of how many visitors viewed the News and Sports section in the same visit? Or pages that attributed to a successful conversion to a sale? The Visit container is the most commonly used container because it captures behaviors for the entire visit session once the rule is met and lets you define which visits you want to include or exclude in building and applying a segment. The Visit container lets you identify page interactions, campaigns, or conversions for a specific web session. Visitor containers can include values based on a visitor’s overall history: Consequently, the Visitor container is the most susceptible to change based on defined date ranges. As the most broadly-defined container, reports generated at the Visitor container level will return page views across all visits and lets you generate a multi-visit analysis. A segment at the Visitor level returns the page that meets the condition plus all other pages viewed by the visitor (and only constrained by defined date ranges). The Visitor container includes every visit and page view for visitors within a specified time frame. Your browser does not support the iframe element. Here is a video overview of segment containers: Each container lets you report across a visitor’s history, interactions broken down by visits, or break down individual hits. A nested Visit container lets you set rules to break down the visitor’s data based on visits, and a nested Hit container lets you break down visitor information based on individual page views. The container architecture employed in the Segment Builder defines Visitor as the outermost container, containing overarching data specific for the visitor across visits and page views. The Segment Builder provides a simple architecture to build these subsets and apply rules as nested, hierarchical Visitor, Visit, or Hit containers. To further break down visitor data, you can filter based on specific visits and/or page view hits for each visitor. To set conditions in a segment, you set rules to filter visitors based on visitor characteristics and/or navigation traits. A Segment sets conditions to filter a visitor based on his or her attributes or interactions with your site.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |