Get the clear '(id)ea' about IDs!

Frequently encountering terms such as cookie ID, session ID, visitor ID etc.?

Not sure why they are tracked and who sets them up?

Do you find yourself confused and unable to understand despite several articles online?

If you fall in any of the categories above, then this article is for you!

In digital analytics, Visitor ID, Cookie ID, Session ID, ECID (Experience Cloud ID) are all identifiers used to track and identify users' interactions on websites or digital platforms.

Let's look and try to understand each of these IDs and how they are used in tracking:

Visitor ID:

• Definition: A unique identifier assigned to each individual visitor across multiple sessions and devices. It helps in tracking the behavior and activities of a specific user over time. In Adobe Analytics and similar platforms, Visitor IDs are typically generated and tracked automatically.
• Example: In Adobe Analytics, a Visitor ID might look like "1234567890abcdef1234567890abcdef."
• Use Case: Enables tracking of how often a user visits a site, what actions they perform, and how their behavior changes over time.
• Setup: No explicit setup is required by the user or website administrator for Visitor IDs in Adobe Analytics. They are managed by the analytics platform itself.

Cookie ID:

• Definition: An identifier stored on a user's device through their web browser. It is used to recognize returning users and maintain session state. Cookie IDs are generated automatically by web browsers when a user visits a website that uses cookies for tracking. They are stored on the user's device.
• Example: A cookie might store an ID such as "a1b2c3d4e5f6g7h8."
• Use Case: Allows websites to remember users across sessions and personalize their experience based on past interactions.
• Setup: Websites need to implement cookies through code (e.g., JavaScript) to set and read cookie IDs. They are not tracked automatically by analytics platforms but by the website’s own implementation.

Session ID:

• Definition: An identifier used to track a user's current visit or session on a website. It typically expires or resets when the user closes their browser or after a period of inactivity. Session IDs are typically managed automatically by web servers or applications to track a user's current session on a website. They are temporary and may reset after a period of inactivity or when the user closes their browser.
• Example: A session ID might be "Session123456789."
• Use Case: Helps in grouping user interactions within a single browsing session, such as tracking a series of pages viewed during a single visit.
• Setup: Session IDs are managed by the web server or application hosting the website. Developers may need to configure server-side logic to handle session tracking, but it’s a standard feature of web applications.

ECID (Experience Cloud ID):

• Definition: A unique identifier provided by Adobe's Experience Cloud services, which helps in stitching together visitor data across different Adobe solutions and devices. ECIDs are part of Adobe’s Experience Cloud services and are automatically tracked across Adobe solutions. They are designed to provide a unified view of user interactions across different Adobe-powered platforms and devices.
• Example: An ECID could be "ECID-1234567890."
• Use Case: Enables a unified view of a user's interactions across various Adobe-powered digital properties, ensuring consistent tracking and personalization.
• Setup: ECIDs are managed and tracked automatically within Adobe Experience Cloud. Users and administrators typically do not need to set them up separately, as they are integrated into Adobe’s ecosystem.

Campaign ID:

• Definition: An identifier used to track specific marketing campaigns or promotions.
• Example: A campaign tracking code appended to URLs (e.g., "utm_campaign=summer_sale").
• Use Case: Enables tracking the effectiveness of different marketing initiatives and attributing user actions to specific campaigns.
• Setup: Marketing teams create and manage campaign tracking codes using tools like Google Analytics Campaign URL Builder or custom URL parameters. These codes are then integrated into marketing materials (e.g., email newsletters, social media posts).

Transaction ID:

• Definition: An identifier associated with a specific transaction or purchase made on a website or app.
• Example: An order ID (e.g., "ORD-123456789").
• Use Case: Facilitates tracking of e-commerce transactions, including purchase details and revenue attribution.
• Setup: E-commerce platforms or developers configure systems to generate unique transaction IDs for each completed purchase. Analytics platforms then capture these IDs along with transaction details for analysis.

User ID:

• Definition: A unique identifier assigned to a registered user who logs in to a website or app.
• Example: A user-specific ID (e.g., "user123").
• Use Case: Allows for tracking and analyzing user behavior across multiple sessions and devices, providing a more personalized user experience.
• Setup: Websites and apps with user registration systems integrate user ID tracking by assigning unique IDs upon user registration or login. This integration often requires backend development to ensure IDs are securely managed and used consistently across platforms.

The above examples, set ups and Definitions are hopefully enough to clarify the different types of IDs that are generally captured for websites & apps.

The specific IDs tracked can vary based on the analytics platform's capabilities and the organization's tracking requirements. Each ID provides valuable insights into different aspects of user behavior and engagement, contributing to a comprehensive understanding of digital performance.

If you found this post useful, please share it within your network and subscribe to the #DecodingDigital newsletter! :)