The walker basics

All you need to know: Everything is based on Entions (= Entities & Actions). And everything is treated as an Ention e.g. the entity page can have the action view. Combined you’ll get a pageview. Entions are arbitrary to fulfill your needs and provide maximum flexibility with minimum complexity.

Entities, Actions and Properties

An entity has properties and an action is triggered by an event. Everything can be defined by design, using just some simple descriptive HTML attributes. Say hello to our own markup language and learn how to speak elbish.

Types

Usage

Example

Entities

elb="<entity>"

product, job, article

Actions

elb-action="<trigger>:<action>"

click:add,

visible:impression,

load:view

Properties

elb-<entity>="<key>:<value>"

price:29,

location:Hamburg,

author:Olli

Related properties use the entities name for identification and can be declared either on the same element or its child elements. The same applies for actions.

<!-- General usage -->
<div elb="<entity>" elb-<entity>="<key>:<value>" elb-action="<trigger>:<action>" />
<div elb="product" elb-product="name:Shirt" elb-action="click:add" />

Ention object structure

Everytime a trigger gets fired the walker creates objects of the following structure that will be pushed to each integration. It will be pushed to elbwalker analytics by default.

interface Ention {
action: string;
entity: {
type: string;
data: { [prop: string]: string };
};
trigger?: string;
}