Compare terminology for Analytics data passed through the Analytics source connector

Last update: 2024-03-08

Topics:
Basics
View more on this topic

Created for:
User

Some terminology differences exist between Adobe Analytics, Data Feeds, Analytics source connector/Data Lake, and Customer Journey Analytics. This topic aims to highlight and clarify those differences.

Related Terms	Adobe Analytics	Adobe Analytics Data Feeds	Analytics source connector/Data Lake	Customer Journey Analytics	Notes
Hits Occurrences Records Events	Occurrences metric See: Terms used in Adobe Analytics Occurrences	Count of rows (records) in the data feed file	Count of rows (records) in the dataset See: Compare your Adobe Analytics data to Customer Journey Analytics data	Events metric	“Hit” and “occurrence” are synonymous in Adobe Analytics. See Custom Events below. Certain data is filtered as it passes through the Analytics source connector to Adobe Experience Platform. See Compare your Adobe Analytics data to Customer Journey Analytics data
Unique Visitors Unique Devices Unique Cookies	Unique Visitors metric See: Terms used in Adobe Analytics Unique Visitors	Distinct values of post_visid_high & post_visid_low concatenated together. See: Use data feeds to calculate common metrics	Count distinct of endUserIDs._experience.aaid.id	People metric, if endUserIDs._experience.aaid.id is chosen as the Person ID.	A “person” in Adobe Analytics is usually associated with a “device identifier” such as a cookie. AAID is the primary device identifier in Adobe Analytics, not ECID. See also AAID, ECID, AACUSTOMID and the Analytics source connector. “Visitor” 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 Adobe Analytics.
People	People metric See: People	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: Terms used in Adobe Analytics Visits Report time processing	Distinct values of post_visid_high, post_visid_low, visit_num & visit_start_time_gmt concatenated together. See: Use data feeds to calculate common metrics	Not available	Sessions metric	With report-time processing in Adobe 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 Adobe Analytics and Customer Journey Analytics reporting features and Virtual report suites, Data views, Adobe Experience Platform sandboxes and the Analytics source connector.
Event deduplication Metric deduplication	See: Event ID serialization	The post_events_list column contains deduplicated event metrics. See Data column reference.	Not available	See: Metric deduplication component settings	Event/metric de-duplication in Adobe Analytics differs slightly from Customer Journey Analytics. In Adobe 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 Adobe Analytics vs Customer Journey Analytics.
Instances metrics	See: Instances	Count of times a “pre” variable is not null (e.g. eVar1).	Count of times a “mid” variable is not null (e.g. _experience.analytics. 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.

On this page

View next: