Website event tracking service
Glossary Item Box
The website tracking service enables to track events from on the customer’s site and pass them to the tracking cloud for further processing and display in Creatio.
Introduction
The website tracking service enables building analytics and business processes based on custom scenarios. The tracking service is integrated into the Creatio platform. In the future, we plan to introduce interaction with all Creatio modules to enrich the data and interact with business processes.
The website event tracking service offers the following opportunities to the users:
- Collect data about page views, visitor numbers, traffic source, device properties, etc.
- Collect data about user activity, goal achievements, conversion rates, routes, and use cases for websites and mobile applications.
- Deanonymize page views.
To set up website activity tracking, make the preliminary settings in Creatio, then embed the tracking JavaScript code into the HTML source code of each page on the website. As a result, Creatio will receive information about all redirections of potential customers to the website and their activity. The tracking code is triggered each time a customer performs a tracked activity on the website.
The tracking code generates the [BpmTrackingId] cookie files, which stores unique customer session IDs. This enables Creatio to gather information about customer's website events, both before and after actual registration.
Learn more about setting up the website event tracking service of version 1.0 in the “How to set up website event tracking” block of articles.
Website event tracking service schema
The website event tracking service of version 2.0 is built on the microservice principles and comprises of the following components:
- Identity server – used to identify the Creatio application in the website event tracking service.
- Tracking WebApp Tenant – responsible for storing the metadata and settings of the connected primary Creatio application.
- Tracking WebApp Report – used to select reporting data on request.
- Tracking WebApp Receiver – used to receive incoming events from web-sites.
- Message broker Apache Kafka – used for data exchange between components.
- Tracking Raw Receiver – used to receive raw tracking data.
- Apache Cassandra database – a distributed NoSQL database management system designed for building highly scalable and reliable repositories capable of storing huge amounts of hashed data. Stores the tracking data. To enable storing huge amounts of data, you can scale the website event tracking service and create new clusters (Nodes).
The working principles of the website event tracking service are presented in Figure 1.
Fig. 1. The workflow of the website event tracking service of version 2.0
Learn more about setting up and working with the website event tracking service of version 1.0 in the “Website event tracking” block of articles.
Website event tracking service scalability
The microservice architecture of the website tracking service of version 2.0 enables scalability via the standard means available in every component, such as clustering, horizontal scaling, and vertical scaling.
Website event tracking service compatibility with Creatio products
The website event tracking service of version 1.0 is compatible with Creatio Marketing version 7.14 and up.
The website event tracking service of version 2.0 is compatible with Creatio Marketing version 7.16.4 and up.
Website event tracking service deployment options
The website event tracking service of version 2.0 can be deployed in the cloud. At the moment, on-site deployment of the service is not implemented.
See Also
