Learn about Goal Tracking
On this page we explain you what does "goal tracking" mean. But if you already know please just jump straight to the point: How to manage "goal-tracking"? :-)
Content of this page
- # What is "goal tracking"?
- # Some quick examples
- # Role of "visit session"
- # How to manage "goal tracking"?
- # Opening the editor
- # The "goal tracking rule"
- # Conditions
- # Event (to fire) setup
What is "goal tracking"?
First of all let's clarify the term "goal": this is YOUR goal. It means something which is important for you as website owner.
And this leads to the following simple definition of "goal tracking": the Visitor behaved during the visit on your website which fulfills the criteria of your "goal" definition.
If that happens, Keytiles fires an Event - increasing the count of it. And by observing how many times the Event fired you can track how many visits of Visitors reached YOUR goal.
Some quick examples
To build better understanding let us give you a few possible "goal" definitions you might be interested in to track:
- "Visitor visited at least 5 contents (Tiles) during the visit"
So (s)he made a long visit on your website, your content is clearly successful as it is engaging Visitors. - "Visitor made a purchase after reading our special offer"
Pretty much self explanatory goal right? - "Visitor came from Facebook or Instagram to our website and later (s)he made a purchase" or more generic "Visitor came from a social platform to our website and later (s)he made a purchase".
You can measure success of your social media presence. - Similarly "Visitor came from a search engine to our website, saw our special offer and later (s)he made a purchase"
You can measure success of your SEO strategy. - "Visitor came from our e-mail Campaign and during this visit (s)he checked our special offers"
You can measure success of your Campaign strategy.
Simple no?
You can combine many things in the criteria which is known about a visit. And this leads to the next point - keep reading...
Role of "visit session"
If you read the above examples you can notice a trivial thing: none of the above questions can be answered without somehow joining different "clicks", different actions your visitor made into something we call: "the visit".
You simply need to know which actions have happened within one visit of the visitor, even in which order. This is what we call "visit session". And Keytiles is capable of doing this so we have it! If you are curious about how does it work, you can check this article. But what is important to note here is: VisitSession works in Keytiles even without any cookie (in this case with ~98.5% precision - yes, we track it that's how we know:-)) so this is a pretty much reliable functionality we can absolutely build on!
How to manage "goal tracking"?
To manage this you need to be in "admin" role in the Data Container.
If you are not admin you can just view the rules but can not change them.
It is easy. Basically you need to phrase so called "goal tracking rules".
Opening the editor
- On the UI just go to the Data Containers page (https://gui-test.keytiles.com/system/data-containers)
- You see there how many goals are configured - this is a link, simply just click it!

The "goal tracking rule"
In this editor you can manage goal tracking rules where each rule consists of:
- condition - an expression which if evaluates to True then the criteria is fulfilled and an event is triggered as the goal is reached.
- event setup - which drives what event is fired and how does it behave when condition is met.
additionally, you can also give it
- title - which is used to display this rule on the UI so your colleagues can recognize this (keep it short but descriptive).
- description - as free text to provide some explanation what/why it does.
Simple like that.
You can have of course multiple goal tracking rules so you can track the success of multiple "goals".
Conditions
Documentation is coming soon!
Event (to fire) setup
Documentation is coming soon!