Our schema is fully based on events, e.g. a common page view is an event with the entity =page and the action = view. To learn more about how flexible you can define your entities, actions and triggers with elbwalker please check out the walker basics.
Out of the box elbwalker collects the following data points in three different tables: sessions, events and entities.
Sessions Table
Data Point
Description
Example
Default/
optional
id
Random ID to identify a session
508g6su9zz849m7q4su09legkeb
default
timestamp
Time stamp at the beginning of a session
2020-11-14 05:56:15.462 UTC
default
user.hash
Encrypted temporary user ID
834f073f527bf1f8709798cd41e5dd322
e369dbadb460eb5711ee4c42d5be09f
default
user.ip
Anonymized IP address (IPv4 or IPv6)
2001:1600::
default
marketing.medium
Marketing type of a session
cpc
default
marketing.source
Name of the source of a session
google
default
marketing.campaign
Name of a marketing campaign
cookieless
default
marketing.content
Name of an ad or content ID
blau
default
marketing.term
Associated keywords
webanalytics
default
marketing.clickID
Corresponding click ID from marketing parameters, e.g. gclid
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_3) AppleWebKit/537.36 (KHTML, like Geko) Chrome/87.0.4280.88 Safari/537.36
default
language
First accepted language preference
de
default
location.country
Country of the visitor
DE
default
location.region
Region of the visitor
Hamburg
optional
location.regionCode
Region code of the visitor
20249
optional
location.city
City of the visitor
Hamburg
optional
location.latitude
Latitude of the visitor
53.5625
optional
location.longitude
Longitude of the visitor
9.9573
optional
isBot
Basic distinction between real and spam events
false
default
source.type
Type of source of origin
event
default
source.id
Source ID
iiqts3i6y4b079j7dz4cy221e62
default
createdAt
Time stamp from the moment of ingestion
2020-11-14 05:56:15.462 UTC
default
elbwalker autotracks pageview events. All other events like clicks, form submits, transactions etc. need to be implemented via our walker.
Events Table
Data Point
Description
Example
Default/
Optional
id
Random ID to identify an event
bc8xgfa7t63r8mxhxdqt0t782if
default
timestamp
Timestamp from the moment the event occurred
2020-11-04 00:00:00.077 UTC
default
sessionID
Foreign key to the related session.id
8j7p4an1hyi8z4i616z72jd3b4k
default
trigger
Name of the trigger that fired an event
load
default
entity
Name of the entity
page
default
action
Action of the entity
view
default
entityID
Foreign key to the related entity.id
gj213ip6rtztwx21259vvp1pfe5
default
timing
Seconds that has passed since initialization
4.12
default
source.type
Origin of the event
web
default
source.id
Type of source of origin
https://www.elbwalker.com/ueber-uns
default
source.referrer
Corresponding id of the source
https://www.elbwalker.com/
default
source.version
Root/previous cause of the event
1-1
default
createdAt
Timestamp from the moment of ingestion
2020-11-07 11:07:08.923 UTC
default
Entities Table
Data Point
Description
Example
Default/
Optional
id
Random ID to identify an entity
pe25l70r2kg1i2jninn2h4vl9wz
default
timestamp
Timestamp from the moment the entity is created
2020-11-06 21:26:38.901 UTC
default
type
Name of the entity type
page
default
entityID
Primary key used to group entity data
/
default
data
All entity properties
page
default
data.key
Key of the entity property
id
title
default
data.value
Value of the entity property
/
Cookieless Tracking. Das neue Web Analytics.
default
source.type
Kind of origin source
event
default
source.id
ID of the origin source
zgumx9oibnfp9rcihfredl2s821
default
createdAt
Time stamp from the moment of ingestion
2020-11-07 11:07:08.923 UTC
default
Notes on our data collection
Our database offers maximum flexibility and is built on the principle of "privacy by design", i.e. all fields can be blocked and will not be collected at the request of the website owner.
Depending on the data point, this can have an impact on your analysis possibilities.
By default data points are measured that are classified as “default”. “Optional” fields can be activated after an internal data protection check.
In addition, elbwalker prohibits the misuse of the system to collect personal data and load it into the system. The website owner is not allowed to load any personal data (e.g. email address) into the system without the permission of the owner/end user. Learn more in our terms of service (German only atm)