Behavioral Tracking

Behavioral tracking refers to the act of tracking what activities a user performs while browsing your website. These activities include:

• Viewing products and product categories
• Viewing content and content categories
• Searching for entities (products, content, categories)
• Adding products to a shopping basket, and either purchasing them or not purchasing them
• Interacting with product recommendations, and either adding them to a shopping basket, or not adding them

In order for Relewise to offer the best performance for our services, Relewise relies on the tracked behavior of users. The more behavior Relewise is able to track, the better our services perform, and the better the conversion of users into paying customers.

Note: Behavioral Tracking data is free of charge for our customers.

Implementation details for Developers

See how to implement Behavioral Tracking here

GDPR Compliance

Tracking always has to happen with the user's explicit permission. Always ensure that your site is GDPR-compliant.

Relewise recommends partnering with a cookie consent provider, such as Cookiebot, CookieInformation, or Cookie Script.

These solutions are guaranteed to keep your solution GDPR-compliant, and integrate easily into Relewise for a hassle-free start to your tracking.

Historical Order Data

When implementing Relewise, you may benefit from importing historical order data to serve as a foundation for the behavioral tracking to come.

Historical order data helps inform our services of pre-existing popularity and entity relations, ensuring that they can perform at their peak from the moment you go live.

Updating Tracked Orders

When Relewise receives an order ID that has already been tracked, the default behavior is to track it again, which means that previously tracked product relations will be double-tracked and receive increased relevancy. As such, it is highly advised not to double-track orders, even when the order is updated.

For B2B scenarios where updating orders is important, it is possible for Relewise to enable an order ID tracker to prevent this double-tracking from happening. The logic then changes to ensure that Relewise persists the orders and uses them to reconcile user and product statistics each time you track a new order with the same OrderNumber. The update logic scans the previous order’s line items and compares them to the current ones. Products or variants that are no longer present are treated as removed lines; their contribution to purchase metrics is reversed.

Use of this feature requires a subscription to the B2B module. To learn more, please reach out to us.

Behavioral Tracking Types

The following is an overview of the various tracking types available via Relewise.

Track-Type	Description
TrackProductViewRequest	Tracks that a given product has been viewed by a user. This is commonly sent whenever a PDP is loaded.
TrackProductCategoryViewRequest	Tracks that the product list of a given product category has been viewed by a user. This should only be sent whenever an active navigation to a product category page is completed, and not for subsequent filtering, pagination-actions etc.
TrackContentViewRequest	Tracks that a given content page has been viewed by a user. This is commonly sent whenever a CDP is loaded.
TrackContentCategoryViewRequest	Tracks that the content list of a given content category has been viewed by a user. This should be sent whenever an active navigation to a content category page is completed, and not for subsequent filtering, pagination-actions etc.
TrackBrandViewRequest	Tracks that a dedicated brand-specific landing page has been viewed by the user.
TrackCartRequest	Tracks that a cart has been modified by a user. The complete contents of the cart should be sent whenever the cart is modified in any way. Note: Once a cart is converted to an order, the order is to be tracked separately (see TrackOrderRequest below). It is not necessary to also track an empty cart during this process.
TrackOrderRequest	Tracks that an order has been completed, including which products it consisted of.
TrackSearchTermRequest	Tracks that a user has searched for a given search term. Note: This is only to be used when not using Relewise Search; if the search was performed using Relewise Search, we automatically and implicitly track the search term.