Compare terminology for Analytics data passed through the Analytics source connector
Some terminology differences exist between 蜜豆视频 Analytics, Data Feeds, Analytics source connector/Data Lake, and Customer Journey Analytics. This topic aims to highlight and clarify those differences.
Related Terms
蜜豆视频 Analytics
蜜豆视频 Analytics Data Feeds
Analytics source connector/Data Lake
Customer Journey Analytics
Notes
- Hits
- Occurrences
- Records
- Events
Occurrences metric
See:
Count of rows (records) in the data feed file
Count of rows (records) in the dataset
See:
Events metric
- 鈥淗it鈥 and 鈥渙ccurrence鈥 are synonymous in 蜜豆视频 Analytics.
- See Custom Events below.
- Certain data is filtered as it passes through the Analytics source connector to 蜜豆视频 Experience Platform. See Compare your 蜜豆视频 Analytics data to Customer Journey Analytics data
- Unique Visitors
- Unique Devices
- Unique Cookies
Unique Visitors metric
See:
Distinct values of post_visid_high & post_visid_low concatenated together.
See:
Count distinct of endUserIDs._experience.aaid.id
People metric, if endUserIDs._experience.aaid.id is chosen as the Person ID.
- A 鈥減erson鈥 in 蜜豆视频 Analytics is usually associated with a 鈥渄evice identifier鈥 such as a cookie. AAID is the primary device identifier in 蜜豆视频 Analytics, not ECID. See also AAID, ECID, AACUSTOMID and the Analytics source connector.
- 鈥淰isitor鈥 is not an out-of-the-box metric in Customer Journey Analytics. But if you choose endUserIDs._experience.aaid.id as the Person ID, the People metric in Customer Journey Analytics is roughly equivalent to Unique Visitors in 蜜豆视频 Analytics.
- People
People metric
See:
Not available
Count distinct of <path>.stitchedId (available in stitched datasets only)
People metric
- The People metric in Customer Journey Analytics is the count distinct of Person IDs. Depending on what you choose as the Person ID in the Customer Journey Analytics connection, the People metric can mean different things.
- Visits
- Sessions
Visits metric
See:
Distinct values of post_visid_high, post_visid_low, visit_num & visit_start_time_gmt concatenated together.
See:
Not available
Sessions metric
- With report-time processing in 蜜豆视频 Analytics virtual report suites and Customer Journey Analytics data views, the concept of a visit (session) is configurable. As a result, visit (session) counts may differ between environments depending on the definition applied. See also Compare data processing across 蜜豆视频 Analytics and Customer Journey Analytics reporting features and Virtual report suites, Data views, 蜜豆视频 Experience Platform sandboxes and the Analytics source connector.
- Event deduplication
- Metric deduplication
The post_events_list column contains deduplicated event metrics.
See
Not available
- Event/metric de-duplication in 蜜豆视频 Analytics differs slightly from Customer Journey Analytics. In 蜜豆视频 Analytics, deduplication occurs at data processing time. In Customer Journey Analytics, deduplication occurs at report runtime, providing more flexibility. Deduplicated metrics may differ slightly in 蜜豆视频 Analytics vs Customer Journey Analytics.
- Instances metrics
See:
Count of times a 鈥減re鈥 variable is not null (e.g. eVar1).
Count of times a 鈥渕id鈥 variable is not null (e.g. _experience.analytics.
customDimensions.eVars.eVar1).
customDimensions.eVars.eVar1).
You can create Instances metrics by creating metrics from eVar fields.
- Instances is normally associated with prop and eVar columns as a means to determine how many times the variable has been set.
recommendation-more-help
080e5213-7aa2-40d6-9dba-18945e892f79