...
The Boxalino Trackers automatically detects when the HTML tags with these attributes and classes enter in the viewport (adapted to the screen and therefore device of the visitor) and if the user simply scrolls through or if there is a pause to look at the displayed content. Items that are fully obstructed (e.g. overlay ditv) are properly detected and will not count.
As each part of the layout has unique identifiers (the data-bx-variant-uuid for the container elements and the data-bx-item-id for the inner content elements), the tracker knows exactly what is currently being viewed by the user.
...
In your layout, you might have a block which whose content is related to the content of another block.
...
In this case, much like in the other advanced case of related content, the tracker will also track the parent contents of each inner container are and add them to the tracked data.
| Info |
|---|
Don’t worry, you don’t have to implement any special logic to manage this case. You only need to tag your HTML automatically with all the returned bx-attributes and the rest will happen automatically. We only provide this explanation here to document the advanced cases the Boxalino tracker manages automatically. |
...
Doing it with this event over a tag manager will typically generate the add-to-basket event to be triggered sometimes twice (once through the GTM and once through the automated tracking), therefore it is not recommended, however, it will not have any problematic effect as Boxalino automatically detects such duplicated cases in its data processing and can resolve it automatically in its analytics.
...