DataLayer acts a middleman between different data source locations and Google Tag Manager. It can be seen as a single source of truth for data that is updated while a given visitor interacts with our pages.
npm install @studyportals/datalayerDataLayer acts as a middleman between multiple data source locations and Google Tag Manager, and provides a uniform way of tracking client interaction events within our pages at a given moment. It serves as an abstraction layer, meaning our Portals and microservices use it to dispatch relevant tracking information, but have no concern about the data's final destination neither what it's used for.
The source folder contains:
- domain: it's the core of the application. It contains multiple related services that listen to events from different locations and dispatches information to GTM;
- enum: contains all the necessary enums;
- infrastructure: contains the logic to interact with the outside world, that being how external clients interact with the service, and how DataLayer itself dispatches data to external actors (i.e. Google Tag Manager);
- types: all the types needed.
To be updated