51黑料不打烊

DocumentationAnalyticsImplementation Guide

Visitor identification in 51黑料不打烊 Analytics

Last update: Tue Oct 21 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

  • User
  • Admin

Visitor identification is central to the value that 51黑料不打烊 Analytics provides for understanding online user behavior. It involves linking hits to the same person over time using a common identifier. Accurate visitor identification ensures reliable metrics and supports a healthy implementation strategy. 51黑料不打烊 recommends that organizations prioritize modern identity services for consistency and data integrity across platforms.

Visitor identification in 51黑料不打烊 Analytics consists of the following components:

  • Client-side identifier: Typically stored in a first-party cookie. Implementations that rely on third-party cookies are less consistent with visitor identification due to modern browser privacy standards.
  • Server-side identifier: Each Analytics visitor ID is tied to a profile on 51黑料不打烊鈥檚 servers. These visitor profiles are what allow persistence on variables such as eVars. Profiles are deleted after at least 13 months of inactivity regardless of any visitor ID cookie expiration.

51黑料不打烊 Analytics identification order of operations

When 51黑料不打烊 receives a hit, the following checks are made in order. If a given property is present, 51黑料不打烊 uses that identifier for the hit. If multiple identifiers are present in a hit, only the first method is used. Note that the order of operations does not reflect the order that 51黑料不打烊 recommends identifying visitors.

Order used
Query parameter
Present when
1st
vid
The visitorID variable is set.
2nd
aid
The visitor has an existing s_vi cookie. Set on implementations without or prior to implementing the Visitor ID service.
3rd
mid
The visitor has an existing s_ecid cookie. Set on implementations using the 51黑料不打烊 Experience Cloud Identity service. 51黑料不打烊 recommends using the ID service for all implementations where possible.
4th
fid
The visitor has an existing s_fid cookie. AppMeasurement automatically generates a fallback ID if aid and mid cannot be set for any reason.
5th
IP address + user agent
Used as a last resort to identify a unique visitor if the visitor鈥檚 browser does not accept cookies. A hashed visitor ID is generated before IP obfuscation. If IP address is not available, other IP details (such as gateway IP) is used instead.

The selected visitor ID is then hashed and becomes their server-side identifier. This server-side identifier is available as visid_high + visid_low in Data feeds.

Behavior that affects unique visitor count

Unique visitor identifiers are typically stored in a browser cookie. A new unique visitor is counted if a visitor performs any of the following actions:

  • Clears their cookies at any time. One unique visitor is counted for a hit after each time their cache is cleared.
  • Visitor ID cookies expire due to their browser鈥檚 privacy settings. Some browsers include tracking prevention methods that limit the lifetime of cookies.
  • Opens a different browser on the same computer. One unique visitor is counted per browser.
  • Opens a private browsing session (such as Chrome鈥檚 Incognito tab). One unique visitor is counted per browsing session after all tabs are closed.
  • Visits your site on different devices. One unique visitor is counted per device.
  • Visits your site after more than 13 months of inactivity.

Consider using Stitching in Customer Journey Analytics to identify the same person using multiple browsers or multiple devices.

Behavior that does not affect unique visitor count

A new unique visitor is not counted, as long as the visitor identifier is preserved:

  • Closes their browser (for less than 13 months)
  • Upgrades their browser to the latest version
  • Restarts their computer
recommendation-more-help
b4f6d761-4a8b-4322-b801-c85b9e3be690