The walker.js is an open-source event tracker for all tools. Easy, standardized & flexible. Capture user events in the browser and send them to any destination - just by setting HTML attributes.
Explore the docs ยท Report Bug ยท Request Feature ยท Say hello
You can implement all sorts of front-end user events. From e-commerce actions like product add to cart or order complete events as well as measuring product usage events, and UX events like navigation or filter usage etc.
Just set a few HTML attributes
<!-- General usage -->
<div elb="ENTITY" elb-ENTITY="KEY:VALUE" elbaction="TRIGGER:ACTION" />
<!-- Example usage -->
<div
elb="product"
elb-product="name:Everyday Ruck Snack;price:220"
elbaction="click:add"
/>
The result is for example something like this:
dataLayer.push({
event: 'product add', // combination of entity and action
data: {
// all set properties with the elb-product attribute
name: 'Everyday Ruck Snack',
price: 220,
},
globals: {
// all set properties with the elbglobals attribute
// Not shown in example usage snippet (elbglobals="language:en;test:darkmode")
language: 'en',
test: 'darkmode',
},
user: {
// a stored random id in the cookie (manually added once)
device: 'cookieid',
},
nested: [], // all nested entities within the product
id: '1647968113641-b4b9h9-5', // timestamp, group & count of the event
trigger: 'click', // name of the trigger that fired
entity: 'product', // entity name
action: 'add', // entity action
timestamp: 1647968113641, // time when the event fired
timing: 13.37, // how long it took from the page load to trigger the event
group: '01b5e2', // random group id for all events on a page
count: 2, // incremental counter of the events on a page
version: {
// Helpful when working with raw data
walker: 1.1, // used walker.js version
config: 42, // a custom configuration version number
},
walker: true, // flag to filter events
});
You are completely free to define naming conventions. All you need to get started are the entity, action & trigger attributes.
- You define the entity scope by setting the
elb
attribute with the name of an entity to an element, e.g.elb="product"
. - An action can be added by setting the
elbaction
attribute on the same level or all child elements in combination with a matching trigger, e.g.elbaction="click:add"
to fire a product add event when a user clicks on the tagged element. - (Optional) To define the entities' properties, set the composited attribute
elb-ENTITY
with the name and value, e.g.elb-product="name:Everyday Ruck Snack;price:220"
.
<body elbglobals="language:en;test:darkmode">
<div elb="product">
<h1 elb-product="name:Everyday Ruck Snack">Everyday Ruck Snack</h1>
<p elb-product="price:220">Price: 220 Euro</p>
<button elbaction="click:add">Add to cart</button>
</div>
</body>
elb
,elbaction
andelbglobals
are reserved attributes whereaselb-
attributes may be arbitrary combinations based on the related entity name. Actions and properties can be set anywhere inside anelb
attribute.
By using the walker.js you don't have to deal with event listener or mutation observer initialization anymore. The walker comes with a bunch of integrated triggers that will fire your event at the right moment.
Trigger | Definition |
---|---|
load | after loading a page when DOM is ready |
click | when the element or a child is clicked |
visible | after the element has been in viewport for at least 50% for one second |
submit | on a valid form submission |
custom | calling elbLayer.push() |
For further inspiration, please refer to the industry examples in our docs.
Learn more about the elbwalker event model and background in our blog.
There are three modes: default
, custom
, and managed
. Modes describe different ways in which the walker.js can be used.
By using the default mode, elbwalker automatically starts and pushes events without further configuration into the dataLayer so that you can use it in Google Tag Manager (GTM).
<script class="elbwalker" src="walker.js"></script>
By using the custom mode, you can e.g. customize destinations flexibly through code yourself. You can use the elbLayer to do the configuration manually.
<script class="elbwalker" src="walker.js" data-custom="true"></script>
When using our managed mode, a project ID will be added to the script. You can generate your custom project ID and configure the walker.js through our web app (UI).
<script class="elbwalker" src="walker.js" data-project="W3BSHOP"></script>
To get a local copy up and running follow these simple steps.
- Clone the repo
git clone https://github.com/elbwalker/walker.js.git
- Install NPM packages
npm install
- Start developing
npm run dev
By default all events gets pushed to the dataLayer
. But you can customize the destinations you want to use. The walker.js comes with optional build-in destinations.
Example of adding a GA4 destination:
import GA4 from './destinations/google-ga4'; // Load the destination
GA4.config.measurementId = 'G-XXXXXXX'; // Set all required properties
elbwalker.push('walker destination', GA4); // Add the destination
A destination has a config
object and an optional init
as well as the push
function.
As soon as an event triggers the destinations init function gets called once.
And all events will get sent to the additional destination now.
Any contributions you make are greatly appreciated.
If you have a suggestion that would make the walker better, please fork the repo and create a pull request. You can also simply open an issue with the tag "enhancement".
- Fork the Project
- Create your Feature Branch (
git checkout -b feature/AmazingFeature
) - Commit your Changes (
git commit -m 'Add some AmazingFeature'
) - Push to the Branch (
git push origin feature/AmazingFeature
) - Open a Pull Request
Distributed under the MIT License. See LICENSE for more information.
Send us an email if you have any questions or feedback at hello@elbwalker.com
Want to send the data directly to your Google BigQuery instance? Check out our hosted version at https://elbwalker.com/