Navigation

Journey Module Web Storage Methods

When Journey is configured on your website, we use 2 web local storage methods to identify the visitors' journey on the website:

  1. Browser local storage (cleaned at the end of each browser session)
  2. Local storage object (never expires)

Note: When using a browser in private mode, all data is deleted at the end of the session.

Web storage is a method for storing data in a web browser. Web storage supports persistent data storage, similar to cookies but with a greatly enhanced capacity (at least 5MB) and no information stored in the HTTP request header. There are two main web storage types: local storage and session storage, behaving similarly to persistent cookies and session cookies. Their only difference relates to data persistence. All browsers have options for the visitors to disable or clear stored data. 

Each method uses a key/value pair which is unique by the origin of the visited page (same protocol, domain and port). Data stored in sessionStorage for a given origin can only be accessed from the tab where the data was stored and only for those pages that share the same origin. If you wish to hide information, choosing a complicated storage key is of no use, as it is possible to identify keys.

The storage capacity is from 5 to 10 MB per object (depending on the browser) per script origin that updates values. So, a malicious script cannot use the entire storage space to block other scripts from web storage.


The sessionStorage Object

The sessionStorage interface memorizes data for the duration of one browsing session, and is limited to the active window or tab. When the browser tab is closed, data is deleted. Each session storage is limited to one a domain. Data stored in sessionStorage for a given origin can only be accessed from the tab where the data was stored and only for those pages that share the same origin.

Key
Values
Description of the value
OFSYS_Visit_{clientcode}

Values associated with a visit. 
vkeyKey of a visit.
oft_campaignThe campaign (if there is any).
["oft_id", "oft_k", "oft_lk", "oft_d", "oft_c", "oft_ck"]If it applies, a value is used to identify the contact in the client’s project. In order: idSendlog, sendlog key, link key, dtClick, idContact, contact key. 

The localStorage Object

The localStorage interface stores data with no expiration date. Unlike sessionStorage, data will not be deleted when the browser or tab is closed. The extent of localStorage is therefore wider: it is possible to open multiple tabs for the same domain or multiple windows, as long as it is in the same browser. Stored data in localStorage for a given origin is accessible in all tabs of pages that share the same origin.

Key 
Values
Description of the value
OFSYS_Interception_{clientcode}

Values used to evaluate whether interception is possible or not.  
DisplayInterceptorTotalCountTotal number of times the interceptor was displayed. 
DisplayByVisitCountNumber of times the interceptor was displayed during the current visit. 
dtDisplayList of all the dates when the interceptor was displayed. 
OFSYS_Extra_{clientcode}

Additional values that can be stored after a special event has been configured by the client. 
dtFirstHitDate of the first time the event occurred. 
dtLastHitDate of the last time the event occurred. 
vkeyVisitorKey of the visitor.
totalHitNumber of times the event was triggered. 
{personalized value}A personalized value.
OFSYS_Visitor_{clientcode}

Describes the visitor. Identifies the visitor and if interception is possible. 
vkeyKey of the visitor.
OFSYSEVENT_dtLastHit_{event name}Date of the last time the event "eventname" occurred. 
OFSYSEVENT_countHit_{event name}Number of times the event "eventname" occurred. 
OFSYSEVENT_dtFirstHit_{even tname}Date of the first time the event "eventname" occurred. 
VisitCountNumber of visits.
dtFirstVisitDate of the first visit. 
dtLastVisitDate of the last visit.
dtPreviousVisitDate of the previous visit.  
openedPageCountNumber of opened pages during the current visit. 
lastOpenedPageLast page opened.
HitCountTotal number of hits.
HitCurrentVisitNumber of hits during the current visit. 
TotalVisitSecondTotal number of seconds spent on the site (all visits), calculated on each hit. 
TotalSecondOpenTotal number of seconds spent on the site (all visits), calculated in real-time. 
CurrentVisitSecondNumber of seconds spent on the site during the current visit, calculated on each hit. 
IsIdentifiedFlag that indicates if the visitor was identified. 
TotalSecondOpenVisitNumber of seconds spent on the site during the current visit, calculated in real-time. 

Fallback: Cookies

When a browser does not allow the use of sessionStorage and localStorage (it's not very common), cookies are used as a fallback.

Visitor Cookie

Name: OFSYS_VisitorID_{idSite}

Content: A unique code with 6 alphanumeric characters (vkey)

Usage: Identifies the visitor. This value will eventually let you recognize the visitor and present the most relevant content on subsequent visits.  

Expiration: 2 years.

Visit Cookie

Name: OFSYS_VisitID_{idSite}

Content: A unique code with 6 alphanumeric characters (vkey) and, if it applies, one or several of the identifiers presented in this table: 

Key
Value
Usage
oft_ididSendlogMeasures the impact of source communications that initiated the visit.
oft_ksendlog key
oft_lklink keyMeasures the impact of click actions on URL links that initiated the visit.
oft_ddtClickIndicates the date of the click. 
oft_cidContactAssociates the actions performed on a visit to a contact, in order to measure interest and offer better communications in the future.
oft_ckcontact key
oft_campaigna campaign tagIdentifies the campaign at the source or associated with the visit and measures its impact.

Usage: 

  • Identifies a contact’s actions based on the interest shown on visited pages (both visit and visitor cookies let you associate data with contacts, depending on the situation).
  • Splits a contact’s actions per visit; visits are collected to measure the impact of communications in order to make them more pertinent.

Expiration: At the end of the session.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.