Component support in Data Warehouse

The unique processing in Data Warehouse architecture allows some components that aren’t typically available in other capabilities of Adobe Analytics. Due to its unique architecture, some components are not available for use in either reports or segments. Use this page to understand what can be used, and what cannot.

Components unique to Data Warehouse

Some dimensions and metrics that can be used in Data Warehouse are not available when using other capabilities in Adobe Analytics.

Dimensions supported exclusively

• Experience Cloud ID: For implementations that use the Experience Cloud ID Service (ECID), a 128-bit number consisting of two concatenated 64-bit numbers padded to 19 digits.
• Page URL: The page URL the hit occurred on.
• Purchase IDs: Unique identifier for a purchase, set using the purchaseID variable.
• Visitor ID: Provides the unique identifier for the visitor. This value is the same as concatenated value of visid_high and visid_low columns in data feeds. See Data column reference under Data Feeds for more information.

Metrics supported exclusively

• Visits: This metric in context of Data Warehouse excludes non-persistent cookie visits.
• Visits - All Visitors: This metric in context of Data Warehouse has closer parity with the visits metric in other tools within Adobe Analytics.

Components not supported in Data Warehouse

Some dimensions and metrics are not supported in Data Warehouse.

Dimensions not supported

• AM/PM
• Some pathing-based dimensions, including:
  • All Entry dimensions, except Entry Page
  • All Exit dimensions, except Exit Page and Exit Link
  • Hit Depth
  • Return Frequency
  • Time Prior to Event
  • Time Spent on Page - Bucketed
  • Time Spent per Visit - Bucketed
• All Search Page Rank
• Hierarchy variables
• Hit Type
• Pages not Found (available as a dimension; not supported for segmentation)
• Paid Search
• Single Page Visits
• Tracking Opt-out Reason
• US States

Metrics not supported

• Some pathing-based metrics, including:
  • Bounces
  • Entries
  • Exits
  • Reloads
  • Single Access
  • ‘Time Spent’ metrics
• Participation metrics (as described in Build a “Participation” metric)

Dimensions supported in a different way (non-standard date formatting)

The following time-based dimensions are supported:

• Year
• Quarter
• Month
• Week
• Day
• Hour
• Minute

However, the output of dates is non-standard when using these dimensions.

Consider the following when calculating the output of dates in Data Warehouse:

• Date dimensions are shown in the following format: 1YYMMDDHHMM

• The year (YY) is offset by 1900. This means that you add 1900 to the first 3 values of the date field.

  For example, if the value of the Date Range Week field in Data Warehouse is 1250901, you would add 1900 to 125, which results in the year 2025.

• All months are zero-based, with January being represented by 00, February by 01, and so forth, as follows:

  • 00: January
  • 01: February
  • 02: March
  • 03: April
  • 04: May
  • 05: June
  • 06: July
  • 07: August
  • 08: September
  • 09: October
  • 10: November
  • 11: December

  For example, if the value of the Date Range Week field in Data Warehouse is 1250901, the month is represented as 09, which indicates October.

Segments as dimensions in Data Warehouse

When you use a segment as a dimension in Data Warehouse, the report returns a column containing "0" or "1":

• "0": The dimension item did not meet the segment’s criteria.
• "1": The dimension item met the segment’s criteria.