Event- and tag-management
Configure tracking events and trigger actions
The event and tag manager lies at the heart of fusedeck®. Here you can define what exactly you want to track and how you’d like to store the data. A tracking event always comprises a trigger element, conditions (e.g. where the user has to come from or which webpage they have to be on), and actions to be triggered when the triggers and conditions are satisfied. You determine how often an event should be triggered (once per session, once per page view or every time) and how long the data should be stored for.
Tracking environments
Usually, a tracking environment for production and an environment for testing are created for each property. But you can create as many environments as you want. For instance, you can easily set up a production environment for GDPR countries and countries with similar data protection laws and another production environment for the rest of the world. This way, you can ensure that events are only run that are actually allowed under the relevant data protection laws. In the test environment, you receive additional information in the console for debugging purposes and can also conveniently send a test environment to an external person, enabling them to run tests as well.
Maintain order with workspaces
In fusedeck®, you have the ability to set up different workspaces to maintain order with your tracking events. These workspaces can be activated or paused at any time and can also be equipped with conditions. These conditions ensure that the events of a workspace are only run if, for example, the user comes from a country that does not require consent for the generation of an audience.
Versioning
Mistakes that need to be undone can happen quickly. You can look at the different versions of your workspace at any time and restore an old version with just one click. The versions show a history of published changes.
Range of adjustable triggers
Triggers set off tracking events. You can choose from a range of different trigger types and configure them as needed. Every trigger can be tied to conditions, for example, in order to measure visibility on a mobile device differently than on desktop.
A page view can be configured as a trigger for a tracking event. As soon as a user views a page, this trigger is activated.
Define which element on the website a user has to click on for a tracking event to be triggered. fusedeck® also allows you to configure all possible clicks on the corresponding elements with a single event. In other words, you don’t need to set up click events individually for each page.
Use this trigger when you want to activate a tracking event as soon as a certain element on your website is visible to the user for a defined period of time. You can determine how long the element has to be visible, at what percentage, and what the maximum scrolling speed may be. Here fusedeck® can recognize DOM manipulation and also takes account of CSS visibility.
With this trigger, you activate tracking events when a user reaches a certain scrolling depth on the website. You can also set multiple trigger points – and not just for scrolling down but also when a user reaches a certain scrolling depth and scrolls back up.
The timer allows you to define a period of time after which a tracking event is activated. The time can be set for the entire session or for individual page views. What’s more, with fusedeck® you can define whether the user has to be active, idle or inactive or if no distinction should be made.
The form submit trigger is used to activate a tracking event as soon as a form has been sent. This tricker also recognizes DOM manipulation. You can decide whether you only want to save the number of submitted forms or also their content in fusedeck®.
This trigger activates a tracking event when a certain layer is present in the data layer. fusedeck® supports a proprietary data layer, but can also read the data layers of other providers.
Using a data layer push, you can set a trigger that listens for changes in the data layer within a page view.
Use the video trigger if you want to activate a tracking event when the user views a video. You define the trigger points as percentages of the video length or in milliseconds, set a required minimum playtime, and define by how many percent the video needs to be visible as well as the maximum scrolling speed. Besides YouTube videos, fusedeck® also supports Vimeo and HTML5 clips.
With the DOM event trigger, you can use all possible browser events and create your own trigger. This includes drag and drop, focus, full-screen change, key up and key down, touch start and touch end, volume change, animation, blur, etc.
The hover trigger is used to activate a tracking event as soon as a user moves the mouse pointer over a certain element on your website. To prevent any accidental hovers from being measured, you can define the minimum amount of time the mouse pointer should be over an element for it to count.
In some cases, it can be really useful to define an event that acts as a trigger. This allows you to combine events in a logical chain.
Process dynamic data with variables
Variables add dynamism to your tracking. They’re indispensable if you want to read out the product ID, shopping cart value, CRM ID or just the text of a button, for example. fusedeck® can read variables from a range of places and store them in the tracking system.
Load values from a JavaScript integrated into the website.
The environment variables enable you to access all information that fusedeck® provides. This can be client-specific data, such as user ID, language, and the tracking type used, or environmental variables such as date and time, the environment name and type, and much more. Page view-specific information such as URL, pathway, pathway segment or URL parameters can also be queried. Moreover, referrer-specific information, user agent, OS, device or geo-specific data can be retrieved in this way.
This function allows you to read values from the data layer and store them in fusedeck®. For example, product IDs, shopping carts, and similar information are often transmitted in this way.
If important values are stored in a cookie, fusedeck® can read and store them as a variable.
fusedeck® can read any values from the DOM and store them as variables. You decide whether you want to save the innerHTML or innerText.
Data is often stored in the browser’s local storage. fusedeck® can also access values in local storage and save them as variables.
As is the case for local storage, you can also read values from session storage and save them as variables in fusedeck®.
Tracking type-based session variables are stored in the tag manager within the session. With full cookie tracking, the variable is stored with the session cookie. In the case of server side sessions, the variable is saved on the server with the session. In both instances, the variable expires when the session is ended.
Trigger actions
When your triggers and conditions are satisfied, you’ll want to activate an action. Based on rule logic, you can generate audiences in third-party systems, dynamically adjust your website, manage external tracking pixels, run A/B tests, and much more.
With the analytics action, you can decide whether you want to have the tracking event available in the reporting engine or not. When you send the event to analytics, you’ll automatically have it on hand in the fusedeck® report builder.
This action activates a pixel. Pixels are typically used by external tracking tools to communicate the performance of an advertising medium to this third-party system, for example.
You can use the JavaScript action to run a JavaScript when the defined triggers and conditions are met. JavaScripts are used for a wide range of applications and allow a third-party system to receive signals from fusedeck®.
With the HTML action, you can load specific HTML code on your website and thereby adjust the layout of your website, for example, when the triggers and conditions are met.
A tracking template can contain HTML, JavaScript and replacement tags and can also be used for more complex actions. This way, you can load rule-based modals on your website or set up more complex audience structures.
This action allows you to save the content of variables, triggers or defined values in a cookie. For instance, you can set up a scoring value that increases depending on the user interaction. In a second event, you can define the threshold value that a user has to reach before an audience is automatically generated.
Events are generally based on variables and triggers in order to run certain actions, such as activating tracking, triggering templates or manipulating data. When the triggers and conditions for an event are met, you can activate another event (or multiple events) via the event action. This is useful if you want to link events in a sequence.
Everything under control with tracking templates
Templates allow you to manage HTML snippets used on a repeated basis. These can contain both HTML as well as JavaScript blocks.
For each template, placeholders can be defined to parameterize the template. Templates can be used as an action for events. Here, the placeholders are filled with values from variables, triggers or fixed values.