What is an elbwalker destination and why should I use it?

A destinations works like a connector to other great tools. It takes care of the right initialization, mapping and any further transformation as well as the invocation of events. Each destination handled by elbwalker is an enormous time saver since you have finished most of the work just by tagging a website using our walker.

Concept of how destinations via elbwalker work

Please make sure you're using a Consent Management Platform to manage your users' consent for your analytics and marketing tools. elbwalker does NOT handle the consent management for 3rd parties for you. It only reduces the massive setup effort that comes with having a lot of tools implemented on a site.

How does it work?

Example Pageview

The most common and best known analytics event is the pageview. Since everything is treated as an ention, the walker will automatically trigger an ention with the action view and an entity page by default. The ention combination gets pushed to all registered channels.

"action": "view",
"entity": {
"type": "page",
"data": {
"hash": "",
"id": "/",
"search": "",
"title": "elbwalker analytics"
"trigger": "load"

Example Add to cart

Also a common analytics event is the add to cart. The walker will trigger an ention with the action add and an entity product once you marked it in your HTML. The ention combination gets pushed to all registered integrations, e.g. Google Ads & Facebook Pixel.

"action": "add",
"entity": {
"type": "product",
"data": {
"id": "ID1234",
"name": "Blue T-Shirt",
"price": "14.95",
"size": "m"
"brand": "thisbrand"
"trigger": "click"

Your dream destination is not available yet? Reach out to us and let's see what we can do: [email protected] 🤓