Reporting, Segments, and Integrations
Containers decide the answer
Every segment is built from containers: hit, visit, and visitor, plus sequential variants. The container determines scope. A hit-container segment filters which rows qualify. A visit-container segment returns all hits belonging to qualifying visits. A visitor-container segment returns everything that visitor ever did, which inflates metrics and surprises candidates. Sequential segments use then with optional within time limits and are the standard way to express funnels; non-sequential segments measure co-occurrence, not order.
Know how segments combine: multiple segments applied to one panel are ANDed, and a segment plus a metric filter such as visits where an event is greater than zero also ANDs at the visit level. Attribution models change which dimension value receives credit for a conversion across a lookback window, so a segment and an attribution model can produce different totals for the same metric. Virtual report suites apply permanent filters and can change time zone and calendar. Calculated metrics stay private unless shared.
Integration knowledge is mostly about picking the right pipe: Analytics API 2.0 for programmatic reports, data feeds and Data Warehouse for raw exports, classifications for metadata, Report Builder for Excel, and Experience Cloud links - A4T for Target activity dimensions inside Analytics, Audience Manager for shared audiences, and Campaign or Advertising Cloud feeding marketing channel attribution. Customer Journey Analytics applies when the organization has moved to the Edge Network and XDM.
Traps: expecting a segment to alter underlying data; mixing hit and visit containers in one comparison; forgetting A4T needs proper Target and Analytics configuration; and assuming API dimensions use friendly names rather than IDs (eVar1, not Promo Code).
Rule of thumb: before building a segment, state out loud which container and which scope the question needs.
Worked example: visits where a visitor viewed a product page and then submitted a form within the same visit. That is a sequential segment with a visit container, page view then form submit, ordered.