OCL 2.0 Locators use an EVENT_NAME column to track specific analytic points throughout our different templates. This page shows which templates each event can be triggered from, for details regarding how each event is triggered and what data these events track see the individual event pages.
Default Data Points
Unless otherwise specified all events will have the below fields included:
| client | The clients' id value. Typically the client_db value from the Destini Database |
| locator |
A pipe | delimited value containing the follow values (in order):
|
| country |
The Country the locator is currently searching for. This value is determined by:
If the locator was unable to geolocate a country this value will be UNKNOWN |
| region |
The Region, also known as state, the locator is currently searching for. This value is determined by:
If the locator was unable to geolocate a region this value will be UNKNOWN |
| city |
The City the locator is currently searching for. This value is determined by:
If the locator was unable to geolocate a city this value will be UNKNOWN |
| zipcode |
The Zipcode, also known as postal code, that the locator is currently searching for. This value is determined by:
If the locator was unable to find a Zipcode via the above methods this value will be UNKNOWN |
| sessionId |
The visitors “unique” session ID value, used to identify different visitors to the locator. This value is created by MD5 hashing the visitors IP Address, User Agent, and the YYYY-MM-DD H timestamp of their visit. This means the same person will get a different sessionId every hour and that people visiting on the same version of a browser from the same IP address will get the same hash (for example from a Library). |
Misc Notes
Ingestion is triggered every 15 minutes and processes data from GTM that is a day behind. Since this process is from a day ago and we don’t send any product/label/category associations we must grab that at the time ingestion. This means that if the client makes any changes it can affect ingested data for up to 24 hours.
Useful Definitions
Locator session
A locator session starts as soon as the locator loads and ends as soon as the client navigates away from the locator. This includes refreshing the page, which will end their previous session and start a new session.
Search session
A search session starts as soon as a search is initiated. A search is automatically triggered if DTR=1 is specified on the locator URL or if the Locator Template is Results First. A search session is based off the locator’s selected country & language as well as what products were selected and what location is being searched.
A new search session is created when:
- The selected country changes
- The selected language changes
- The searched location changes
- The selection of products has changed
- This means if you go back to the product selection screen but do not make any changes and then click the Find Products button a new session is not created.
Comments
Article is closed for comments.