ONEcount Cookies

ONEcount uses first-party cookies to track users. The cookies are set in the ONEcount domain and on the customer's site(s).

Cookies on the ONEcount domain are called Central Domain Cookies (CDC). Those on the client's site are called Local Cookies (LC).

Below is a list of the cookies and their description:

First Part Cookie Setting

ONEcount sets 2 types of cookies: A temp cookie on the first visit- and an OCID cookie when the user is identified by registering, logging in, or when OC performs a cookie sync. All ONEcount cookies are first-party cookies, which means they are supported by all web browsers.

When a user visits the site for the first time, he or she will have no ONEcount cookies for that site.  In order to facilitate multi-site tracking, targeting and gating, ONEcount will do an initial redirect to the onecount.net domain to determine if the user has a cookie in the onecount.net domain, meaning, he or she has already been identified on another site within the customer’s group of sites

If the user is already identified in the onecount.net domain, ONEcount will set a cookie in the local domain identifying that user. When the user returns to the local site, they will no longer be redirected.

The One-Time redirect will happen only when you visit a page for the 1^st time of a brand and is considered an industry standard.

 Upon registering, clicking on a smartlink, or being identified through a cookie-sync with a third-party, ONEcount sets an OCID cookie showing that we have identified the person as a known user.

This helps a brand that has multiple sites. If a customer has 40 sites and a user is identified on Site A, then ONEcount will first set the temp cookie and then OCID cookie and store that data as a known user.

If a user visits Site B, then OCID will be able to retrieve that user’s identity, which is stored in cookies on the onecount.net domain. At this point, the user is known and his or her activity can be tracked across all brand sites that the user has registered for.

Central Domain Cookies

These cookies are set on the ONEcount domain.

__ocgt: This is the global token. It's used to track users across all sites where the ONEcount widget is deployed. The value is a 64-character hash. This cookie is set under onecount.net domain.

__ocid: set when a user is logs in on one of the Customer's sites. The value is a 64-character hash that represent sthe user in that customer's installation of ONEcount. It's set under client-reg.onecount.net domain. (ie: if client is foo, then the cookie will be set under foo-reg.onecount.net)

__ocusername: Similar to __ocid, it's set when the user logs in on the client's system. The value, is the user's username on that client's system. The domain for this cookie client-reg.onecount.net.

Local Cookies

These cookies are set on the customer's site(s). If the customer has multiple sites, these cookies will be set as first-party cookies in each domain.

__tempcookie: used track users on the client's site. The value is the same as __ocgt from the central domain. It's set under the client's site domain.

__ocid: set when a user is logged in on the client's site. The value is the same as __ocid from the central domain. It's set under the client's site domain.

__ocusername: set when a user is logged in on the client's site. The value is the same as __ocusername from the central domain. It's set under the client's site.

cookieValid: this is a daily cookie. It's set on the first visit of the day if __ocid is present. It's used as a flag that can be used to determine whether __ocid is still valid or not.

realReferer: used to preserve the original referer when a redirect to onecount.net happens for setting the Central Domain Cookies. This can be passed to Google Analytics or other platforms.

_gcna: this represents the visit id. The value is a combination of the __ocid and __tempcookie cookies as well as the visit timestamp and the visit counter.

_gcnb: used as part of the visit id generation process.