Important disclaimer
Fibbl do not own, or save, the data that comes through Google Analytics 4. Fibbl only sends raw data connected to the script's potential events, all data and logic connected to behavior and purchases comes directly from your own GA4. Fibbl provides a standardized Looker Studio report with built-in logic to make it easier for you as a customers to analyze and draw insights from what impact Fibbl has on your e-commerce. It is your responsibility as a customer to ensure that your general Google Analytics tracking functions as it should.
Introduction – What you can track
When the Fibbl script is implemented on your product detail pages and there is an available 3D model for the specific product, Fibbl can render and display its technologies for the website visitor. In those cases, there are three fundamental technical events that can happen in the user journey.
The script will be loaded. This will always occur in case there is a matching model for the specific product.
The visitor can view the Fibbl integration, by simply navigating to the place on the web page where it is placed.
The visitor can interact with the Fibbl integration, by simply interacting with the element (e.g. 3D, AR, VTO).
These three events is also the raw data we send to Google Analytics automatically when the script is implemented in the correct way, and can be used to segment users and view the difference in traditional metrics like time spent on site, pages per session, conversion rate when Fibbl is involved versus not involved. Take a look below for the exact name of the events we send and their meaning.
Event name | Description |
fibbl_load | The number of times the Fibbl integration (script) has been loaded. The script is only loaded when there is an available model on the specific product detail page that the visitor is browsing. |
fibbl_display | The number of times the Fibbl integration has been viewed by a visitor. "Viewed" have different meanings depending on what experience you have implemented. If you are using the fibbl-bar buttons, both fibbl-display and fibbl-use will be triggered when a user click on the buttons. |
fibbl_use | The number of times the Fibbl integration has been interacted with by a visitor, e.g. when someone twist and turn the 3D model in the model viewer when using the model-viewer or the fibbl-layer components. If you have implemented the fibbl-bar this event eill be triggered when the user clicks the button. |
Implementation – How to enable the tracking
Below you can see what the generic Fibbl script looks like. As long as you have added your specific GA4 Measurement ID in data-analytics-id, the events will be sent automatically to your GA4 property as soon as you are live with the script.
<script
src="https://cdn.fibbl.com/fibbl.js" type="module"
data-fibbl-config
data-locale="en-US"
data-analytics-type="google"
data-analytics-id="G-ABCABCABC"
></script>
Not sure which ID to use? This is how you find the ID in GA4.
Navigate to Admin in GA4
Click on 'Data streams' within the "Data collection and modification" section
Select the main data stream
Copy 'MEASUREMENT ID'
Validate implementation
If everything is set up correctly and you are live with the script in production, the different event types should start to trickle in. To validate, simply:
Navigate to Admin in GA4
Click 'Events' within the "Data display" section
Look out for the event types fibbl_load, fibbl_display and fibbl_use
Nothing in sight? Reach out to your dedicated Customer Success Manager and we will help you troubleshoot.
Configure Fibbl's standardized Looker Studio report
The set-up of the report is not mandatory, but it's highly recommended. With that said, you can still track events and build your own reports in GA4 even without the Looker Studio report. The report template (view demo here) was created to offer an easier solution that visualizes the performance and provides a further breakdown of the data.
Before proceeding with the project setup, there are two important things to consider:
Data is only being collected after the GA4 & Google BigQuery linkage is established so it’s better to configure it as soon as possible
Make sure that the product ID passed in Fibbl events is mappable with standard eCommerce events, especially purchase (i.e. the values are consistent). Follow the steps in the guide Product ID lookup between Fibbl and GA4 to validate this.
Get access to your Google Cloud project
Let us know if you prefer to set it up from your Google Cloud account. Otherwise we usually do this for you as we would like to cover the potential cost of the database. If you have not already received access, ask your Customer Success Manager for access.
Linking the GA4 property to Google BigQuery
This part takes about 2 minutes to complete and must be done from the customer side and by someone who has right access to the relevant GA4 property.
In the Google Analytics Admin section, under the "Product links" section, click "BigQuery links"
Choose the Google Cloud project you got access to step 1 and set data location to European Union (eu)
From the second step choose the Export type to be “Daily” (it’s the only setting to be included)
In the third setup step click [Submit] to link the GA4 property to BigQuery
Verify the setup - it may take some time (up to 48h) for data to start appearing in BigQuery. Once the setup is completed, you should be able to see the relevant dataset for GA4 data exports named analytics_[random digit combination] in BigQuery Studio with a corresponding table named events_(number)
Creating tables in Google BigQuery
This part takes about 30 minutes to complete and can either be done from the customer side or Fibbl side.
Since this setup is relatively new, we recommend that Fibbl do these steps for you. If you still want to do it yourself, let us know and we will share our internal documentation with you. Otherwise, sit back, relax and wait for a link to the report.
Did we miss something?
Not to worry! Just write to us via the chat bubble in the bottom right corner or email our support team at help@fibbl.com. ✌️