Rubens Knowledge Base

To effectively measure the success of your 3D configurator, you need to understand exactly how users are interacting with your products. Rubens provides a built-in analytics interface that emits events based on the Google Tag Manager standard, allowing your webshop to capture and process user behavior in real-time.

In this guide, you’ll learn how to:

• Understand the event system and the onGATracking callback
• Identify the most important analytic events for your business KPIs
• Implement data parsing for parameter and material changes
• Connect interaction data to your global tracking stack

The Rubens platform utilizes a dedicated analytics callback to bridge the gap between the 3D iFrame and your host website.

Analytic Event Callback: The primary method for capturing behavioral data is the configurator.analytics.callbacks.onGATracking function. When initialized, this callback passes three key arguments: type, event, and data. This structured approach ensures compatibility with standard tracking tools like gtag.js while allowing for custom data processing within your own environment.

The following events represent the most critical user interactions within the configurator and are essential for calculating conversion rates and ROI.

RequestProduct: This event is triggered the moment a user clicks the "Request" or "Add to Cart" button. It serves as your primary conversion signal, indicating that the user has completed their configuration and is ready to proceed with a purchase or inquiry.

Parameter:ChangeEvent: Captured whenever a user modifies a product attribute, such as a material, color, or dimension. This event is highly detailed; the event_label within the data object typically contains a string that identifies exactly which parameter was changed and what the new value is.

ARButtonClicked: Fired when a user initiates an Augmented Reality session. Tracking this event allows you to measure how often AR is used as a decision-making tool and its direct impact on final purchase intent.

TypeChangeEvent: Emitted when a user switches between different predefined product variants or models. This is useful for analyzing the user's discovery journey and identifying which starting configurations are most attractive.

Dock: Specifically for modular products, this event is triggered when a user adds or snaps a new component onto an existing configuration. It provides insight into the complexity and scale of the solutions your customers are designing.

By listening to these events, you can create a high-resolution map of user preferences and friction points.

Data Parsing & Custom Logic: Within the onGATracking callback, you can implement logic to filter for specific events. For example, by checking if the event includes "Parameter:ChangeEvent", you can split the event label to log exactly which material a user selected. This data can then be pushed to your internal CRM, a marketing pixel, or a custom dashboard.

Technical Integration Tip: To ensure no data is lost, it is recommended to register your analytics callbacks immediately after creating the configurator instance. This ensures that even the very first interaction – such as a user immediately changing a color – is captured and logged correctly.

Technical Documentation: Listen to Events